Skip to content
This repository was archived by the owner on Oct 28, 2024. It is now read-only.

Not allow edit virtualcluster for some field #184

Closed
jichenjc opened this issue Jul 19, 2021 · 5 comments
Closed

Not allow edit virtualcluster for some field #184

jichenjc opened this issue Jul 19, 2021 · 5 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@jichenjc
Copy link
Contributor

What steps did you take and what happened:
[A clear and concise description on how to REPRODUCE the bug.]

What did you expect to happen:

kubectl edit vc vc-sample-23

spec:
  clusterDomain: cluster.local
  clusterVersionName: cv-sample-np23 ===> cv-sample-np24

success

expected: it should fail, we should consider only allow desired field to be updated and block others ..

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • cluster-api-provider-nested version:
  • Minikube/KIND version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):

/kind bug
[One or more /area label. See https://github.com/kubernetes-sigs/cluster-api-provider-nested/labels?q=area for the list of labels]

@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Jul 19, 2021
@jichenjc
Copy link
Contributor Author

any thoughts on this? @christopherhein @Fei-Guo comments?

@jichenjc
Copy link
Contributor Author

/assign

@Fei-Guo
Copy link

Fei-Guo commented Jul 19, 2021

Yes. In current version, we don't consider vc upgrade through changing the cluster version name and we should add webhook to make this field immutable. We defer the upgrade story for cluster version based provisioning because we will design update worklflow based on CAPN in next step.

@christopherhein
Copy link
Contributor

/close

Closing since this PR was implemented and merged.

@k8s-ci-robot
Copy link
Contributor

@christopherhein: Closing this issue.

In response to this:

/close

Closing since this PR was implemented and merged.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

4 participants