<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cloud on Support Tools</title><link>https://support.tools/categories/cloud/</link><description>Recent content in Cloud on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 28 Sep 2026 00:00:00 -0500</lastBuildDate><atom:link href="https://support.tools/categories/cloud/index.xml" rel="self" type="application/rss+xml"/><item><title>Multi-Cloud Networking and Hybrid Cloud Connectivity: Enterprise Infrastructure Guide</title><link>https://support.tools/multi-cloud-networking-hybrid-connectivity-enterprise-guide/</link><pubDate>Mon, 28 Sep 2026 00:00:00 -0500</pubDate><guid>https://support.tools/multi-cloud-networking-hybrid-connectivity-enterprise-guide/</guid><description>&lt;p&gt;Multi-cloud networking and hybrid cloud connectivity enable enterprises to leverage multiple cloud providers while maintaining seamless, secure, and high-performance connectivity. This comprehensive guide explores advanced multi-cloud architectures, interconnection strategies, and production-ready implementations for enterprise environments.&lt;/p&gt;</description></item><item><title>The Time Linkerd Erased My Load Balancer</title><link>https://support.tools/linkerd-erased-load-balancer/</link><pubDate>Sun, 10 Aug 2025 12:00:00 -0500</pubDate><guid>https://support.tools/linkerd-erased-load-balancer/</guid><description>&lt;p&gt;Kubernetes is an incredibly flexible system, but that flexibility sometimes comes with pitfalls. This is the story of how a CRD conflict between Linkerd and the Gateway API in GKE led to an unexpected and dramatic production outage. Hopefully, by sharing my experiences, I can help others avoid a similar fate.&lt;/p&gt;</description></item><item><title>Solving Persistent Volume Issues in Multi-AZ Kubernetes Clusters</title><link>https://support.tools/multi-az-persistent-volumes/</link><pubDate>Wed, 30 Apr 2025 10:00:00 -0500</pubDate><guid>https://support.tools/multi-az-persistent-volumes/</guid><description>&lt;p&gt;Managing Persistent Volumes (PVs) in a multi-AZ Kubernetes cluster can be a challenging task. If you&amp;rsquo;re running your Kubernetes cluster on AWS with EBS volumes as PVs, you&amp;rsquo;ve likely encountered the dreaded issue of evicted pods when they are rescheduled to nodes in different availability zones (AZs).&lt;/p&gt;&#10;&lt;p&gt;In this guide, we’ll dive into why this issue occurs, its impact, and how to resolve it using Kubernetes features like &lt;code&gt;nodeSelector&lt;/code&gt; and &lt;code&gt;volumeBindingMode&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>Backup Kubernetes Cluster Resources to AWS S3 with Velero</title><link>https://support.tools/backup-kubernetes-cluster-aws-s3-velero/</link><pubDate>Thu, 13 Feb 2025 09:37:00 -0500</pubDate><guid>https://support.tools/backup-kubernetes-cluster-aws-s3-velero/</guid><description>&lt;p&gt;Ensuring the safety and recoverability of your Kubernetes cluster is critical, especially in production environments. Velero, a powerful open-source tool, simplifies the process of backing up Kubernetes cluster resources to cloud storage, such as AWS S3. In this guide, we&amp;rsquo;ll walk through how to set up Velero to back up your Kubernetes cluster resources to an AWS S3 bucket.&lt;/p&gt;</description></item><item><title>How to Use One Helm Chart for EKS and GKE</title><link>https://support.tools/use-one-helm-chart-eks-gke/</link><pubDate>Thu, 17 Oct 2024 19:26:00 -0500</pubDate><guid>https://support.tools/use-one-helm-chart-eks-gke/</guid><description>&lt;p&gt;As Kubernetes grows in popularity, many organizations are deploying clusters across multiple cloud providers like &lt;strong&gt;Amazon EKS (Elastic Kubernetes Service)&lt;/strong&gt; and &lt;strong&gt;Google GKE (Google Kubernetes Engine)&lt;/strong&gt;. Managing applications across these environments can become complex, especially when dealing with cloud-specific configurations. &lt;strong&gt;Helm&lt;/strong&gt; provides an excellent way to standardize deployments, but how can you create a single Helm chart that works for both EKS and GKE?&lt;/p&gt;&#10;&lt;p&gt;In this post, we’ll explore how to configure one Helm chart to deploy your applications on both &lt;strong&gt;EKS&lt;/strong&gt; and &lt;strong&gt;GKE&lt;/strong&gt; by using cloud-specific values and conditionals.&lt;/p&gt;</description></item><item><title>Configure Kubelet Out of Resource Handling, or How to Stop EKS Kubernetes Nodes from Going Down</title><link>https://support.tools/configure-kubelet-out-of-resource-handling-eks-nodes/</link><pubDate>Sun, 15 Sep 2024 19:26:00 -0500</pubDate><guid>https://support.tools/configure-kubelet-out-of-resource-handling-eks-nodes/</guid><description>&lt;p&gt;Managing resources effectively in Kubernetes is essential to avoid node crashes and resource starvation issues, especially in cloud environments like AWS EKS. Kubelet provides out-of-resource management capabilities that allow you to define eviction thresholds and reserve resources for system daemons, ensuring your EKS worker nodes remain operational.&lt;/p&gt;&#10;&lt;p&gt;In this post, we’ll explore how to configure Kubelet’s out-of-resource handling for EKS worker nodes using Amazon’s EKS-optimized AMI and Terraform.&lt;/p&gt;</description></item><item><title>Multi-Cloud Secrets Rotation Explained</title><link>https://support.tools/multi-cloud-secrets-rotation-explained/</link><pubDate>Fri, 13 Sep 2024 19:26:00 -0500</pubDate><guid>https://support.tools/multi-cloud-secrets-rotation-explained/</guid><description>&lt;p&gt;Managing secrets securely across multiple cloud platforms is a challenge for organizations adopting multi-cloud architectures. Multi-cloud secrets rotation ensures that sensitive credentials, such as API keys, certificates, and database passwords, are rotated regularly and managed consistently across cloud providers. This practice helps reduce security risks, such as compromised credentials, and keeps your environment compliant with security best practices.&lt;/p&gt;</description></item></channel></rss>