63 lines
2.8 KiB
Markdown
63 lines
2.8 KiB
Markdown
---
|
|
title: "Build Your Golden Path Construction Playbook: A Maturity-First Implementation Approach"
|
|
weight: <index of talk on the day>
|
|
tags:
|
|
- platformengineeringday
|
|
---
|
|
|
|
<!-- {{% button href="https://youtu.be/rkteV6Mzjfs" style="warning" icon="video" %}}Watch talk on YouTube{{% /button %}} -->
|
|
{{% button href="https://hosted-files.sched.co/colocatedeventseu2026/7c/golden-path-implementation-atul-kubeconeu-26compressed.pdf?_gl=1*xrtp7z*_gcl_au*NDQ0MzAwNDQuMTc3NDAyNzk5NQ..*FPAU*NDQ0MzAwNDQuMTc3NDAyNzk5NQ.." style="tip" icon="person-chalkboard" %}}Slides{{% /button %}}
|
|
{{% button href="https://colocatedeventseu2026.sched.com/event/2DY6g" style="error" icon="calendar" %}}Sched Link{{% /button %}}
|
|
<!-- {{% button href="https://github.com/graz-dev/automatic-reosurce-optimization-loop" style="info" icon="code" %}}Code/Demo{{% /button %}} -->
|
|
<!-- {{% button href="https://cloudnativeplatforms.com" style="info" icon="link" %}}Website/Homepage{{% /button %}} -->
|
|
|
|
A lot of people have talked about golden paths for platforms since KubeCon EU 2022 (including the speaker of this session).
|
|
Most of these talks only tell you why you need this and about the value-add but not about the journey.
|
|
|
|
## Baseline
|
|
|
|
- Golden Path: A supported opinioated way to build and deploy software that makes the right wa the easiest way while not beina a mandate but a product and roducing decision fatique
|
|
- Intro analogy: The bikepaths are the golden path of amsterdam: Strongly oppinionated and self-service, safe by default and built progressivly -> Reduces cognitive load
|
|
- The golden path always related to the journey across the platform maturity model (our lord and savior of the day)
|
|
|
|
## How do we start (and continue)
|
|
|
|
### Phase 0: Chaos
|
|
|
|
- Every team has their own deployment script (or just `kubectl apply -f`)
|
|
- Same goal, 0 consistency, no standards
|
|
- Deploy latest, no limits, ....
|
|
|
|
### Phase 1: Standardize
|
|
|
|
> Unify existing scripts
|
|
|
|
- One script, one template, every team -> Teams just insert thgeir image, name, ...
|
|
- Resource Limits, healthchecks, labels -> Everything enforced by default
|
|
- Same command -> Consistent output every time
|
|
|
|
### Phase 2: Validate + make it scalable
|
|
|
|
> Improve the previously unified script
|
|
|
|
- Config driven -> Declarative YAML instead of cli arguments
|
|
- Reject bad inputs before they touch the cluster
|
|
- Environment-aware defaults for dev, staging and prod
|
|
|
|
### Phase 3: GitOps
|
|
|
|
> The script still handels creation/validation we only move the apply
|
|
|
|
- `git push` instead of `kubectl apply`
|
|
- Tool watches the repo and deploys automaticly
|
|
- Every deployment is a commit -> Audit trail and rollbacks
|
|
|
|
### Phase 4: IdP
|
|
|
|
- Same validation and push logic
|
|
- Replace the script + template with a form -> No more YAML or CLI needed
|
|
- Any developer can use it and deploy
|
|
|
|
## Journey overview
|
|
|
|
TODO: Steal from slides |