Argo Rollouts using blue green configmap

[sourceful-karlson]

Hi,

In our application, we would like to do hot swapping of a dataset.

This means that our blue green deployment, the only thing that we care about is change in configmap.

Is there a way in argo rollout for the blue to use a blue set of configmap and green to to use a green set of configmap?

[kostis-codefresh]

To the best of my knowledge this is not supported. Argo Rollouts references a deployment and not a configmap.

However you can easily do a workaround.

1. Deploy configmap1 and configmap2 on cluster (so both of them exist but with different name/values)
2. Create application container image v1 (that looks at configmap1) and container image v2 (that looks at configmap2)
3. Use Argo Rollouts normally for container images v1->v2

You could also have a single configmap which itself have v1-value and v2-value if you prefer that.

[sourceful-karlson]

Hi Kostis,

We have solve the problem by using a configmap generator that had the rollout using different configmap values

[sourceful-karlson]

No idea for them sorry, but Configmap should get you very far

[Dentrax]

Thanks. I'd be great if you could share a simple Rollouts resource example that i can combine with the kustomize config generator.

[showwin]

This document will help you. https://github.com/argoproj/argo-rollouts/blob/ddce67165b4832001d2ccb6d68798a9580ea9afe/docs/features/kustomize.md
Example code is here: https://github.com/argoproj/argo-rollouts/tree/ddce67165b4832001d2ccb6d68798a9580ea9afe/docs/features/kustomize/example.

[Dentrax]

Seems a bit hard and confusing to me. I still couldn't get the relation between Kustomization and ConfigMap/Secret/CRDs, what I want to do is replacement, not patch.

[kostis-codefresh]

@Dentrax I have written a guide for this problem https://codefresh.io/blog/progressive-delivery-for-kubernetes-config-maps-using-argo-rollouts/