Episode Details

🙌 My next course is coming soon! I've opened the waitlist for those wanting to go deep in GitHub Actions for DevOps and AI automation. I'm so thrilled to announce this course. The waitlist allows you to quickly sign up for some content updates, discounts, and more as I finish building the course. https://www.bretfisher.com/waitlist🍾

Bret is joined by Ravi Lachhman, Field CTO at Shipa, to discuss the basics of Shipa application and policy management, and show off the developer experience that Shipa brings to apps running on IaC and GitOps tools like ArgoCD,  Crossplane, Terraform, Kubernetes, and more.

Shipa is focused on the layer above the infrastructure where application developers can avoid other Kubernetes manifest tools like Helm or Kustomize, and create a cleaner contract between what their application needs are and how the infrastructure provides them.

If you've done Kubernetes YAML long enough, you know that it can get quite complex and verbose, and it requires both infrastructure and developer roles or knowledge to fully configure it. So you kind of got to know both worlds. But Shipa wants to fit in the middle somewhere, not replacing the infrastructure tools like Terraform or Crossplane, but rather working on top of them, providing an easier way to describe your apps from a dev's point of view and how they work on top of your infrastructure. It focuses on the application requirements, not necessarily how those requirements are implemented. Streamed live on YouTube on April 14, 2022.

Unedited live recording of this show on YouTube (Ep #166). Includes demos.

★Topics★
Shipa website
Shipa example
DevOps Days Atlanta

★Ravi Lachhman★
Ravi on Twitter

★Join my Community★
Best coupons for my Docker and Kubernetes courses

Chat with us on our Discord Server Vital DevOps

Homepage bretfisher.com

• (00:00) - DDT MAIN
• (00:03) - Intro
• (02:31) - Bret Custom Intro
• (05:01) - Main Show
• (05:41) - Introductions
• (06:03) - About Ravi
• (07:16) - Any advice for starting engineers?
• (10:16) - Never stop learning
• (11:48) - It's ok to get it wrong the first time
• (12:20) - It's crucial to create reproducible deployments
• (13:44) - Infrastructure-as-code
• (14:50) - Application-as-code vs Infrastructure-as-code
• (17:26) - Shipa is a two-part thing
• (18:38) - What does Shipa 'replace'?
• (21:24) - Is Shipa strictly designed for Kubernetes?
• (22:28) - One-line developer experience
• (25:58) - Bret was a diehard swarm fan
• (28:49) - How flexible is this?
• (30:50) - Docker can't make pants
• (31:38) - What Bret was hoping might be implemented
• (33:23) - Preparing for demo?
• (33:43) - Bret doesn't want to develop in Kubernetes
• (35:37) - Demo intro
• (36:08) - Crossplane
• (37:41) - Q: Shipa working through Crossplane?
• (38:02) - Q: How else can I adopt Shipa without Crossplane?
• (39:03) - Q: Shipa versions - on-prem and SaaS
• (44:42) - Question: Will it override the YAML of Kubernetes?
• (49:35) - Devs shouldn't handle so much infrastructure
• (50:39) - Where else can people get started?
• (51:06) - Q: OAM and OpenAPI
• (52:41) - Q: Is AAC similar to OpenAPI?