Abstract: Kubernetes is hard and achieving deployment success on the first try is no small feat. All teams from Developers to DevOps and beyond need to have a basic understanding of the ins and outs of Kubernetes to complete the necessary tasks that each role requires to achieve fast, secure cloud-native deployments successfully.

Developers, DevOps, and Production teams are having to negotiate about who is responsible for new tasks related to cloud deployments. From heading YAML to create the necessary resources to validating and securing these manifest files to ensure they communicate correctly with Kubernetes, the list of things teams must know is ever-growing. This workshop will focus on leveraging Monokle, an open-source tool that streamlines the process of creating, analyzing, and deploying Kubernetes configurations by providing a unified visual tool for authoring YAML manifests, validating policies, and managing live clusters. We’ll also discover how to make sense of Helm charts and Kustomize overlays, including OPA validation in pipelines, incorporate GitOps actions, and create each type of YAML manifest needed for deployment to help teams seamlessly collaborate

In this intensive workshop, you’ll learn all of the basic steps needed to deploy to Kubernetes successfully by leveraging open-source technologies to make this happen.

Learn the following:

• Install a local K8s (out of scope)
• Install an application
• Use a PostgreSQL database with Helm
• See Helm output
• Create a simple application, easy to understand (really, really, really easy)
• Configure the application
• Create the image, use an existing one
• Create, debug, and implement OPA validation of the necessary YAML resource manifests for proper deployment to K8s using templates
• Deploy the application to K8s
• See how the application behaves in Production
• Cluster mode for shell logs and terminal access and graph view
• Git action and version storage in Git
• Create an overlay to Kustomize
• Store in git in a different branch
• Compare
• Compare the Kustomize output with existing things deployed in the cluster
• Compare the pre-Kustomize (git) with post-Kustomize

Blog of the speaker on the same topic:

• Sergio Medium: https://medium.com/@chargio

• Erdi Github: https://github.com/erdkse