Grayson Adkins
04/01/2022, 12:28 AMHenning Jacobs
04/26/2022, 1:01 PMHow do you envision the DevEx for managing infrastructure resources and other dependencies?Everybody talks about infrastructure as code, so that's definitely what I would see for us. Currently we have AWS resources (CloudFormation) and Kubernetes manifests as YAML in the same repo as the application code. We do not use Helm or any advanced templating (just Mustache). Changes are applied via CI/CD when deploying a new version (CloudFormation update, kubectl "apply"). Some teams already use AWS CDK and I can foresee us adopting something higher-level (than YAML) going forward. There are some trade-offs between what is possible to customize locally vs. how to allow central changes across 200 teams. YAML is not so bad right now as we do automated PRs to change certain things as needed (e.g. Kubernetes API version updates needing changes). Full "code" can make this harder to achieve (interpreting turing-complete code from automated tools). We definitely strive to increase leverage, i.e. remove toil from engineers and move to centrally provided services incl. updates etc.
Henning Jacobs
04/26/2022, 1:11 PMWDYT about Backstages Golden Paths idea?Our developer portal ("Sunrise") is based on Backstage and I'm certainly a fan of golden paths. Currently we have so-called application templates (e.g. for Java Spring Boot app) in our developer portal so teams can get started easily. The idea is that our communities of practice (e.g. Kotlin or Python guild) provide such "golden path" application templates for the common use cases.
Henning Jacobs
04/26/2022, 1:17 PMHow do you deal with failure and debugging of infrastructure?That's always a tricky topic. Right now our Container Platform team is looped in when necessary, e.g. if some EC2 Kubernetes worker node behaves in a strange way (that happens from time to time on AWS). Teams have the possibility to subscribe to cluster updates (we have >160 Kubernetes clusters) and can also stop any ongoing cluster updates if they suspect some issues. The Container Platform team has inspection tools to check cluster health, e.g. networking etc and relies on Prometheus/ZMON/Grafana for monitoring. In general we follow a continuous delivery approach for any changes going to production Kubernetes clusters. There is some KubeCon talk about this --> We do not have advanced infrastructure debugging capabilities for engineering teams right now, but they can always request (automated, 4-eyes approval) cluster API access e.g. to start some Pod with Busybox or do port forwarding.
Hugo Pinheiro
05/02/2022, 5:42 PMKarolina JunÄytÄ
05/10/2022, 9:12 AMRaquel Pau Fernandez
05/11/2022, 8:48 AMRaquel Pau Fernandez
05/11/2022, 8:50 AMRaquel Pau Fernandez
05/13/2022, 9:41 AMKarolina JunÄytÄ
05/17/2022, 3:25 PMAndre Marcelo-Tanner
05/18/2022, 1:47 AMRaquel Pau Fernandez
05/18/2022, 10:04 AMAndrew Fong
05/18/2022, 10:05 AMAndrew Fong
05/18/2022, 10:06 AMRavi Kotecha
05/18/2022, 10:15 AMjonny s.
05/18/2022, 10:16 AMAndrew Fong
05/18/2022, 10:19 AMRaquel Pau Fernandez
05/18/2022, 1:08 PMAndy McKay
05/19/2022, 11:58 AMMitesh Sharma
05/20/2022, 2:47 PMMarc Barry (enclave.io)
05/20/2022, 2:48 PMRaquel Pau Fernandez
05/25/2022, 1:50 PMKarolina JunÄytÄ
05/26/2022, 10:05 AMGobiraj Vadivelrajan
05/30/2022, 5:11 PMKarolina JunÄytÄ
06/02/2022, 1:34 PMahn heesuk
06/06/2022, 7:51 AMGitOps
+ ArgoCD
to deploy to a Kubernetes cluster after commits and merges in Git.
This works fine, but we want to take the user experience to the next level beyond committing to Git every time.
Using the Internal Developer Portal, users want to be able to skaffolding and management of the application they want with a click.
But the difficulty I feel here is the Git Layer.
Since GitOps is distributed using the Git Repository, all changes must occur in the Git Repo. (Single Source of Truth)
If you change the value (eg. replicas, helm value...) on the dashboard, you also need to commit it to Git. What is the best practice in this case?
1. When a change value is triggered in the dashboard, the operator or API server commits it to Git on its behalf.
2. You cannot modify the dashboard after scaffolding, only the Read Only mode is allowed.
If you want to change the value, you have to edit it directly in Git.
Anyone running GitOps and dashboards together? I'm curious about your experience. š¤Michael Butak
06/06/2022, 4:26 PMEelko
06/07/2022, 9:12 AMAndrew Fong
06/07/2022, 1:27 PMAndrew Fong
06/07/2022, 1:27 PM