CHE_INFRA_KUBERNETES_NAMESPACE_ANNOTATIONS does not work as expected for OpenShift Node Selector annotation #23375
Labels
area/che-server
help wanted
Community, we are fully engaged on other issues. Feel free to take this one. We'll help you!
kind/bug
Outline of a bug - must adhere to the bug report template.
severity/P2
Has a minor but important impact to the usage or development of the system.
status/analyzing
An issue has been proposed and it is currently being analyzed for effort and implementation approach
Describe the bug
The customer would like to set the
openshift.io/node-selector
annotation on newly created namespaces. They are aware ofdevEnvironments.nodeSelector
, but would like to set the Node Selector on the namespace via this annotation still.When they set
CHE_INFRA_KUBERNETES_NAMESPACE_ANNOTATIONS: openshift.io/node-selector=node-role.kubernetes.io/worker=
in.spec.components.cheServer.extraProperties
on theCheCluster
however this does not work as expected (likely due to the "=" at the end). See the attached screenshots.I believe this is a Bug on how these additional annotations are handled. Or do you have any hints on how to set the necessary annotation like
openshift.io/node-selector: node-role.kubernetes.io/worker=
on Dev Spaces namespaces?Che version
other (please specify in additional context)
Steps to reproduce
CHE_INFRA_KUBERNETES_NAMESPACE_ANNOTATIONS: openshift.io/node-selector=node-role.kubernetes.io/worker=
in.spec.components.cheServer.extraProperties
on theCheCluster
Expected behavior
The annotation
openshift.io/node-selector=node-role.kubernetes.io/worker=
is set on the newly created namespace.Runtime
OpenShift
Screenshots
Installation method
OperatorHub
Environment
Linux
Eclipse Che Logs
Additional context
No response
The text was updated successfully, but these errors were encountered: