akhayam

Hey HN. We just released an Upgrade Context Server and an Upgrade Agent to upgrade OSS components running on a K8s Platform. Platform, DevOps, SRE teams can use this Server + Agent to easily and safely raise IaC PRs in their existing coding assistants (starting with Cursor).

The hard part of Platform upgrades isn’t the IaC syntax (TF, Jsonnet, CDK, Pulumi, etc.); it’s other “stuff”. This “stuff” has two main dimensions: 1. Gathering environment context: what’s actually running, which version is compatible for your stack, which breaking changes matter, and what IaC patterns you use, etc. 2. Making upgrade choices and getting team’s +1: Once you’ve got the environment context nailed down, you choose a version that will hold in production, applying diffs in a meaningful way (e.g. only surgical Helm values / RBAC changes, while CRDs can be overwritten), and surfacing “the why” and “the what” of these upgrade choices to PR reviewers so they can provide meaningful feedback.

Chkk Upgrade Context Server + Upgrade Agent focuses on those two problems. - Version recommendations are computed against your constraints and policies so targets are compatible and stable, not simply recent. - Diffs are scoped to what you actually run, with ordering and selectors that make changes deterministic and auditable. - Breaking changes, critical fixes, and upgrade considerations appear next to the change, so reviews move quickly and the blast radius for each change is well-understood upfront.

Initial support includes the Cursor IDE and Helm IaC across 260+ open-source projects, including Networking (Istio, Cilium, …), Databases (PostgreSQL, Redis, …), Data Jobs (Argo Workflows, Jenkins, …), Data Streams (Kafka, RabbitMQ, …), Observability (Datadog, Grafana, …), Security (cert-manager, Kyverno, …), Autoscaling (Karpenter, KEDA, …), and Developer Tooling (ArgoCD, Bitbucket, …).

Workflow walkthrough is in the launch blog linked with this post. Or you can just dive directly into setup and docs here: https://docs.chkk.io/ai/chkk-plus-cursor

It’s early and we would really appreciate feedback from the HN community, especially from teams juggling multi-cluster upgrades or inherited IaC. Looking forward to your feedback and happy to answer questions .

Guess what.... agents, like humans, also get confused with too much context, all at once. "Minimum relevant context injected at the right time" is how you assure quality artifacts and actions from your agentic workflows.

It's just sooo hard to reconstruct the "minimum relevant context" from running infrastructure state matched against a moving target (i.e. the next version you should be upgrading to).

"Operational Safety" is the neglected child of software operations. I saw how it was implemented effectively when working at AWS, but the broader software ecosystem appeared oblivious to this key concept. While the CrowdStrike outage caused havoc, its silver lining is that Operational Safety has now become a key consideration for software leaders, all the way to CIOs. It must stay this way as complex, mission-critical systems will continue to rely more and more on software and cascaded failures are just a fact of life in these systems.

Thanks! Indeed, sharing knowledge programmatically will save time and effort, _while_ improving safety of these systems.

Mostly by hiring contractors, which is basically not working well for a lot of enterprises.

Most are just focusing on incident response and reactively improving things. That's why a proactive discipline that prevents these issues from happening is dearly missed.

Even when postmortems are done, information continues to exist in team silos as there is no way to share these learning across teams and enterprises. Hence, everyone repeats each others' mistakes.

Platform teams is such a new concept and is catching on like wildfire inside enterprises. However, the technology, people and process challenges faced by these teams are really not understood very well. In this blog, we tried to crystallize the biggest obstacles that we see Platform teams facing.

Thanks for your encouraging words and we are glad that the challenges and solutions resonate.

What an excellent post. I love the "first felt PMF" criterion which is the right way to think about it because, like validated by interviews in this blog, most of the times you remain unsure that you have actually found PMF... and that's perfectly ok!

Beautifully said... one generation must do the less exciting things to pave the way for the next generation.