Is there anyway to do a rolling deploy of a @kubernetesio deployment using a configmap when deploying with @HashiCorp Terraform?
Show this thread
-
Seems like there’s no easy way in K8s to apply configmap or secret changes for fear that it would break running pods. You have to manually orchestrate a rolling deployment update. Since there’s no API for that, Terraform can’t handle it, afaict.
Show this thread
Create a new ConfigMap and update the reference in the Deployment. https://github.com/kubernetes/kubernetes/issues/22368 …
-
-
Agree -- sometimes a configmap/secret is a "child object" to the deployment and sometimes it isn't. YAML management/template/config system can help to represent when it is.
-
Ok so replacing the configmap seems reasonable manually, provided the deployment handles the rolling update. But it doesn’t seem easy with the Terraform provider. You’d have to generate a new name only when the config changes... maybe with a random_id resource.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.