Zasady i wdrażanie GitOps

Welcome to GitOps! This lesson explores a powerful way to manage your infrastructure and applications.

GitOps is an operational framework that uses Git as the single source of truth for defining the desired state of your systems.

Think of it as 'Infrastructure as Code' (IaC) taken a step further, where Git is central to deployment and management.

GitOps stands on four key principles:

• Declarative: Systems are described using declarative configurations.
• Versioned & Immutable: The desired state is stored in Git, fully versioned.
• Pulled: Changes are 'pulled' by agents, not 'pushed' by CI.
• Continuously Reconciled: Agents continuously ensure the live state matches the desired state.

These principles ensure consistency, reliability, and auditability.

In GitOps, every change to your production environment starts with a change in your Git repository.

• Your Git repo holds the entire desired state of your system.
• No direct manual changes to servers or clusters are allowed.
• Git's history provides a complete, auditable trail of all changes.

This makes rollbacks and understanding changes much simpler.

Declarative means you describe what you want your system to look like, rather than how to get there.

Instead of a script that runs commands, you provide a configuration file. Here's a tiny example for a Kubernetes deployment:

Traditional CI/CD often 'pushes' changes to production. GitOps uses a 'pull' model.

• An operator (an agent) runs inside your cluster or environment.
• This operator continuously monitors your Git repository for changes to the desired state.
• When a change is detected, the operator pulls it and applies it.

This enhances security by reducing external access to your production environment.

The GitOps operator doesn't just apply changes; it continuously reconciles.

• It constantly compares the actual state of your system with the desired state defined in Git.
• If any drift is detected (e.g., someone manually scaled down a replica), the operator automatically corrects it.
• This ensures your system is always aligned with your version-controlled configuration.

Adopting GitOps brings significant advantages:

• Faster Deployments: Streamlined, automated processes.
• Improved Reliability: Consistent environments, fewer human errors.
• Easier Rollbacks: Revert to any previous state in Git.
• Enhanced Security: Audit trails, reduced direct access.
• Better Collaboration: All changes visible and reviewable in Git.

Several open-source tools help implement GitOps, especially for Kubernetes.

• Argo CD: A declarative, GitOps continuous delivery tool for Kubernetes. It offers a great UI to visualize deployments.
• Flux CD: Another popular GitOps tool, part of the Cloud Native Computing Foundation (CNCF). It focuses on Git-driven deployments and reconciliation.

These tools act as the "operator" that pulls changes and reconciles states.

Let's walk through a simplified GitOps workflow:

1. A developer modifies a configuration file (e.g., changes an image version) in their local repo.
2. The developer commits the change and pushes it to the central Git repository.
3. The GitOps operator (e.g., Argo CD) detects the change in the Git repo.
4. The operator pulls the new desired state and applies it to the target environment (e.g., Kubernetes cluster).
5. The operator continuously monitors to ensure the live state matches the desired state.

You've explored GitOps, a framework that brings the best of Git to operations.

We covered its four principles: Declarative, Versioned, Pulled, and Continuously Reconciled. By using Git as the single source of truth, GitOps enhances speed, reliability, and security in managing infrastructure and applications.

Keep exploring tools like Argo CD and Flux CD to see GitOps in action!