GitOps centers itself around a version control system such as git to control the software delivery lifecycle. Leverage a git repo as a source of truth for changes and easily auto-sync changes to Kubernetes clusters. You can have confidence that changes managed through git are active within a Kubernetes environment.
What are Pipelines as Code?
Pipelines as Code are programmatic ways of defining and executing software delivery. The build, test, and deployment of applications should be treated as code.
How Harness uses Pipelines as Code.
The Harness Platform is backed by configuration-as-code. All aspects of the Harness Platform can be saved as configuration-as-code so your pipelines are accessible as code. The Harness Platform supports a bi-directional Git Sync, so changes made in a Source Code Management [SCM] solution or vice versa in the Harness Platform are represented as code.
Ruckus Networks leveraged Harness GitOps and Pipeline as Code, allowing developers to manage pipeline, service, environment, Helm, and Kubernetes configuration all in one place as code. All pipelines can be version-controlled and managed like code in any Git repository.
GitOps has picked up momentum recently and has been garnering participation in the CNCF. Learn how to leverage GitOps to supercharge your CI/CD pipelines using a Pipelines as Code approach.
What is Infrastructure as Code?
Infrastructure as Code or IaC is the administration and management of infrastructure through code vs physical configurations. Examples of IaC are Chef, Puppet, Terraform, and CloudFormation.
How Infrastructure as Code relates to Harness.
Harness has the ability to interact and manage with several infrastructure-as-code providers. As part of a modern deployment, infrastructure is provisioned at deployment time. Harness can orchestrate popular infrastructure-as-code providers such as Terraform and CloudFormation.