You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 22, 2022. It is now read-only.
This is an issue to discuss the integration of GitOps paradigm in overnode.
As a declarative way of deploying infrastructure, I think it would be nice to have some sort of GitOps operator, so you could do a Pull-Request on a git repo to update your YAML files, and then it gets automatically deployed with overnode up
The text was updated successfully, but these errors were encountered:
I guess PSA, as well as implementation perspective:
before that, testing, testing
you will shoot yourself in the head with that
don't deploy to prod with a half-assed gitops setup
(tldr you know the manual way if something ends up not working; with gitops you panic and make 10 commits with the message being 'testing push to prod, does it work now?')
Sorry, I don't understand Hebrew! But I get the point on the tradeoffs on using GitOps. If you don't do it right, it's way worse than just doing ops "by hand".
Good point on the rollover! command was just an example of a task to perform.
PS: I see, the earlier version video is in English, I will watch it when I have a bit of time :)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is an issue to discuss the integration of GitOps paradigm in overnode.
As a declarative way of deploying infrastructure, I think it would be nice to have some sort of GitOps operator, so you could do a Pull-Request on a git repo to update your YAML files, and then it gets automatically deployed with
overnode up
The text was updated successfully, but these errors were encountered: