This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Specifying automated containers in a HelmRelease #3143
Labels
Comments
austinbv
added
blocked-needs-validation
Issue is waiting to be validated before we can proceed
bug
labels
Jun 17, 2020
Running
|
austinbv
changed the title
Specifying automated containers for airflow helm
Specifying automated containers in a helm release
Jun 17, 2020
austinbv
changed the title
Specifying automated containers in a helm release
Specifying automated containers in a HelmRelease
Jun 17, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Describe the bug
We are running into a weird issue with the
HelmOperator
- We are trying to configure the automated deployments of custom images in the Airflow Helm Chart in thegitsync
containers andinitContainers
. We have added annotations to our helm release and it looks like the below. We are not seeing any logs about theinitContainer
orgitSync
and new images are not detected.Additional context
1.1.0
v1.16.8-eks-e16311
github
stable/airflow
Note, this is a direct copy of fluxcd/helm-operator#464 (comment) I was not sure which repo was correct as it's a feature of the helm operator but documentation for this feature is in this repo, and the code is in this repo https://github.com/fluxcd/flux/blob/master/pkg/cluster/kubernetes/resource/helmrelease.go. If I did anything wrong feel free to close the issue!
The text was updated successfully, but these errors were encountered: