Skip to content
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

patch deployments on every fire #66

Open
matti opened this issue Oct 3, 2018 · 2 comments
Open

patch deployments on every fire #66

matti opened this issue Oct 3, 2018 · 2 comments
Labels
enhancement New feature or request

Comments

@matti
Copy link
Contributor

matti commented Oct 3, 2018

currently needs to have some build id or timestamp as a variable to make pods roll

@jnummelin jnummelin added the enhancement New feature or request label Oct 11, 2018
@jnummelin
Copy link
Contributor

Not sure if Mortar can actually do this. The issue is that mortar does not really understand anything about the resources themselves. It only understands the higher level Kube stuff, metadata, labels, annotations, etc.. AFAIK changing some labels or annotation on the object level (in this case on a Deployment metadata) will not make pods roll. Mortar would need to understand the inner workings of Deployment and be able to change the deployments spec.template.metadata...

@matti
Copy link
Contributor Author

matti commented Oct 11, 2018

Sure it can, just parse the resources, see if it is a deployment and add some stuff to spec.template.metadata

I'm doing this manually for every single deployment I have and the stuff is always the same.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants