-
Notifications
You must be signed in to change notification settings - Fork 66
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
Revisit label and annotation restrictions in AdditionalServiceConfig #689
Comments
olim7t
added a commit
to olim7t/cass-operator
that referenced
this issue
Aug 23, 2024
5 tasks
olim7t
added a commit
to olim7t/cass-operator
that referenced
this issue
Aug 23, 2024
Merged
5 tasks
adejanovski
added
review
Issues in the state 'review'
and removed
ready-for-review
Issues in the state 'ready-for-review'
labels
Aug 26, 2024
olim7t
added a commit
to olim7t/cass-operator
that referenced
this issue
Aug 26, 2024
olim7t
added a commit
to olim7t/cass-operator
that referenced
this issue
Aug 26, 2024
olim7t
added a commit
to olim7t/cass-operator
that referenced
this issue
Aug 27, 2024
olim7t
added a commit
to olim7t/cass-operator
that referenced
this issue
Aug 27, 2024
adejanovski
added
done
Issues in the state 'done'
and removed
review
Issues in the state 'review'
labels
Aug 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
cass-operator does not allow label and annotation keys that start with
cassandra.datastax.com
ork8ssandra.io
inAdditionalServiceConfig
(source). This is intended to prevent collisions with the labels that the operator uses internally.However, k8ssandra-operator, which relies on cass-operator to manage its datacenters, also uses the
k8ssandra.io
prefix. There are cases where it might need to label services for its own internal needs, but this is currently not possible.The text was updated successfully, but these errors were encountered: