You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The templates/injector-deployment.yaml uses injector.image.registry instead of injector.agentImage.registry for the value of AGENT_INJECT_VAULT_IMAGE.
To Reproduce
Steps to reproduce the behavior:
Install chart, etc
Observe that inject pod config AGENT_INJECT_VAULT_IMAGE value is incorrect (docker.io instead of quay.io for registry)
and/or run a openbao unaware application, and observe that it doesn't get init container added by webhook
(reporter is testing under kubernetes, opendev/starlingx project)
Expected behavior
Inject agent image name is rendered with quay.io (not docker.io)
Describe the bug
The templates/injector-deployment.yaml uses injector.image.registry instead of injector.agentImage.registry for the value of AGENT_INJECT_VAULT_IMAGE.
To Reproduce
Steps to reproduce the behavior:
(reporter is testing under kubernetes, opendev/starlingx project)
Expected behavior
Inject agent image name is rendered with quay.io (not docker.io)
Environment
openbao-helm/charts/openbao/templates/injector-deployment.yaml
Line 72 in b73f988
Chart values:
default chart values, as from values.yaml.
Additional context
The opendev/starlingx developer uses this patch to fix openbao 0.7.0:
https://review.opendev.org/c/starlingx/app-openbao/+/935703/17/helm-charts/upstream/openbao-helm/debian/deb_folder/patches/0003-Fix-agent-image-registry-in-injector-deployment.patch#25
The text was updated successfully, but these errors were encountered: