-
Notifications
You must be signed in to change notification settings - Fork 10
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
Charm is deducing the executor tag based on the tag of the controller image #115
Labels
bug
Something isn't working
Comments
orfeas-k
added a commit
that referenced
this issue
Aug 29, 2023
Add executor-image field in the charm's config file in order to avoid deducing it based on the tag of the container image. Closes #115
We need to merge this #125 before proceeding with canonical/bundle-kubeflow#680. |
orfeas-k
added a commit
that referenced
this issue
Aug 29, 2023
Add executor-image field in the charm's config file in order to avoid deducing it based on the tag of the container image. Closes #115
i-chvets
added a commit
that referenced
this issue
Sep 22, 2023
i-chvets
added a commit
that referenced
this issue
Sep 27, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Charm is deducing what executor image to use based on the tag of the controller image. This is error prone and expects a specific tagging for both images.
We should instead have this whole image configurable, via the
config.yaml
file. This also limits our airgapped story, since we can't define a different registry for the image.argo-operators/charms/argo-controller/src/charm.py
Lines 82 to 85 in 0d80f2a
The text was updated successfully, but these errors were encountered: