…require deliberate design decisions that the community is still converging on. Looking ahead Our platform continues to evolve. Some of the areas we are actively developing: SPIRE/SPIFFE integration for workload identity…
…How development and rollout actually go As we move from development into rollout, the operational model already looks like any Kubernetes platform we have run before. Alerts are structural: policy bundle failed…
…To support this evolving ecosystem, we are actively feeding our customizations and tooling back as upstream contributions to the Mirantis k0smos projects, ensuring the wider community can continue to build upon this…
…The worst-case outcome of a compromised PR build is a malicious CI image landing in the development registry, which is the same blast radius any CI system that builds contributor code…
…You didn’t just build a cluster. You built the system that builds clusters. Feel free to check out more on the k0s and k0rdent community The stack we’ve walked through…
…The community is actively building solutions to alleviate data scaling pain points. Keep an eye on incoming paradigms like retroactive sampling , which allows systems to make a centralized sampling decision first and…
…As the developer submitting the code, you are accountable for that code. Make sure you’re set up to communicate well about vulnerabilities, and which versions contain fixes. See this best practices…
…CI credentials can push to our development image registry ( quay.io/cilium/*-ci ) and are available to CI builds. Even if a CI workflow is compromised somehow, these credentials cannot push to…
…Platform engineering, accompanied with the rise of projects like Backstage, is all about making developers more productive by smoothing out the day-to-day friction in how they build and ship software…
…who can trigger builds and what code CI is allowed to execute. This post covers the dependency layer: what code those builds pull in, and how we make sure it hasn’t…