-
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
oc annotate does not allow setting an annotation to empty #11175
Labels
component/cli
component/internal-tools
kind/bug
Categorizes issue or PR as related to a bug.
priority/P2
Comments
cc: @openshift/cli-review probably needs an upstream issue |
juanvallejo
added a commit
to juanvallejo/origin
that referenced
this issue
Oct 4, 2016
Fixes: openshift#11175 Annotations with empty values can be used, for example, in oadm diagnostics logging. This patch removes the client-side check for empty values in an annotation key-value pair. **Before** ``` $ oc annotate pod zookeeper-1 openshift.io/node-selector="" --overwrite error: invalid annotation format: openshift.io/node-selector= ``` **After** ``` $ oc annotate pod zookeeper-1 openshift.io/node-selector="" --overwrite pod "zookeper-1" annotated ``` ``` $ oc get po/zookeeper-1 --template='{{.metadata.annotations}}' map[... openshift.io/node-selector: openshift.io/scc:anyuid test-label:test] ```
This was referenced Oct 4, 2016
juanvallejo
added a commit
to juanvallejo/origin
that referenced
this issue
Oct 4, 2016
Fixes: openshift#11175 Annotations with empty values can be used, for example, in oadm diagnostics logging. This patch removes the client-side check for empty values in an annotation key-value pair. **Before** ``` $ oc annotate pod zookeeper-1 openshift.io/node-selector="" --overwrite error: invalid annotation format: openshift.io/node-selector= ``` **After** ``` $ oc annotate pod zookeeper-1 openshift.io/node-selector="" --overwrite pod "zookeper-1" annotated ``` ``` $ oc get po/zookeeper-1 --template='{{.metadata.annotations}}' map[... openshift.io/node-selector: openshift.io/scc:anyuid test-label:test] ```
k8s-github-robot
pushed a commit
to kubernetes/kubernetes
that referenced
this issue
Oct 5, 2016
…ation-values Automatic merge from submit-queue Allow empty annotation values Related downstream issue: openshift/origin#11175 **Release note**: ```release-note release-note-none ``` Annotations with empty values can be used, for example, in diagnostics logging. This patch removes the client-side check for empty values in an annotation key-value pair. **Before** ``` $ kubectl annotate pod zookeeper-1 node-selector="" --overwrite error: invalid annotation format: node-selector= ``` **After** ``` $ kubectl annotate pod zookeeper-1 node-selector="" --overwrite pod "zookeper-1" annotated ``` ``` $ kubectl get po/zookeeper-1 --template='{{.metadata.annotations}}' map[... node-selector: test-label:test] ``` @fabianofranz @liggitt
both origin and upstream PRs have been merged, closing this issue, please re-open if necessary |
Did this make it to 3.7.1? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
component/cli
component/internal-tools
kind/bug
Categorizes issue or PR as related to a bug.
priority/P2
oc annotate does not allow setting an annotation to empty. Trying to advise users to set a project node selector to empty for use in oadm diagnostics logging.
Version
oc v1.3.0-alpha.3
kubernetes v1.3.0+507d3a7
features: Basic-Auth GSSAPI Kerberos SPNEGO
Server https://172.28.128.4:8443
openshift v1.3.0-alpha.3
kubernetes v1.3.0+507d3a7
Steps To Reproduce
Current Result
$ oc annotate namespace logging openshift.io/node-selector="" --overwrite
error: invalid annotation format: openshift.io/node-selector=
Expected Result
Yeah for you
Additional Information
The text was updated successfully, but these errors were encountered: