cloud-provider-gcp
cloud-provider-gcp copied to clipboard
cloud-provider-gcp contains several projects used to run Kubernetes in Google Cloud
* Migrates e2e test for recreating nodes from k/k in-tree to this repository (`cloud-provider-gcp`). * Test file migrated for k/k: https://github.com/kubernetes/kubernetes/blob/release-1.30/test/e2e/cloud/gcp/recreate_node.go #### Status Failure due to missing `TestContext.NodeInstanceGroup`, which looks...
* Migrates 3 GPU upgrade/downgrade e2e tests from k/k in-tree to this `cloud-provider-gcp` repository. Migrated from file: https://github.com/kubernetes/kubernetes/blob/release-1.30/test/e2e/cloud/gcp/node/gpu.go * Migrates 2 Nvidia GPU e2e tests from k/k in-tree to this...
* Migrates 10 e2e test for persistent disks from k/k in-tree to this repository (`cloud-provider-gcp`). * Test file migrated for k/k: https://github.com/kubernetes/kubernetes/blob/release-1.30/test/e2e/storage/pd.go
* Migrates 10 e2e test for persistent disks from k/k in-tree to this repository (`cloud-provider-gcp`). * Test file migrated for k/k: https://github.com/kubernetes/kubernetes/blob/release-1.30/test/e2e/storage/regional_pd.go
* e2e test for `PersistentVolumes` on GCP transitioned from in-tree to the `cloud-provider-gcp` * Migrated from k/k in-tree e2e test at: https://github.com/kubernetes/kubernetes/blob/master/test/e2e/storage/persistent_volumes.go #### Status * Currently all tests are failing...
Related issues: #664 #359 With the in-tree provider becoming obsolete, we need basic documentation that covers the following: * Key concepts about the out-of-tree provider (what is it, why/when would...
Hi! I have been starting a cluster using the legacy mode before like this: `kubetest2 gce -v 2 --repo-root ~/src/k8s.io/kubernetes --gcp-project --legacy-mode --build --up --env=ENABLE_CUSTOM_METRICS=true --env=KUBE_ENABLE_CLUSTER_AUTOSCALER=true --env=KUBE_AUTOSCALER_MIN_NODES=3 --env=KUBE_AUTOSCALER_MAX_NODES=6 --env=KUBE_AUTOSCALER_ENABLE_SCALE_DOWN=true --env=KUBE_ADMISSION_CONTROL=NamespaceLifecycle,LimitRanger,ServiceAccount,ResourceQuota,Priority...
Bumps the gomod-dependencies group with 6 updates in the /providers directory: | Package | From | To | | --- | --- | --- | | [github.com/GoogleCloudPlatform/k8s-cloud-provider](https://github.com/GoogleCloudPlatform/k8s-cloud-provider) | `1.25.0` |...
For core K8s APIs, `cloud-node`, `cloud-node-lifecycle`, `service` and `route` controllers fetch informers from the completed config rather than from the controller context (e.g. [here](https://github.com/kubernetes/kubernetes/blob/283ff763b3fd82c831f1f45efa87fb2aa518d184/staging/src/k8s.io/cloud-provider/app/core.go#L45)), so we basically mimic that behavior...
This PR updates the Internal Load Balancer Bug: Load Balancer controller removes nodes when they have an empty string in the Zone field, but the nodes are actually already in...