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.
Fixed the Helm template so imagePullSecrets is only defined at the pod level (not inside the container), eliminating the warning about spec.template.spec.containers[0].imagePullSecrets.
🐛 Bug-fix PR
Before opening this PR please:
make lint- passesruff,mypy,pylintmake test- all unit + integration tests greenmake coverage- ≥ 90 %make docker docker-run-sslormake podman podman-run-ssl📌 Summary
It fixes the below warning when trying to deploy using helm:
"Warning: unknown field "spec.template.spec.containers[0].imagePullSecrets""
🔁 Reproduction Steps
Run the helm install command to deploy on K8S or OCP cluster.
🐞 Root Cause
The job-migration.yaml file (charts/mcp-stack/templates/job-migration.yaml) has the imagePullSecrets inside 'containers' section; which is incorrect. This is triggering the warning.
💡 Fix Description
Fixed the Helm template so imagePullSecrets is only defined at the pod level (not inside the container), eliminating the warning about spec.template.spec.containers[0].imagePullSecrets.
🧪 Verification
make lintmake testmake coverage📐 MCP Compliance (if relevant)
✅ Checklist
make black isort pre-commit)