Repository navigation
feat: add production Helm chart controls - #47
Conversation
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Caution Review failedThe pull request is closed.
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: be163d33cb
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| {{- toYaml .Values.podSecurityContext | nindent 8 }} | ||
| containers: | ||
| - name: logsight-api | ||
| image: "{{ .Values.image.repository }}:{{ default .Chart.AppVersion .Values.image.tag }}" |
There was a problem hiding this comment.
Support digest-qualified image references
For deployments using the immutable image digests advertised in the chart guide, this template always inserts a tag separator: setting image.tag=sha256:… produces repository:sha256:…, while putting repository@sha256:… in image.repository appends :0.2.0 to the digest. Both are invalid image references, so those pods cannot start. Add a digest-aware rendering path using repository@sha256:…, or support a complete image reference without appending a tag.
Useful? React with 👍 / 👎.
Summary
Operational boundary
Validation