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

GitOps support #259

Open
jkleinlercher opened this issue Mar 1, 2023 · 2 comments
Open

GitOps support #259

jkleinlercher opened this issue Mar 1, 2023 · 2 comments

Comments

@jkleinlercher
Copy link

Does this work also when those resources are managed by a gitops agent like fluxcd or argocd? If not, what needs to be done to make it work? I think this is really a good project!

@davidebianchi
Copy link
Member

Hi @jkleinlercher, really interesting use case!
At the moment we have not experience with kube-green working with argocd and fluxcd.
A possible way could be set some sync window to exclude the specific hours to the sync workload of the GitOps operators.

There is this comment of @victorboissiere #142 (comment), which uses Argo and could be useful to use kube-green in this context.

This is a really interesting and increasingly widespread use case, so I think we should add some guideline and documentation about this, and go deep to know if there is a way to improve integration.

@ziouf
Copy link

ziouf commented Feb 8, 2024

I think argocd or fluxcd should not manage replica count in manifests (not always) like said in argocd best practices

https://argo-cd.readthedocs.io/en/stable/user-guide/best_practices/#leaving-room-for-imperativeness

Same issue with suspend field of CronJobs

This should be a prerequisite for enabling downscaling

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

3 participants