rancher/rancher#31221
initial creation of gke driver
create shared google service for v1/v2 driver
wip
all fetch methods for google to shared service
cluster/kubernetes options
ippolicy conditionals
private nodes observer so can force ipaliases true
subnetwork logic
cru-private-cluster for gke
initial values
gke node pools
default configs and service cleanup
node group changes
subnet work
hide private nodes config if not enabled
useIpAliases work
master authorized network component
loggings
no initial master version
gke node pool fixups
input-cidr component and validation
wip - new np logic
node pool updates
fix ups from launching
edit mode changes
more edit updates
more fix ups
node pool edits
import gke
reset auto-scale
implment cloud credentials in gke v2
Cloud cred changes for gke nice to haves
imp fetch clusters
Implement Shared Subnets
cleanup
Import private cluster work and other fixes
private cluster changes
More import/register changes
Null values and node pool version changes
gke private networks warning
fixups
k3s clusters that do not have a config should not allow editing of items on the config.
A null k3s config indicates a docker installed cluster so I've added extra logic
to check if the config exists and if it does not we don't show the manage import cluster info component.
I also added logic to the final save method in cru cluster to only show the registration step if the cluster is pending
and not a null k3s config.
rancher/rancher#30977
Since the env vars have to be saved on a cluster there is no easy way of dynamically updating the cluster command without trying to split the string and do all kinds of nasty things.
I refactored the logic for when we show the command for both Custom and Import clusters until after the cluster has been saved. This ensures the user is required to save the cluster before fetching the command on an edit action
rancher/rancher#31529
After some discussions we decided to simplify things since all that's actually needed are keyValues.
I made the changes within the existing component instead of switching to keyValue to reduce risk at this stage of the release.
rancher/rancher#31545
Since the reference types can't exist until the cluster is created I added an option to disable all reference types and use it during RKE create
Even though the backend doesn't indicate the variable name is required we're marking it as such because it casues cluster to fail. No validation will be done at this time.
rancher/rancher#31528
- Fixed issues with determining the provider when editing clusters that are still provisioning.
- Fixed empty values causing problems
- Fixed an issue where the default value wasn't getting set properly for configmaps and secrets when selecting the type and nothing else
https://github.com/rancher/rancher/issues/31023#issuecomment-784717552
updated the spot instance to make spot instance types required along with adding a default row
during the process I also found that the nodegroups data was being reset on a failure so added some wrappers around the observer for this.
rancher/rancher#31213rancher/rancher#31288
rancher/rancher#30613
Initial seperation of the node instance info and group info EKS v2
Template versions
inputs enabled for eks launch templates
build files
Resource instance tags
resource template cleanup
lint fix
dont disable gpu or spot during create
launch template pr feedback
Add example user data and removal on save logic
* Add LKE string constants
Supersedes https://github.com/rancher/ui/pull/4298
* New cluster driver boilerplate
* Pull assets from from https://github.com/linode/ui-cluster-driver-lke
* Convert from skeleton format
* Add LKE to build_in_ui
- refactored to have the two locations match
* Replace " with '
* Translations for labels
* Language was moved to translations file
* Linter errors
* replace multiple sets with setProperties
* Move bare strings to translations
* Swap this.setProperties for ember/object's version
* Remove custom language change reactions
* remove dollar sign in favor of format-number
* Convert node pool list to a sortable table
Co-authored-by: Tamal Saha <tamal@appscode.com>
custom config has a type of `map[json]` and when we process this for the edit yaml view we can goof some of the keys in the arbitrary JSON.
specifically the `Resources` key gets dasherized and lower cased which borks the cluster on save.
rancher/rancher#30555
exposes the kubeApi Secrets config enabled property which allows users to rotate keys
disable rotate action when prop is not set, we are rotating or, the cluster is transitioning
rancher/rancher#30077
previously we prevented users from changing the choice of standard or custom vpc which also loads the security groups, this adds the same logic back in for eks v2
rancher/rancher#30301
Westly Wright
Cody Jackson
Westly Wright
jesse.millan
Phillip Campbell