Skip to content
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

injector image registry value used for agentImage image registry #31

Open
michel-thebeau-WR opened this issue Jan 10, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@michel-thebeau-WR
Copy link

michel-thebeau-WR commented Jan 10, 2025

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:

  1. Install chart, etc
  2. Observe that inject pod config AGENT_INJECT_VAULT_IMAGE value is incorrect (docker.io instead of quay.io for registry)
  3. 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)

Environment

  • Kubernetes version:
    • 1.29.2
    • integrating openbao into opendev/starlingx
  • openbao-helm version: tag 0.7.0;
  • and observed on openbao-helm main branch:
    value: "{{ .Values.injector.image.registry | default "quay.io" }}/{{ .Values.injector.agentImage.repository }}:{{ .Values.injector.agentImage.tag }}"

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant