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

Move selector immutability check to validation after v1beta1 retires #50791

Open
crimsonfaith91 opened this issue Aug 16, 2017 · 12 comments
Open
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. kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/apps Categorizes an issue or PR as relevant to SIG Apps.
Projects

Comments

@crimsonfaith91
Copy link
Contributor

crimsonfaith91 commented Aug 16, 2017

The check for selector immutability is located at PrepareForUpdate functions of deploymentStrategy, rsStrategy and daemonSetStrategy. We are not able to have the check at validation before v1beta1 API version retires due to breaking change to some tests (discussed in this closed PR). Once v1beta1 retires, we should move the check to validation.

@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.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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 Jan 3, 2018
@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
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Feb 8, 2018
@kow3ns kow3ns added this to Backlog in Workloads Feb 27, 2018
@liggitt liggitt added 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. labels Jan 25, 2022
@liggitt
Copy link
Member

liggitt commented Jan 25, 2022

the beta types have not been served since 1.16, so this can be done now.

relevant spots to update are in https://grep.app/search?q=TODO%28%2350791%29&filter[repo][0]=kubernetes/kubernetes

@yardenshoham
Copy link

/assign

@yardenshoham
Copy link

/unassign

@XDRAGON2002
Copy link
Member

@crimsonfaith91 is this issue still up for grabs? If so then as a new contributor I would like to take this up.

@yardenshoham
Copy link

I had a PR to resolve it but it never got reviewed. If you do grab it:

  1. Move selector immutability checks into validation #107858 is a good starting point
  2. Expect for it to go unreviewed for a long time

@XDRAGON2002
Copy link
Member

I had a PR to resolve it but it never got reviewed. If you do grab it:

  1. Move selector immutability checks into validation #107858 is a good starting point
  2. Expect for it to go unreviewed for a long time

Thanks a lot @yardenshoham! I did go through your PR and understand the basics of what the issue entails. Also I still can't believe that your PR went unreviewed for an entire year!

@XDRAGON2002
Copy link
Member

/assign

@46kumarshivam
Copy link

/assign

@XDRAGON2002 XDRAGON2002 removed their assignment Oct 1, 2023
@kushalShukla-web
Copy link
Contributor

is this issue still open ?

@lavishpal
Copy link

/assign

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. kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/apps Categorizes an issue or PR as relevant to SIG Apps.
Projects
Status: Needs Triage
Workloads
  
Backlog
Development

Successfully merging a pull request may close this issue.

9 participants