-
Notifications
You must be signed in to change notification settings - Fork 74
[Enhancement] Define some default values uniformly #425
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
[Enhancement] Define some default values uniformly #425
Conversation
a5ff654
to
3d15606
Compare
@@ -61,7 +106,7 @@ starrocksFESpec: | |||
image: | |||
# image sliced by "repository:tag" | |||
repository: starrocks/fe-ubuntu | |||
tag: 3.1-latest | |||
tag: "" |
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.
if we set it to empty string. will it also take precedence over the values in componentValues
?
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.
No. Only when it has a non-empty value.
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.
- @mingmxu to take a loot as well
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.
Thanks for the change. This is super useful!
# - key: metadata.name | ||
# operator: In | ||
# values: | ||
# - target-host-name |
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.
Let's add podLabels
as well.
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.
commited
3d15606
to
05deb8f
Compare
Signed-off-by: yandongxiao <[email protected]>
05deb8f
to
f5c450d
Compare
Get the value of the nodeSelector field in the starrocksFESpec | ||
*/}} | ||
{{- define "starrockscluster.fe.nodeSelector" -}} | ||
{{- if .Values.starrocksFESpec.nodeSelector -}} |
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.
this is a complete replace behavior, not the merge together behavior, need explicit this in the values.yaml comments.
Otherwise, the user can define some of the common criteria in compontValues and add additional specific criteria in each XXSpec and expect the final result is the merge-replace output.
The same applies to hostAlias/Labels/affinity ...
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.
committed
Signed-off-by: yandongxiao <[email protected]>
Description
In the individual spec definitions of the sub-components, there are indeed many fields with the same name, such as image, imagePullSecrets, nodeSelector, schedulerName. Generally, the contents of these fields are consistent in the individual spec definitions of the sub-components.
Fixes: #424
Checklist
For helm chart, please complete the following checklist:
file of starrocks chart.
scripts
directory, runbash create-parent-chart-values.sh
to update the values.yaml file of the parentchart( kube-starrocks chart).