Kostis Kapelonis
Developer Advocate at Octopus Deploy
Athens, Greece
Actions
Kostis is a software engineer/technical-writer dual class character. He lives and breathes automation, good testing practices and stress-free deployments with GitOps. He is also a member of the Argo team focusing mainly on Argo Rollouts and Argo CD
Links
Badges
Area of Expertise
Take the best of both worlds using Terraform and Argo CD
Stop me if you have heard this before. You finally decided to adopt Argo CD (and possibly Crossplane) for your new developer platform. But you don't really know how your existing Terraform process will now look. How do you pass information from Terraform to Argo CD? How you inject ARNs from the cloud provider to Argo CD applications? What about database URLs and secrets?
Fear not! In this talk we will see not one, not two, but three (3) ways to combine Argo CD and Terraform/OpenTofu in a single and cohesive solution for all your internal platform needs.
Stop deploying blind! Using Observability and Argo Rollouts to Light the Way
Are you tired of looking at metrics and logs after each deployment? Do you learn about failed deployments from unhappy customers? Did you always want to deploy on Friday afternoon and go straight to the pub?
Many teams perform “blind” deployments without any real insight into what will be affected by the new application version. Consequently, they don’t have enough data to understand the blast radius of a release and whether to decide if it was successful or not.
Even companies that have several metrics in place, don’t always use them in an automated manner. Wouldn’t it be great if you could see user behavior with new features in real time and identify performance bottlenecks before a full release?
In this talk, we will focus on common scenarios regarding Argo Rollouts and observability metrics, we will explain:
- Minimum requirements in terms of tools and metrics/traces/logs
- Well-known observability use cases
- Common automation pitfalls
- RED/USE metrics tradeoffs
Perform Laser Focused Deployments by Deciding in Advance the Blast Radius
Progressive Delivery is an advanced deployment method that allows for zero-downtime application releases. Argo Rollouts is a Kubernetes controller that allows you to adopt progressive delivery in the form of blue/green and canary deployments.
We see a lot of teams that choose an arbitrary number of clients that access the new version of a canary. Yes, it is very easy to send only 10% of the traffic to the new version of a Kubernetes deployment. But sometimes you want to choose WHICH 10% sees the new traffic.
In this talk we will see several approaches on pinning down specific clients to the old or new version and advanced scenarios for sending canary traffic only to a specific subset of users such as internal employees or customers who have expressed their interest on seeing brand new releases as soon as possible.
Autoscaling and Progressive Delivery - a match made in heaven
Argo Rollouts is a Kubernetes controller for Progressive Delivery deployments. In the most basic scenario, Argo Rollouts supports advanced Kubernetes deployments such as blue/green and canaries. While this is great, the main selling point of a Kubernetes cluster is the autoscaling facilities it offers. Can you use canary deployments while still taking advantage of Horizontal (and Vertical) autoscalers?
The answer is yes! In this talk, we will see how you can combine these two worlds - progressive delivery and autoscaling - and explain how to perform advanced deployments even in the presence of autoscalers.
Kostis Kapelonis
Developer Advocate at Octopus Deploy
Athens, Greece
Links
Actions
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top