-
Notifications
You must be signed in to change notification settings - Fork 181
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
Enabled overrides for worker and coordinator configmap resources #163
Conversation
Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla |
Would be nice to have a test for this, maybe a second call to |
@@ -132,7 +132,7 @@ data: | |||
apiVersion: v1 | |||
kind: ConfigMap | |||
metadata: | |||
name: trino-access-control-volume-coordinator | |||
name: {{ template "trino.coordinator" . }}-access-control-volume-coordinator |
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.
could we eliminate suffix -coordinator
?
since in the template already has it, similar to other confimap objects
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.
since in the template already has it, similar to other confimap objects
I thought of it. The problem with it would be that in case someone doesn't overrides the name the default name only say "trino" which will cause duplicate configmap issues.
@silent-lad I recently added a |
Hey @nineinchnick , will do the same. Thanks for the heads up |
Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla |
Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla |
This is done now. |
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 looks great! My only ask is if you could add coordinatorNameOverride
and workerNameOverride
to values.yaml
with empty defaults, but with a comment describing when to use them.
test.sh
Outdated
time ct install "${CT_ARGS[@]}" --helm-extra-set-args "$HELM_EXTRA_SET_ARGS ${testCases[$test_name]}" | ||
echo "${testCases[$test_name]}" | ||
if [ "$test_name" == "multiple_clusters" ]; then | ||
time ct install "${CT_ARGS[@]}" --helm-extra-set-args "$HELM_EXTRA_SET_ARGS ${testCases[default]}" |
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.
I think we also need --skip-clean-up
added for ct install
.
Co-authored-by: Jan Waś <[email protected]>
Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla |
Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla |
Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla |
Have pushed the required changes @nineinchnick |
# If you want to have multiple Trino Clusters in same namespace | ||
# override the following values to avoid naming conflicts | ||
# Example: | ||
# coordinatorNameOverride: trino-adhoc | ||
# workerNameOverride: trino-adhoc | ||
# nameOverride: trino-adhoc |
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 you want to have multiple Trino Clusters in same namespace | |
# override the following values to avoid naming conflicts | |
# Example: | |
# coordinatorNameOverride: trino-adhoc | |
# workerNameOverride: trino-adhoc | |
# nameOverride: trino-adhoc | |
# -- Override resource names to avoid name conflicts when deploying multiple | |
# releases in the same namespace. | |
# @raw | |
# Example: | |
# ```yaml | |
# coordinatorNameOverride: trino-adhoc | |
# workerNameOverride: trino-adhoc | |
# nameOverride: trino-adhoc | |
# ``` | |
nameOverride: | |
coordinatorNameOverride: | |
workerNameOverride: |
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 will also require update to README.md
, but it should be automatically generated by the pre-commit
hook, if you've installed it locally.
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.
Also fix trailing spaces, see the CI errors for details.
@@ -133,7 +133,7 @@ data: | |||
apiVersion: v1 | |||
kind: ConfigMap | |||
metadata: | |||
name: trino-access-control-volume-coordinator | |||
name: {{ template "trino.coordinator" . }}-access-control-volume-coordinator |
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.
How about using trino.fullname
instead of trino.coordinator
?
@cla-bot check |
Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla |
The cla-bot has been summoned, and re-checked this pull request! |
This is to install multiple helm releases of trino cluster in the same namespace.
Closes #159 .