Karpenter now deployed by default and migrated system pool

In September last year we announced the addition of Karpenter as experimental feature. Since then we have been making improvements to our implementation and gradually used some pilots internally and with some customers. We are happy to announce that Karpenter is now deployed by default (via AWS Fargate) on all our EKS clusters and we’ve migrated the system NodePool to use it instead of the standard Cluster Autoscaler.

More …

Upgraded Teleport to version 14.0.1

We’ve upgraded all Teleport clusters from version 13.3.8 to 14.0.1. Teleport is a tool we mostly use internally to provide secure and auditted access to (EC2) instances, Kubernetes clusters and several dashboards. The nodes will gradually be upgraded to the new version when new instances are launched.

More …

Removed Calico as NetworkPolicies engine - this functionality has merged with the AWS VPC CNI

Historically we’ve been using Calico as controller to provide NetworkPolicies support. This was offered as an optional feature only, considering the resource (and thus possible cost) impact of running this component. As announced in our K8s 1.27 upgrade post, the latest version of the AWS VPC CNI, responsible for providing cluster networking, now has native support for NetworkPolicies built-in.

More …

Support for GPU node pools on AWS (EKS)

We’re adding support for GPU node pools in EKS. GPU nodes are great for compute-intensive workloads such as graphics and visualization workloads, or machine-learning processes. AWS uses the NVIDIA device plugin to make the GPU capacity of a node available to Kubernetes workloads.

More …

Upgraded Teleport to version 13.3.8

We’ve upgraded all Teleport clusters from version 13.3.0 to 13.3.8. Teleport is a tool we mostly use internally to provide secure and auditted access to (EC2) instances, Kubernetes clusters and several dashboards. The nodes will gradually be upgraded to the new version when new instances are launched.

More …

Upgraded Teleport to version 13.3.0

We’ve upgraded all Teleport clusters from version 13.0.3 to13.3.0. Teleport is a tool we mostly use internally to provide secure and auditted access to (EC2) instances, Kubernetes clusters and several dashboards. The nodes will gradually be upgraded to the new version when new instances are launched.

More …

Disable kubernetes-dashboard by default

In an effort to further reduce the footprint of the reference solution we are no longer going to deploy the kubernetes-dashboard* by default. The Skyscrapers team is using k9s as a tool to manage our clusters and we think its a worhty replacement. This tool can just run in your terminal and doesn’t require any deployments on the K8s side. If you have this workload enabled today we will reach out to you to check if you are using this and take action based on your input.

More …

Dedicated system node pool + reduced system component footprint

In order to improve our services we changed the way the Kubernetes nodepools are structured. Previously there was a default nodepool that had a mix of both Kubernetes add-ons and application deployments. This made things more complex than it needed to be. Therefore we created a dedicated system nodepool where all add-ons are scheduled on. During this change we also took a closer look at the requested resources for all add-ons and made adjustments where needed. For most of our customer environment we’ve been able to reduce the cluster size with at least 1 equivalent node. A handful are break-even for now, but we have further optimizations planned as follow-ups.

More …