This post is the 6th in our Kubernetes training series, providing DevOps engineers with an introduction to Docker, Kubernetes, and Octopus.
This video introduces many Octopus concepts such as:
- Environments
- Certificates
- Targets
- Workers
It then demonstrates how to integrate Octopus with a Kubernetes cluster and perform a deployment.
If you don’t already have an Octopus account, you can start a free trial.
You can work through the series using the links below.
- Getting started with Docker
- Installing a development Kubernetes cluster
- Creating Docker containers
- Creating Kubernetes resources
- Creating Kubernetes services
- Deploying to Kubernetes with Octopus
- Multi-environment deployments
- Installing a dashboard
- Observing deployment strategies
- Blue/green deployment strategy
- ConfigMaps and Secrets
- ConfigMaps and Secrets demo
- Role Based Access Control
- Role Based Access Control demo
- Ingress and Ingress Controllers
- Ingress and Ingress Controllers demo
- Deploy Google’s Online Boutique microservice stack in Octopus
Resources
Learn more
If you’re looking to build and deploy containerized applications to AWS platforms such as EKS and ECS, the Octopus Workflow Builder populates a GitHub repository with a sample application built with GitHub Actions workflows and configures a hosted Octopus instance with sample deployment projects demonstrating best practices such as vulnerability scanning and Infrastructure as Code (IaC).
Happy deployments!
Related posts
The State of GitOps report: Exploring effective GitOps
Key insights from the first State of GitOps report based on 660 survey responses. Learn how high-performing teams achieve better software delivery, increased reliability, and stronger security through 6 essential GitOps practices.
Inside DevOps with Oluwateniola Olubowale from United Capital
A series where we share lessons learned from those on the frontlines of DevOps. This post features Oluwateniola Olubowale, DevOps Engineer at United Capital.
Beyond skeleton pipelines: who owns your software pipeline?
Most teams have basic CI/CD pipelines that work but never improve. Without clear ownership, these 'skeleton pipelines' become bottlenecks instead of enablers.
