Re: [kubernetes/kubernetes] kubectl apply with blank clusterIP leads to "spec.clusterIP: Invalid value: "": field is immutable" error (#65272)
k8s-ci-robot
@deitch: Reiterating the mentions to trigger a notification:
@kubernetes/sig-cli-bugs
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.
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
fejta-bot
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
Avi Deitcher
/remove-lifecycle stale.
fejta-bot
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
Avi Deitcher
/remove-lifecycle rotten
k8s-ci-robot
@code-sleuth: Closing this issue.
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.
—
k8s-ci-robot
Closed #65272.
Tim Hockin
Because this came up again - kubectl replace (HTTP "PUT") is probably the wrong verb to be using. kubectl apply should be better in most ways (acknowledging the issues around changing ambiguous ports, which may require a read-modify-replace cycle)
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.