You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Applying the annotation to Nodes would reduce the levels of redundant messaging in the controller
What happened instead?:
Annotation could not be applied.
How to reproduce it (as minimally and precisely as possible):
; k patch node ip-XXX-XXX-XXX-XXX.ec2.internal --patch '{"metadata": {"annotations": {"k8s.io/cluster-autoscaler/enabled": "false"}}}'
The Node "ip-XXX-XXX-XXX-XXX.ec2.internal" is invalid: metadata.annotations: Invalid value: "k8s.io/cluster-autoscaler/enabled": a qualified name must consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyName', or 'my.name', or '123-abc', regex used for validation is '([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9]') with an optional DNS subdomain prefix and '/' (e.g. 'example.com/MyName')
Anything else we need to know?:
The text was updated successfully, but these errors were encountered:
Which component are you using?: cluster-autoscaler
What version of the component are you using?:
HEAD
(feature is unreleased)Component version:
HEAD
What k8s version are you using (
kubectl version
)?: EKS 1.28kubectl version
OutputWhat environment is this in?: AWS
What did you expect to happen?:
Applying the annotation to Nodes would reduce the levels of redundant messaging in the controller
What happened instead?:
Annotation could not be applied.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
The text was updated successfully, but these errors were encountered: