Closed igordrnobrega closed 1 year ago
@viveklak would love your thoughts on this?
Hey guys, any news on this? Because suddenly I see new behavior with what used to work with new k8s.helm.v3.Release
is now trying to delete the Ingress resource.
Kubernetes provider updated from 3.21.0
to 3.21.2
.
Thanks
Hey guys, Is any news on this?
Thanks
Hey guys,
is there any news on this? I've updated it to 3.22.1
and still have the same error.
Thanks
@igordrnobrega sorry for not responding sooner. Are you sure your provider is fully updated to 3.22.1? Existing resources have an embedded link to their provider version. If this is on an existing stack, you will want to update the package dependency (e.g. package.json) to v3.22.1 and then do a single pulumi up
.
FWIW it looks like the helm chart template in question uses kubernetes capabilities: https://github.com/actions-runner-controller/actions-runner-controller/blob/v0.20.2/charts/actions-runner-controller/templates/githubwebhook.ingress.yaml#L4 which has been fixed in v3.22.1 thanks to https://github.com/pulumi/pulumi-kubernetes/pull/2155
cc @lblackstone for further follow up if necessary.
Looks like this may have been fixed. Please let us know if you're still having the same problem and we can reopen.
What happened?
Deploying the chart for actions-runner-controller I found an odd behavior with the Chart deployment. When using
new k8s.helm.v3.Chart
withfetchOpts
it misses the Ingress resource, however, cloning the mentioned chart locally setting the same tag of release, and replacing thefetchOpts
topath
works - I get the Ingress resource to be created. Plus, usingnew k8s.helm.v3.Release
instead ofnew k8s.helm.v3.Chart
with the same options just changing thefetchOpts
to its respective equivalentrepositoryOpts
it also works - Ingress resource is there to be created.Steps to reproduce
Deploy the chart for actions-runner-controller using the following configuration:
You won't get the Ingress resource deployed:
Do the same deployment but instead of fetching from the repo, clone the mentioned chart locally, check it out to the same version, set up the
path
option, and runpulumi up
the resource will be created:Or, using
k8s.helm.v3.Release
instead ofk8s.helm.v3.Chart
also creates the Ingress resource:Expected Behavior
The Ingress resource is to be created in
new k8s.helm.v3.Chart
.Actual Behavior
When using
new k8s.helm.v3.Chart
I don't get the Ingress resource created.Output of
pulumi about
Plugins because we use a monorepo to our projects
Helm JIC
Additional context
IDK if it's important, but with helm command, it also works:
Where
values.yaml
it's just the same options in the mentioned configuration fornew k8s.helm.v3.Chart
.Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).