Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Deploy mise as a frontend subchart #1424
base: main
Are you sure you want to change the base?
Deploy mise as a frontend subchart #1424
Changes from all commits
633d69e
114ba33
9e3655d
69cd5a1
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
nit: probably best to expose this in values.yml
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.
nit: it's a wider-reaching issue across our repo, and you're following the convention we have here, so I wouldn't block merge - but we should really really consider using the Helm standard Selectors/Labels for multiple Helm lifecycling reasons. Instead of writing these up ourselves, we can simply inject
ChartName.selectorLabels
. If you do a rawhelm init <chartName>
you'll see a mature implementation in their default scaffolding to follow, but here's the jist:On the Deployment (and any resource in the chart) itself, that looks like:
Here in the Pod selector, we use:
and below in the Pod template, it would be:
As I understand, properly labeling our resources in a way Helm understands allows us to do full lifecyling (including delete) on resources in our charts. Without standard Labels for Helm to select on, it's impossible for Helm to understand what resources are part of a chart inside a cluster, so it can't find them after initial installation.
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.
As far as I observed Helm adds their own labels to keep track what is managed by helm for lifecycling (including deletion)
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.
Nevertheless consistent labels are nice. We should decide on a scheme and implement it across our repo. I would not block merging though