GitOpsCon Europe 2022

gitops in Kubernetes is a simple but powerful workflow: declare the deployments' desired state in git and an agent (often Flux) should pick it up and reflect the state in the cluster automatically. However, this approach allows for the propagation of issues by "broken" versions of software, which could be avoided with a progressive rollout and enforcement of policies around those. In this talk we propose the use of an update and policy manager – Nebraska – as a complement to gitops. Nebraska allows to set up policies to be met for granting updates, and aggregates the data about update statuses. The integration is accomplished using a new Nebraska Update Agent (NUA), which controls Flux itself, automatically reports statuses, and has a minimal impact to the gitops users’ workflows. With NUA and flux, users can manage new deployment rollouts in a more controlled way, by defining policies for updates, for example: update just one cluster at a time and halt all updates if one cluster fails to update; update cluster only during certain hours; see a global view of the updates’ statuses and drill down to any error reports. Hence, tying gitops and policy-based updates in Kubernetes.

Click here to view captioning/translation in the MeetingPlay platform!

Implementing Preview Environments with GitOps in Kubernetes: how to spin up ephemeral environments on the fly at each Pull-requests for the delight of your team. Have you ever experienced a delayed-release because your Staging environment was broken by another feature? Ending up merging a non-production tested Hotfix branch to your Main branch? Preview environments are an answer to increasing velocity inside your team. Kubernetes combined with GitOps allow you to quickly create and destroy resources along with keeping a clear code history and infrastructure changes in Git. Using Bitbucket Pipelines for Continuous Integration and ArgoCD for declarative Continuous Delivery, we will go through different challenges you can encounter to deploy Preview environments such as Secrets management with Sealed Secrets, splitting repositories, and clearing resources to prevent further costs.

Click here to view captioning/translation in the MeetingPlay platform!

Progressive Delivery as you all know is controlled deployments to minimize the risk associated with service updates. Organizations use tools like ArgoRollouts to achieve Progressive delivery for individual services. Progressive delivery across microservices with dependencies is a challenge that many companies are working to solve. In this session, We will demonstrate how to use Argo Rollouts in achieving progressive rollouts & automated rollbacks across microservices in a dependency graph using capabilities such as automated analysis & custom webhook notifications. We will also discuss how to use your current complex multi-service monitoring queries in analysis and automate the entire deployment flow across microservices. Another important capability that we will present is ‘dry runs’ that will enable users to identify and validate possible automated rollbacks in production without actually doing rollbacks.

Click here  to view captioning/translation in the MeetingPlay platform!

With Kubernetes becoming more and more popular, so is managing clusters at scale. Applying GitOps principles with Flux simplifies provisioning clusters and managing workloads deployed onto them, including tenant and RBAC management. In this session I will demonstre a best practice approach towards GitOps with a management cluster handling the provisioning and further maintenance of clusters, tenants and workloads, employing the CNCF projects Flux, OPA Gatekeeper and the Kubernetes Cluster API sub-project. The benefits of such an approach are: * It creates a simplified way to declaratively define thousands of clusters and perform operations on those clusters * Makes it easy to have a multi-tenancy approach where each team or group of applications gets their own cluster or individual namespace on a certain cluster * Operations against clusters are fully audited and attributable, as reverting changes is hard.

Click here to view captioning/translation in the MeetingPlay platform!

Gone are the days of daisy chaining Jenkins Jobs together. With modern CI/CD tools pipelines are the new high ways. But unlike a driving a car, which you can only take down one road at a time. CI/CD pipleines have the power to run concurrent processes, across multiple lanes, to get to the same destination: Code in production, fast, reliably, and automatically. Join us for a review of Pipelines, CI/CD, and how to leverage tools to get jobs done with your GitOps workflows.

Click here to view captioning/translation in the MeetingPlay platform!