Technical writing
Technical deep-dives, best practices, and guides from engineers who run Kubernetes every day.
Running production Kubernetes in-house costs more than the cluster bill. The real cost is the platform team: enough engineers to cover a 24/7 on-call rotation, keep up with three Kubernetes releases a year, and patch CVEs across a dozen add-ons. For most organizations without a dedicated platform team, a managed Kubernetes provider is cheaper.
Read moreAzure AKS, AWS EKS and Google GKE are “managed Kubernetes” in a narrow sense: the cloud provider runs the control plane. Most of what keeps a production cluster healthy is still yours. That includes node and add-on upgrades, ingress, certificates, monitoring, backups, security policies and incident response. This split, the shared responsibility model, is what teams moving to Kubernetes most often misunderstand.
Read moreA migration from ingress-nginx to Gateway API is less about YAML than about planning. Converting Ingress objects is largely automated. The real work is in three places: the annotations and configuration snippets nobody remembers adding the things ingress-nginx did for you implicitly the moment traffic moves to the new gateway Plan for those, and the migration is routine.
Read moreGateway API is the successor to the Kubernetes Ingress API. Ingress put everything in one object, extended with controller-specific annotations. Gateway API splits traffic configuration into separate resources for separate roles: the platform team runs the gateway, and application teams attach their routes to it.
Read moreChoosing the right Kubernetes hosting for your municipality or government organization is crucial. At Guida, we understand your needs for high availability, reliability, and compliance. That’s why our Managed Kubernetes Service (IKS) on the Intermax Cloud is Haven Compliant.
Read moreIn the rapidly evolving tech landscape, the term “cloud-native” often gets associated with running applications exclusively in the public cloud. However, this is a common misconception. Being cloud-native is more about how you build and manage your applications than where they are hosted.
Read moreKubernetes is a powerful platform that helps businesses deploy and manage applications at scale. However, despite its many advantages, Kubernetes is not inherently secure by default. In fact, after reviewing numerous Kubernetes environments, we’ve identified several critical security risks that require immediate attention. These issues often stem from misconfigurations, weak access controls, lack of visibility, poor network isolation, and running pods with privileged or root access.
Read moreKubernetes has become one of the most popular tools for managing containers in the cloud. It’s flexible, powerful, and can help organizations manage their applications at scale. Many think that once a Kubernetes cluster is set up, the hard work is over. However, the truth is that setting up the cluster is just the start. Keeping it running smoothly and securely requires ongoing work, known as “Day-2 operations.”
Read moreKubernetes offers numerous features to ensure high availability for applications running in its cluster environment. One critical aspect of maintaining high availability is managing pod disruptions effectively. In Kubernetes terminology, pod disruption refers to the temporary unavailability or termination of a Kubernetes pod, which can occur voluntarily or involuntarily.
Read moreThe KubeCon Europe 2024 event was a significant milestone, with over 12,000 developers in attendance, making it the largest gathering in its history. From March 18th to 22nd, attendees had the opportunity to engage with the latest announcements and discussions that are shaping the landscape of cloud-native computing and Kubernetes technology.
Read moreWe use cookies to improve your experience on our website. Learn more about our privacy policy.