aws / aws/eks-anywhere

Unable to upgrade cluster after changing network path in vmware

Open
#4,302 1 comment 1 reaction 0 assignees View on GitHub
area/cli external team/cli
Dominant language
Go
Stars
2.1k
Forks
328
Avg merge
1d 4h
Merged PRs (30d)
9

Description

**What happened**:
After changing network path in vmware (/cluster/network/eks to /cluster/network/qual/eks ), i'm unable to upgrade cluster.

✅ Connected to server
✅ Authenticated to vSphere
✅ Datacenter validated
❌ Validation failed {"validation": "vsphere provider validation", "error": "network /cluster/network/eks not found", "remediation": ""}

After changing network in config

✅ Cluster CRDs ready
✅ Cluster object present on workload cluster
✅ Upgrade cluster kubernetes version increment
✅ Validate authentication for git provider
❌ Validation failed {"validation": "upgrade preflight validations pass", "error": "validation failed with 1 errors: spec.network is immutable. Previous value /cluster/network/eks, new value /cluster/network/qual/eks", "remediation": ""}
Error: failed to upgrade cluster: validations failed

I tried to change the value manually :

```
kubectl get vspheredatacenterconfigs.anywhere.eks.amazonaws.com mgmt -o yaml > /tmp/vspheredatacenterconfigs.yaml

vim /tmp/vspheredatacenterconfigs.yaml

kubectl apply -f /tmp/vspheredatacenterconfigs.yaml
The VSphereDatacenterConfig "mgmt" is invalid: spec.network: Invalid value: "/cluster/network/qual/eks": field is immutable
```

After, I tried deleting the object to recreate it :

```
kubectl delete vspheredatacenterconfigs.anywhere.eks.amazonaws.com mgmt
vspheredatacenterconfig.anywhere.eks.amazonaws.com "mgmt" deleted

kubectl apply -f /tmp/vspheredatacenterconfigs.yaml

Error from server (BadRequest): error when creating "/tmp/vspheredatacenterconfigs.yaml": admission webhook "validation.vspheredatacenterconfig.anywhere.amazonaws.com" denied the request: Creating new VSphereDatacenterConfig on existing cluster is not supported
```

does it mean that i have to recreate the cluster ?

**What you expected to happen**:

Changing network in vmware don't affect upgrade operation

**How to reproduce it (as minimally and precisely as possible)**:
Change network path in vmware and try to upgrade cluster

**Environment**:
- EKS Anywhere Release:
eksctl version
0.111.0-dev+9a99e9218.2022-09-09T18:36:17Z

bottlerocket-v1.23.9-kubernetes-1-23-eks-5-amd64

- Vmware
vSphere Client version 7.0.3

Contributor guide

Open the contributing guide

Research direction

Start by tracing the upgrade preflight validation and the VSphereDatacenterConfig admission validation described in the report. Reproduce the network-path change followed by an upgrade, then determine the supported outcome for an existing cluster and verify it with the relevant validation or upgrade tests; done means the behavior is corrected or the limitation is clearly documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes
Domain
infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.