-
Notifications
You must be signed in to change notification settings - Fork 117
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
MAISTRA-2023 Add support for specifying kiali resource and scheduling constraints #696
Conversation
50ff6ec
to
2f3ffe9
Compare
if nodeSelector != nil { | ||
if values, err := toValues(nodeSelector); err == nil { | ||
if len(values) > 0 { | ||
if err := setHelmValue(kialiValues, "deployment.nodeSelector", values); err != nil { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@luksa should this not be node_selector? See
{% if kiali_vars.deployment.node_selector|length > 0 %}
nodeSelector:
{{ kiali_vars.deployment.node_selector | to_nice_yaml(indent=0) | trim | indent(8) }}
{% else %}
nodeSelector: null
{% endif %}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
never mind, I see we have used nodeSelector in our template but are setting node_selector
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, unfortunately, Kiali uses the node_selector
notation for its values, whereas SMCP uses nodeSelector
. It was hard for me to decide where to perform the switch, but the existing code in conversion/kiali.go
already used the latter format, so I kept things consistent.
No description provided.