Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add validations for AzureCluster Updates #497

Closed
CecileRobertMichon opened this issue Apr 3, 2020 · 15 comments · Fixed by #1098
Closed

Add validations for AzureCluster Updates #497

CecileRobertMichon opened this issue Apr 3, 2020 · 15 comments · Fixed by #1098
Assignees
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

Comments

@CecileRobertMichon
Copy link
Contributor

Some fields (eg. Azure location) are immutable and we should fail when they are updated.

To get started, you can look at how we implemented validation for AzureMachines here:

https://github.com/kubernetes-sigs/cluster-api-provider-azure/blob/master/api/v1alpha3/azuremachine_webhook.go#L46

and add to https://github.com/kubernetes-sigs/cluster-api-provider-azure/blob/master/api/v1alpha3/azurecluster_webhook.go

You can also look at this PR in CAPA which achieves something similar: https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/1677/files

@CecileRobertMichon CecileRobertMichon added the good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. label Apr 3, 2020
@CecileRobertMichon
Copy link
Contributor Author

/help

@k8s-ci-robot
Copy link
Contributor

@CecileRobertMichon:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

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.

@k8s-ci-robot k8s-ci-robot added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Apr 3, 2020
@jackfrancis
Copy link
Contributor

/assign

@CecileRobertMichon CecileRobertMichon changed the title Add validations for AzureCluster Add validations for AzureCluster Updates Apr 20, 2020
@jackfrancis
Copy link
Contributor

@CecileRobertMichon should we re-scope this issue to just the location property? If so, then #522 will close this. If not, then I'll note in #522 that we've made progress, but we'll keep this issue open.

@CecileRobertMichon
Copy link
Contributor Author

@jackfrancis let's keep this one open and once #522 merges we can make a list of the other properties that should be validated as immutable in this issue for someone else to pick up.

@CecileRobertMichon CecileRobertMichon added this to the next milestone Jun 4, 2020
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 2, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 2, 2020
@CecileRobertMichon
Copy link
Contributor Author

/remove-lifecycle stale

@alexeldeib
Copy link
Contributor

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Oct 29, 2020
@CecileRobertMichon
Copy link
Contributor Author

/unassign @jackfrancis

@surajrana93
Copy link
Contributor

@CecileRobertMichon do you need help in this?

@furkatgofurov7
Copy link
Member

@surajrana93 have you picked this up already? if not I would like to work on this.

@CecileRobertMichon
Copy link
Contributor Author

@furkatgofurov7 go for it, I believe @surajrana93 is already working on #1075

@furkatgofurov7
Copy link
Member

/assign

@CecileRobertMichon
Copy link
Contributor Author

Fields that we should allow updates on:

  • AdditionalTags
  • ControlPlaneEndpoint (this should be moving to status in v1alpha4 but we need to keep it updatable so the controllers can update it when the LB is provisioned)
  • NetworkSpec.APIServerLB (this is to allow backcompat backfill)

Everything else should not be updated.

/cc @devigned

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants