-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
UPSTREAM: 16668: Fix hpa escalation #5579
Conversation
[test] |
I would recommend just carrying the changes that ignore the namespace on the field, rather than changing the kube object. If someone specifies the namespace, we merely ignore it. That reduces the risk of an upstream change. |
You have permission to carry the change that ignores Namespace without argument without upstream. |
I can do that, but the risk during rebase is high because the old field will still be referenceable. |
setup problem re[test] |
I don't want to leave a dangerous latent field in play for another controller to start using |
upstream has LGTM |
https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/6593/
[test] |
[test] |
[test] |
9316ac7
to
db848a0
Compare
[merge] |
Evaluated for origin merge up to db848a0 |
[test] |
1 similar comment
[test] |
Evaluated for origin test up to db848a0 |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/6834/) (Image: devenv-rhel7_2638) |
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/6834/) |
pick for kubernetes/kubernetes#16661
@liggitt @smarterclayton we need this (or something like it) to make the HPA controller safe in 3.1
@DirectXMan12 @ncdc This is needed in or before #5310