-
Notifications
You must be signed in to change notification settings - Fork 39.2k
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
apply can't work, but delete/apply work #86463
Comments
@ozbillwang: The label(s) In response to this:
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. |
@kubernetes/sig-cli-bugs |
@ozbillwang: Reiterating the mentions to trigger a notification: In response to this:
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. |
@ozbillwang: The label(s) In response to this:
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. |
The selector on an apps/v1 replicaset is immutable after creation. /remove-sig cli |
As it said |
See #66602 |
What happened:
when apply a replicaset change, and change the label and apply again, it reports error, I have to delete this replicaset and apply again, all fine.
Furtherly, if the first deployment with wrong yaml, and apply with correct one, it only starts one pod.
What you expected to happen:
should be fine to switch the label and start the nominated count of replica pods.
How to reproduce it (as minimally and precisely as possible):
sometime, if previous yaml file is not correct and I apply a proper yml later, I can see the replicaset is created, but only run with one pod. which I need 2 replica pods.
Anything else we need to know?:
Environment: linux
kubectl version
):cat /etc/os-release
):uname -a
):master $ uname -a
Linux master 4.4.0-166-generic #195-Ubuntu SMP Tue Oct 1 09:35:25 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered: