GITHUB_REPO

GITHUB_PAT

GITHUB_USERNAME

DOCKERHUB_USERNAME

GitOps- Modern Operations for Cloud Native Applications.png

k8s.tar.gz

cluster-with-k3d

cluster-with-kind

cluster-with-k3d-versioning

cluster-k3d-github-flux

cluster-k3d-github

cluster-with-no-k3d

cluster-with-k3d-helm

cluster-with-k3d-helm-flux-cli

cluster-k3d-github-flux-helm

cluster-k3d-github-flux-helm-flagger

GitOps is an operational model that allows developers to accelerate the delivery of cloud-native applications that run on Kubernetes.

In this course, you’ll learn the essential principles behind GitOps and how to apply the operational model to modern cloud-native systems. The course provides a detailed description of the relationship between GitOps and technologies like Docker, Kubernetes, and Helm. You’ll gain hands-on experience managing containerized workloads that run on Kubernetes using Flux. Additionally, you’ll explore how GitOps is used to execute progressive delivery strategies with Flagger.

After completing this course, you’ll be prepared to manage the operations of systems using GitOps. You’ll be able to establish and manage the GitOps operational model for systems that run on Kubernetes. You’ll also understand how to install and configure tools like Flux and Flagger that improve your systems' stability and rate of change.

GitOps—Modern Operations for Cloud Native Applications

It allows a single resource to be applied to a Kubernetes cluster independent of other resources.

It allows developers who create software for Kubernetes and those who install it to work with multiple resources in a single overarching package with configuration that can be parameterized.

Helm provides native support for deployment and progressive delivery strategies with GitOps.

Helm supports the management of Kubernetes workloads using an imperative style configuration, providing developers that use GitOps with an alternative configuration approach.

What advantage does Helm provide when managing Kubernetes workloads?

What advantage does Helm provide when managing Kubernetes workloads?

Which Helm command is used to switch or change a release to a new version of a chart?

Which Helm command is used to switch or change a release to a new version of a chart?

It specifies the directory on the local workstation that contains a Helm chart, which will be applied by Flux to the cluster.

It specifies the directory within a `HelmRepository` that contains a Helm chart, which will be applied by Flux to the cluster. 

It specifies the directory within the `GitRepository` that contains a Helm chart, which will be applied by Flux to the cluster.

It specifies the namespace where the Helm chart will be installed on the cluster.

When creating a `HelmRelease` using the Flux CLI, what is the purpose of the `--chart` flag in the following command?
```  
flux create helmrelease helm-release \
  --interval=1m \
  --source=GitRepository/helm-git-source \
  --chart=./infrastructure/python-sample \
  --target-namespace=default \
  --values=/usercode/system/infrastructure/python-sample/version2-values.yaml \
  --export > ./educative-cluster/python-sample-helm-release.yaml
```

When creating a <code>HelmRelease</code> using the Flux CLI, what is the purpose of the <code>--chart</code> flag in the following command?
<pre><code>flux create helmrelease helm-release \
 --interval=1m \
 --source=GitRepository/helm-git-source \
 --chart=./infrastructure/python-sample \
 --target-namespace=default \
 --values=/usercode/system/infrastructure/python-sample/version2-values.yaml \
 --export &gt; ./educative-cluster/python-sample-helm-release.yaml
</code></pre>

It specifies the location of a values file on the local workstation that contains values which will be overridden in the Helm chart when applied by Flux to the cluster.

It specifies the location of a values file within the `GitRepository`. This file contains values that will be overridden in the Helm chart when applied by Flux to the cluster.

It specifies the location of a values file within a `HelmRepository`. The file contains values that will be overridden in the Helm chart when applied by Flux to the cluster.

What is the purpose of the `--values` flag in the following command when creating a `HelmRelease` using the Flux CLI?

```  
flux create helmrelease helm-release \
  --interval=1m \
  --source=GitRepository/helm-git-source \
  --chart=./infrastructure/python-sample \
  --target-namespace=default \
  --values=/usercode/system/infrastructure/python-sample/version2-values.yaml \
  --export > ./educative-cluster/python-sample-helm-release.yaml
```

What is the purpose of the <code>--values</code> flag in the following command when creating a <code>HelmRelease</code> using the Flux CLI?
<pre><code>flux create helmrelease helm-release \
 --interval=1m \
 --source=GitRepository/helm-git-source \
 --chart=./infrastructure/python-sample \
 --target-namespace=default \
 --values=/usercode/system/infrastructure/python-sample/version2-values.yaml \
 --export &gt; ./educative-cluster/python-sample-helm-release.yaml
</code></pre>

Chapter quiz

Chapter quiz

Quiz yourself on the skills required to manage Helm charts with Flux.

Introduction to GitOps

GitOps Principles

Architecting GitOps-based Systems

Project I: Hands-on GitOps

GitOps in Practice

Project II: Use GitOps with Flux

Continuous Delivery with GitOps

Using Flux with Helm

Advanced Deployment Models with Flagger

Wrapping up

Appendix

Quiz Yourself: Using Flux with Helm