-
Notifications
You must be signed in to change notification settings - Fork 163
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
Kubernetes job not being deployed #746
Comments
@LukeRH Hi! Thanks for your issue. First of all - I am not a member of FluxCD team, just curious to assist. Probably I had the same issue but have no clues. Could you please describe issue prettier and give more precise instructions to reproduce it? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi
I am installing and subsequently upgrading a helm chart but a job is not being deployed to the cluster. If i run helm get all i can see the job yaml but it is not being applied. If i install and upgrade the helm release manually everything works as expected it seems to be specific to Flux helm deployments.
For example this works:
helm install redis-cluster bitnami/redis-cluster --set "usePassword=false,cluster.nodes=9"
$ helm upgrade --timeout 600s redis-cluster --set "usePassword=false,cluster.nodes=10,cluster.update.currentNumberOfNodes=9,cluster.update.addNodes=true,cluster.init=false" bitnami/redis-cluster
but this does not when applied via flux cd
release.yaml
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
name: redis
spec:
timeout: 20m0s
chart:
spec:
version: "8.3.8"
values.yaml
usePassword: false
cluster:
nodes: 10
Then to upgrade
usePassword: false
cluster:
init: false
nodes: 12
replicas: 1
update:
addNodes: true
currentNumberOfNodes: 10
Please could you help?
The text was updated successfully, but these errors were encountered: