Helm install in certain order

by

Helm collects all of the resources in a given Chart and it’s dependencies, groups them by resource type, and then installs them in the following order (see here – Helm 2.10):

  1. Namespace
  2. ResourceQuota
  3. LimitRange
  4. PodSecurityPolicy
  5. Secret
  6. ConfigMap
  7. StorageClass
  8. PersistentVolume
  9. PersistentVolumeClaim
  10. ServiceAccount
  11. CustomResourceDefinition
  12. ClusterRole
  13. ClusterRoleBinding
  14. Role
  15. RoleBinding
  16. Service
  17. DaemonSet
  18. Pod
  19. ReplicationController
  20. ReplicaSet
  21. Deployment
  22. StatefulSet
  23. Job
  24. CronJob
  25. Ingress
  26. APIService

During uninstallation of a release, the order is reversed (see here).

Following this logic, in your case when your Job resource is created, both the Secret and the ConfigMap will already be applied, but Helm won’t wait for the Job to complete before applying the Deployment.
If you split your Chart to two parts (1-4, 5) and install them sequentially you would still have the problem of the Deployment being possibly applied before the Job is completed.
What I would suggest is splitting your Chart to two parts (1-3, 4-5), in which the the Job has a pre-install hook, which would make sure it completes before your Deployment is applied.

More Related Contents:

  1. How to pull environment variables with Helm charts
  2. pod has unbound PersistentVolumeClaims
  3. How do I access the Kubernetes api from within a pod container?
  4. Expose port in minikube
  5. How kubectl port-forward works?
  6. chown: changing ownership of ‘/data/db’: Operation not permitted
  7. What’s the best way to share/mount one file into a pod?
  8. Mount local directory into pod in minikube
  9. Restart pods when configmap updates in Kubernetes?
  10. Invalid x509 certificate for kubernetes master
  11. Can a PVC be bound to a specific PV?
  12. How to merge kubectl config file with ~/.kube/config?
  13. Connect to local database from inside minikube cluster
  14. Is it possible to Autoscale Akka
  15. Minikube expose MySQL running on localhost as service
  16. Allow scheduling of pods on Kubernetes master?
  17. Adding insecure registry in containerd
  18. Namespace “stuck” as Terminating, How I removed it
  19. no matches for kind “Deployment” in version “extensions/v1beta1”
  20. How to rolling restart pods without changing deployment yaml in kubernetes?
  21. How to schedule pods restart
  22. What is the difference between a pod and a deployment?
  23. Restart container within pod
  24. Can I set custom ports for a Kubernetes ingress to listen on besides 80 / 443?
  25. How do I set ulimit for containers in Kubernetes?
  26. Is there a way to add arbitrary records to kube-dns?
  27. Kubernetes: Routing non HTTP Request via Ingress to Container
  28. gcloud ingress loadbalancer / static ip
  29. How to Enable KubeAPI server for HPA Autoscaling Metrics
  30. How to know a Pod’s own IP address from inside a container in the Pod?

Leave a Comment