HYPERFLEET-786 - chore: use CHANGE_ME for both registry and repository defaults#78
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
WalkthroughThe PR updates Helm chart defaults, templates, and the Makefile test commands. charts/values.yaml: Sequence Diagram(s)Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Comment |
c2a0fd3 to
8f7d6e6
Compare
8f7d6e6 to
0c136fd
Compare
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@charts/templates/_helpers.tpl`:
- Around line 66-68: The failing validation only checks .Values.image.registry
(the block in charts/templates/_helpers.tpl) but deployment resolves registry
from .Values.global.imageRegistry first; update the guard to accept a valid
registry when either .Values.image.registry is set and not "CHANGE_ME" or when
.Values.global.imageRegistry is set and not "CHANGE_ME" (i.e., change the eq
check to consider both .Values.image.registry and .Values.global.imageRegistry
or resolve effectiveRegistry = coalesce(.Values.image.registry,
.Values.global.imageRegistry) before validating) so releases that set
global.imageRegistry won't be blocked.
In `@charts/templates/deployment.yaml`:
- Around line 23-25: podLabels can overwrite required selector labels causing
selector mismatch; update the charts/templates/deployment.yaml template so that
.Values.podLabels are merged in a way that does not override
sentinel.selectorLabels (the required keys like app.kubernetes.io/name and
app.kubernetes.io/instance). Specifically, ensure sentinel.selectorLabels are
rendered after or merged with higher precedence (e.g., mergeMaps behavior) so
sentinel.selectorLabels take precedence over .Values.podLabels, and reference
the symbols .Values.podLabels and sentinel.selectorLabels in your change to
guarantee those keys cannot be replaced.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 40a0dc8f-9542-425f-947b-79a5cdc66774
📒 Files selected for processing (4)
Makefilecharts/templates/_helpers.tplcharts/templates/deployment.yamlcharts/values.yaml
0c5b71f to
b75733c
Compare
|
/retest |
b75733c to
3e7bb29
Compare
77030b5 to
77070b9
Compare
77070b9 to
5039b33
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 86254860 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
42f5a82
into
openshift-hyperfleet:main
Summary
sentineltohyperfleet-sentinelfor consistency withhyperfleet-apiandhyperfleet-adapterimage.registryandimage.repositorydefaults toCHANGE_MEwith_helpers.tplvalidation guardsrunAsNonRoot/runAsUserfrom containersecurityContexttopodSecurityContextseccompProfile.type: RuntimeDefaultto container security contextpodLabelsto deployment templateBreaking Changes
Chart rename:
sentinel→hyperfleet-sentinelThis changes the
app.kubernetes.io/nameselector label fromsentineltohyperfleet-sentinel. Since Kubernetes selector labels are immutable on Deployments, existing sentinel releases must be uninstalled before upgrading:Umbrella charts (hyperfleet-infra) must also update their dependency name and values key from
sentinel:tohyperfleet-sentinel:.Test plan
make test-helmpasses (all 10 scenarios)Relates to: HYPERFLEET-786
Depends on: architecture#108