Intro to GitOps & Tools
By Shivlal Sharma
© 2022 Cloud Native Computing Foundation
2
Shivlal Sharma
DevOps Engineer @Quicko
● Community Builder @PYPRO
● Co-organiser @Docker Ahmedabad, @CNCF
Ahmedabad
● Write blogs @CommBlogs
@whoami
© 2022 Cloud Native Computing Foundation
3
GitOps a new fish?
It was in the lake..!
● You were using it before it came to trending.
● DevOps practices + IaaC(Infra as a code) = GitOps
● DevOps Practices like Continuous building and Continuous
deploying.
● IaaC tasks like
○ Terraform for infrastructure provisioning
○ Ansible playbooks for defining configurations
○ Kubectl for container orchestration using mainfest
© 2022 Cloud Native Computing Foundation
4
DevOps Practices
© 2022 Cloud Native Computing Foundation
5
Lemme give you one task..
© 2022 Cloud Native Computing Foundation
6
Create one instance and setup Apache on it.. Simple
IaaC(Infrastructure as Code)
© 2022 Cloud Native Computing Foundation
7
IaaC automation
© 2022 Cloud Native Computing Foundation
8
How GitOps works?
© 2022 Cloud Native Computing Foundation
9
● Two kind of deployment strategy : Push and Pull based
● Push: When someone push changes to the repo, it invokes the pipeline and pushes the
changes to the Infrastructure
● Pull: We instruct the infrastructure to actively look up for the changes made to the repo, after
it find out changes made to the repo it pulls the changes and apply it internally.
How GitOps work?
© 2022 Cloud Native Computing Foundation
10
GitOps tools
© 2022 Cloud Native Computing Foundation
11
How these tools works?
© 2022 Cloud Native Computing Foundation
12
Advantages:
© 2022 Cloud Native Computing Foundation
13
● Follows “Git is the single source of truth, when it comes to infrastructure point of view”.
● Easily track changes in the infrastructure, due to versioning.
● More secure due to role based access
● Not much complex
Disadvantages:
© 2022 Cloud Native Computing Foundation
14
● A proliferation of repositories
● No help for secrets management, as number of repositories grows it is hard to manage
secrets.
Any Questions?
Mat pucho yarr 😔
© 2022 Cloud Native Computing Foundation
15
© 2022 Cloud Native Computing Foundation
16
Connect with me.
Thank you

GitOps and Its tools.pptx

  • 1.
    Intro to GitOps& Tools By Shivlal Sharma
  • 2.
    © 2022 CloudNative Computing Foundation 2 Shivlal Sharma DevOps Engineer @Quicko ● Community Builder @PYPRO ● Co-organiser @Docker Ahmedabad, @CNCF Ahmedabad ● Write blogs @CommBlogs @whoami
  • 3.
    © 2022 CloudNative Computing Foundation 3 GitOps a new fish?
  • 4.
    It was inthe lake..! ● You were using it before it came to trending. ● DevOps practices + IaaC(Infra as a code) = GitOps ● DevOps Practices like Continuous building and Continuous deploying. ● IaaC tasks like ○ Terraform for infrastructure provisioning ○ Ansible playbooks for defining configurations ○ Kubectl for container orchestration using mainfest © 2022 Cloud Native Computing Foundation 4
  • 5.
    DevOps Practices © 2022Cloud Native Computing Foundation 5
  • 6.
    Lemme give youone task.. © 2022 Cloud Native Computing Foundation 6 Create one instance and setup Apache on it.. Simple
  • 7.
    IaaC(Infrastructure as Code) ©2022 Cloud Native Computing Foundation 7
  • 8.
    IaaC automation © 2022Cloud Native Computing Foundation 8
  • 9.
    How GitOps works? ©2022 Cloud Native Computing Foundation 9 ● Two kind of deployment strategy : Push and Pull based ● Push: When someone push changes to the repo, it invokes the pipeline and pushes the changes to the Infrastructure ● Pull: We instruct the infrastructure to actively look up for the changes made to the repo, after it find out changes made to the repo it pulls the changes and apply it internally.
  • 10.
    How GitOps work? ©2022 Cloud Native Computing Foundation 10
  • 11.
    GitOps tools © 2022Cloud Native Computing Foundation 11
  • 12.
    How these toolsworks? © 2022 Cloud Native Computing Foundation 12
  • 13.
    Advantages: © 2022 CloudNative Computing Foundation 13 ● Follows “Git is the single source of truth, when it comes to infrastructure point of view”. ● Easily track changes in the infrastructure, due to versioning. ● More secure due to role based access ● Not much complex
  • 14.
    Disadvantages: © 2022 CloudNative Computing Foundation 14 ● A proliferation of repositories ● No help for secrets management, as number of repositories grows it is hard to manage secrets.
  • 15.
    Any Questions? Mat puchoyarr 😔 © 2022 Cloud Native Computing Foundation 15
  • 16.
    © 2022 CloudNative Computing Foundation 16 Connect with me.
  • 17.