Post #1473438

The work platform I’m building: Kubernetes for the primary substrate. Developers will speak k8s manifests as their main mechanism to declare what they want. That runs on EKS Auto-mode, so we have less to administer. Crossplane for AWS resource provisioning. We were initially hoping to go with direct access, but the fact that the resources aren’t namespaced, means we had to go with more compositions. Kyverno for policy enforcement. This is primarily to get cost attribution tags on things, but also to generally help folks do the right thing. Backstage (Q2) will layer a UI on top of this so more people can see what it looks like. The idea is that this is a central jumping off point for any service related “what does this even do?” questions you have. Builds happen through github actions. They produce a candidate artifact for production in an ECR repo and trigger the pipeline. Pipeline is done via Tekton. We went with Teuton rather than Argo because it’s important to me that there’s a logical progression of left to right when it comes to deploying software. The gitops model where you do one portion of the workflow then commit back to your own repo to do the next part is disjoint and confusing (to me). All telemetry is done via Otel. This currently goes into New Relic, but may not always. All in all, it's a pretty exciting project which will have big impact to the company.