Read on Twitter
THREAD: What is GitOps?
Is this something that you should learn?
Let's dive into it.
Is this something that you should learn?
Let's dive into it.
1/10
The idea behind GitOps is straightforward:
1. Scripts that create update, delete, etc. infrastructure are saved in GIT.
2. The state of your infrastructure is saved in GIT.
3. You have automation to trigger all your scripts.
Let's see an example.
The idea behind GitOps is straightforward:
1. Scripts that create update, delete, etc. infrastructure are saved in GIT.
2. The state of your infrastructure is saved in GIT.
3. You have automation to trigger all your scripts.
Let's see an example.
2/10
Let's deploy an app with a single replica:
1. Commit the Deployment definition in GIT
2. Execute the script to deploy
3. Done
How is this new?
Surely you do this already!
The devil is in the details, though.
Let's deploy an app with a single replica:
1. Commit the Deployment definition in GIT
2. Execute the script to deploy
3. Done
How is this new?
Surely you do this already!
The devil is in the details, though.
3/10
What do you do if you want to scale your deployment?
In GitOps, the state of the infrastructure is stored in GIT.
So you change your Deployment definition in GIT and apply the change to production.
What about autoscaling?
What do you do if you want to scale your deployment?
In GitOps, the state of the infrastructure is stored in GIT.
So you change your Deployment definition in GIT and apply the change to production.
What about autoscaling?
4/10
The autoscaler should not increase the number of replicas live!
It should increment the number of replicas in GIT.
Then, the change should be redeployed to production.
In GitOps, every change goes through GIT.
Always.
But why?
The autoscaler should not increase the number of replicas live!
It should increment the number of replicas in GIT.
Then, the change should be redeployed to production.
In GitOps, every change goes through GIT.
Always.
But why?
5/10
Imagine deleting your infrastructure by mistake
If you have the full state in GIT, you can trigger your scripts and recreate the same setup as before!
When you rebuild the infra, even the number of replicas set by the autoscaler are set correctly.
Powerful, isn't it?
Imagine deleting your infrastructure by mistake
If you have the full state in GIT, you can trigger your scripts and recreate the same setup as before!
When you rebuild the infra, even the number of replicas set by the autoscaler are set correctly.
Powerful, isn't it?
6/10
There are other benefits:
- You have an audit log of all the changes: the GIT history
- You only need to learn GIT to deploy
- You can roll back to any point in time! (just a GIT revert!)
There are other benefits:
- You have an audit log of all the changes: the GIT history
- You only need to learn GIT to deploy
- You can roll back to any point in time! (just a GIT revert!)
7/10
Do you need CI/CD to do GitOps?
No.
You can manually trigger deployments yourself.
But it's boring, and automation goes a long way to help.
You should checkout @argoproj #FluxCD @jenkinsxio
Do you need CI/CD to do GitOps?
No.
You can manually trigger deployments yourself.
But it's boring, and automation goes a long way to help.
You should checkout @argoproj #FluxCD @jenkinsxio
8/10
Does GitOps work only with Kubernetes?
No.
You can apply GitOps to any project!
As long as you hold your infrastructure state in GIT and have scripts to apply changes, you can use anything you want.
Does GitOps work only with Kubernetes?
No.
You can apply GitOps to any project!
As long as you hold your infrastructure state in GIT and have scripts to apply changes, you can use anything you want.
9/10
If you want to learn more about GitOps:
- https://www.gitops.tech/
- https://github.com/weaveworks/awesome-gitops
- https://deploy.live/blog/a-year-with-gitops-in-production/
GitOps was invented by the clever people at @weaveworks â you can check out their website here https://www.weave.works/technologies/gitops/
If you want to learn more about GitOps:
- https://www.gitops.tech/
- https://github.com/weaveworks/awesome-gitops
- https://deploy.live/blog/a-year-with-gitops-in-production/
GitOps was invented by the clever people at @weaveworks â you can check out their website here https://www.weave.works/technologies/gitops/
10/10
You can also tune-in to @Salaboy's webinar on Jenkins X (a CI/CD tool designed for GitOps): https://event.on24.com/wcc/r/2451691/ED89B0E41E3B88C04ABF98F34E67128A/1210267?partnerref=learnk8s
Salaboy will demonstrate GitOps end-to-end with a live demo!
@linode is hosting the event!
What should the next thread be about? Let me know!
You can also tune-in to @Salaboy's webinar on Jenkins X (a CI/CD tool designed for GitOps): https://event.on24.com/wcc/r/2451691/ED89B0E41E3B88C04ABF98F34E67128A/1210267?partnerref=learnk8s
Salaboy will demonstrate GitOps end-to-end with a live demo!
@linode is hosting the event!
What should the next thread be about? Let me know!
