-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Setting Helm deployer imageStrategy.helm
does not have any effect
#2681
Comments
Wow, what an odysee trying to figure out the right combination of config values to get this working. Apparently, explicitly setting works
does not work
|
Thank you for filing this and sharing the working solution. I agree, this is not intuitive. At least we should document it more clearly but it looks like maybe we can get rid of the requirement to set |
Yes, that sounds like a good idea :) And |
I have similar situation to the one described here but when I try to apply the suggested workaround, the tag becomes the name of the image:
This is what helm is said to use:
So tag is the name of the image instead of being the actual tag. @aeneasr I am wondering why I get different behavior from yours.
|
Hi @aeneasr and @oscar-martin, I wonder if there's any way you can test #2772 and see if solves your issue. |
For me, this is fixed in @2772. Please reopen in case you disagree. Maybe there's more things to be fixed |
Expected behavior
Using
helm.ImageStrategy.helm: {}
should set the right repository name and tag forimage.repository
andimage.tag
when using the helm deployerActual behavior
It appears that #826 should have closed #360 . However, using
helm.ImageStrategy.helm: {}
does not work at all because neitherimage.repository
norimage.tag
are being overwritten - they just keep their defaults from the originalvalues.yaml
file.Seeing the skaffold.yaml file from below, I would expect:
console
to usegcr.io/ory-artifacts/console:<some-hash>-dirty
oathkeeper
to usegcr.io/ory-artifacts/oathkeeper:<some-hash>-dirty
However, that's not the case - the default values are being used instead:
console
usesgcr.io/ory-artifacts/console:stable
oathkeeper
usesoryd/oathkeeper:v0.17.1-beta.1
Information
Steps to reproduce the behavior
Not possible at the moment but happy to provide something if it speeds up the process.
The text was updated successfully, but these errors were encountered: