stevehipwell
GitHub blames 8-hour outage on autoscaling fail and VS Code retry storm
Re:Kubernetes on Oxide: How customer needs shaped our integrations
on Thursday August 13, 2026 @05:10PM (#49291918)
I'd assumed @sudomateo was talking about you when he said his colleague had built a prototype.
Re:Kubernetes on Oxide: How customer needs shaped our integrations
on Thursday August 13, 2026 @12:43PM (#49288588)
My point was that the major cloud CCMs are rooted (at least spiritually) in in-tree implementations. With Oxide having an API first strategy (similar in principle to a major cloud provider) the direction you take on your greenfield CCM could be interesting.
RE Karpenter, it always seemed like a natural fit for Oxide, even more so than some of the currently implementors. And now you have the expertise in the team, I'd be really interested in the reason if you don't go down that path.
Re:Kubernetes on Oxide: How customer needs shaped our integrations
on Thursday August 13, 2026 @11:33AM (#49287553)
I'm interested to see how the `oxide-cloud-controller-manager` is being built for "modern" Kubernetes and if it leads to any signify difference compared to CCMs that originated in-tree. Given the way Oxide engineer their solutions this could be really interesting.
FYI I've got `karpenter-provider-oxide` on my bingo card...
Kubernetes on Oxide: How customer needs shaped our integrations
Dependency cooldowns are unfair; we should use phased rollouts instead
S3 Is Not a Filesystem (But Now There's One in Front of It)
Amazon ECR now supports pull through cache for Chainguard
GitHub – REST API version 2026-03-10 is now available
Beyond Namespaces: Why Kubernetes Needs Real Workload Isolation
OpenTofu has a new contributor and potential MVP
Re:HashiCorp Adopts Business Source License
on Friday August 11, 2023 @05:02AM (#37086595)
AFAIK the official Crossplane providers for AWS, GCP & Azure are built on the respective Hashicorp owned Terraform providers; so I'm not sure how this is going to impact them?