Add blog for implementing Kubernetes ConfigMap revisions with Pulumi and Argo Rollouts #15441
Conversation
…h Pulumi and Argo Rollouts This commit introduces a new blog post detailing the implementation of a custom ConfigMap revision system in Kubernetes using Pulumi's ConfigMapPatch and owner references. The solution addresses challenges faced during canary deployments, particularly with AWS Spot instances, by leveraging Kubernetes' garbage collection mechanism for automatic cleanup of ConfigMaps. Key highlights: - Overview of the problem with existing ConfigMap behavior during canary deployments - Detailed explanation of the solution using owner references and ConfigMapPatch - Code examples demonstrating the implementation - Benefits of the approach, including revision control and canary safety Additionally, a meta image for the blog post has been added.
|
@matanbaruch Deepest apologies for this PR sitting for so long without any followup. I've alerted a few folks internally to your post and you should see some action on it soon. |
Any update on this? |
adamgordonbell
left a comment
adamgordonbell
left a comment
There was a problem hiding this comment.
Sorry on the delay. If we can bump the publish date and make the description of the replacement value a bit more precise, then lets publish it.
content/blog/kubernetes-configmap-revisions-with-pulumi/index.md
Outdated
Show resolved
Hide resolved
content/blog/kubernetes-configmap-revisions-with-pulumi/index.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Adam Gordon Bell <[email protected]>
Co-authored-by: Adam Gordon Bell <[email protected]>
@adamgordonbell Done |
|
@adamgordonbell Do we know why it failed? |
|
@matanbaruch nothing that is your issue. Merged! Thanks for your contribution! |
4 participants
This PR introduces a new blog post detailing the implementation of a custom ConfigMap revision system in Kubernetes using Pulumi's ConfigMapPatch and owner references. The solution addresses challenges faced during canary deployments, particularly with AWS Spot instances, by leveraging Kubernetes' garbage collection mechanism for automatic cleanup of ConfigMaps.
Key highlights:
Additionally, a meta image for the blog post has been added.