<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Saad Malik on Medium]]></title>
        <description><![CDATA[Stories by Saad Malik on Medium]]></description>
        <link>https://medium.com/@saamalik?source=rss-4b253ccb3824------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*3H7XWVZeiwb1PNw7a8vr6Q.jpeg</url>
            <title>Stories by Saad Malik on Medium</title>
            <link>https://medium.com/@saamalik?source=rss-4b253ccb3824------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 18:51:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@saamalik/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[You’re not using Cluster API for Kubernetes Infrastructure Management? Why not?]]></title>
            <link>https://medium.com/spectro-cloud/cluster-api-for-kubernetes-infrastructure-management-144c5e6df24b?source=rss-4b253ccb3824------2</link>
            <guid isPermaLink="false">https://medium.com/p/144c5e6df24b</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[k8s]]></category>
            <category><![CDATA[spectro-cloud]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cluster-api]]></category>
            <dc:creator><![CDATA[Saad Malik]]></dc:creator>
            <pubDate>Fri, 15 May 2020 04:06:02 GMT</pubDate>
            <atom:updated>2020-05-15T15:39:59.036Z</atom:updated>
            <content:encoded><![CDATA[<h3>You’re not using Cluster API for K8s Infrastructure Management? Why not?</h3><h4>Best of breed technology for Kubernetes cluster provisioning and management</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kzAKqfIUHBstY8Wd" /><figcaption>Photo by Steven Christenson via <a href="https://starcircleacademy.com/">StarCircleAcademy</a></figcaption></figure><p>As Kubernetes continues to mature there has been a proliferation of choice for Kubernetes infrastructure tools, installers, and services. Practitioners have a pretty big menu of options, specifically around cluster provisioning and management. As these Kubernetes infrastructure management products continue to innovate and introduce new features and capabilities, are there places where these products should share a common toolset?</p><p>In this post, we’ll explore why Cluster API should be embedded in many of these infrastructure management products. If you’re not familiar with Cluster API and its capabilities, we highly recommend you read the <a href="https://cluster-api.sigs.k8s.io/">Cluster API Book</a>.</p><h3>K8s Infrastructure Management Products</h3><p>Kubernetes container orchestration technology has swept the enterprise world, with 75% of organizations running containers in production soon (most orchestrated by Kubernetes). Kubernetes delivers a cloud-native platform for application delivery, runtime, and scaling. While these are huge benefits for scale out applications, providing all these capabilities comes at the expense of the complexity of the platform itself. These complexities can be categorized as:</p><ul><li>Complex and heavyweight lifecycle management: significant time and resources needed to provision, upgrade, and maintain the control planes of clusters. Each cloud has a different set of IaaS primitives that need to be cobbled together to make a “cluster”.</li><li>Intricate and involved integrations for basic components such as storage, networking, security, and others.</li><li>Difficult and not always consistent multi-cluster management and operations.</li></ul><p>Attempting to address these issues, the first generation of Kubernetes infrastructure products were born; think Kubespray, Kops, Kubicorn, KQueen, Bootkube — and from the public cloud providers a set of services on the managed Kubernetes front: GKE, EKS, AKS, DigitalOcean. Simplification and automation of deployment and, sometimes, management, was part of the goal of these projects and offers.</p><p>The number of installers, cluster managers, and managed Kubernetes platforms that exist today is nearing the <a href="https://github.com/ramitsurana/awesome-kubernetes">triple-digits</a>! Many of the Kubernetes installers are designed to provision dev/test clusters on developer workstations and laptops, but the vast majority of the cluster managers and managed Kubernetes platforms run and manage production Kubernetes clusters.</p><p>Providing basic cluster provisioning and management is <em>table stakes</em> for a Kubernetes infrastructure management product, but most provide significantly more value than just infrastructure and cluster lifecycle management, including backup, upgrades, audit, observability, and much more. Over time, these infrastructure products will continue to innovate and build new capabilities to best serve their maturing customer bases.</p><h3>What is Cluster API?</h3><p>Cluster API is a project to bring Kubernetes style APIs and declarative approach to Kubernetes cluster lifecycle management (creation, configuration, upgrade, destruction). It’s designed to work across various cloud properties and provide a reusable set of ecosystem components.</p><p>Some of the capabilities gained through Cluster API include:</p><ul><li>Provisioning of multi-master Kubernetes-conformant clusters</li><li>Provisioning and maintenance of all required cluster primitives (compute, storage, networking, security, …)</li><li>Implementation of security best practices (security groups, isolated subnets, bastion hosts, etc)</li><li>Upgrades of Control Plane and Workers on a rolling basis (control-plane now part of v1alpha3)</li><li>Support for thirteen cloud providers (public, private, and bare-metal)</li></ul><p>The key observation behind Cluster API is that Kubernetes orchestration is already complex and requires an orchestration system, so you can just rely on Kubernetes as the orchestrator to orchestrate other Kubernetes clusters. Recall, Kubernetes, in addition to container orchestration, also provides first-class features for application workloads running in Kubernetes:</p><ul><li>Workload rolling upgrades</li><li>Dynamic scaling</li><li>Resiliency</li><li>Logging / Monitoring</li></ul><p>Especially if you are using the operator pattern, the Kubernetes framework provides significant additional capabilities to your apps — declarative state management, reconciliation, error retries, and much more. Modern applications will need to implement all of these, so instead of building all of these capabilities, you can just leverage Kubernetes orchestration to orchestrate the platform.</p><p>This is truly where Cluster API shines. It’s built on the same building blocks as Kubernetes and provides the functionality to provision and manage cluster primitives and operations.</p><h3>Why Cluster API as an infrastructure management building block</h3><p>A subset of the new capabilities that Kubernetes infrastructure management products will add relate to infrastructure provisioning and cluster management: provisioning to new types of compute infrastructure, multi-master rolling upgrade, or even support of a new public or private cloud.</p><p>Instead of Kubernetes infrastructure management products reimplementing similar logic to cover these kinds of cases, why not leverage a shared component across these solutions? A <em>shared</em> component is similar to a shared library where bug fixes, enhancements, and new capabilities are provided with little or no effort. That’s where something like Cluster API could come in. By leveraging Cluster API, either as an embedded component or a required dependency, Kubernetes infrastructure products would increase their rate of innovation, decrease their time to market, and ultimately provide better experiences to their customers.</p><p>If you believe that infrastructure management products should utilize a shared <em>component </em>to provide cluster infrastructure provisioning and management, the next question is why Cluster API? Why not leverage a more mature and developed tool, like Kops?</p><p>Well, the answer really boils down to the Kubernetes architecture and functionality itself; because Cluster API utilizes Kubernetes and inherits application resiliency, scaling, logging, and more; it becomes a natural choice for the job.</p><p>There would be an advantage for all Kubernetes infrastructure management tools if they didn’t all have to implement and reimplement similar capabilities to launch, configure, and manage IaaS infrastructure for a cluster. Think about everything that goes into making a “cluster”: virtual machines, storage volumes, IP addresses, security groups, networking isolations, load balancers, etc; there are many areas of repeated non-differentiated investment on the part of solutions. Many of the Kubernetes infrastructure management tools are innovating in different areas but cannot leverage or build on top of the work done by others. If tomorrow your public cloud provider of choice offers some fancy new application load balancer or networking plugin to enforce network security policies in hardware there would be significant effort expended by all these management tools to provide support.</p><p>If infrastructure tools and products leveraged Cluster API internally it would free those tools and products up to really focus on additional value-add capabilities such as:</p><ul><li>Namespace and resource management</li><li>Container security management</li><li>Policy, Audit, Compliance</li><li>Service Mesh, Observability, and Logging</li><li>CICD and Deployment</li><li>Archive, Backup, Restore</li></ul><h3>The Road Ahead</h3><p>The first major release of Cluster API was on March 29, 2019. In a little over a year, across the Cluster API and its providers there have been a little over <em>1000</em> commits from 100+ contributors across VMware, Google, Microsoft, and more! We’re proud to share that <a href="https://spectrocloud.com/">Spectro Cloud</a> is also contributing to the vibrant and growing Cluster API project and its providers. The main development repository is healthy and continues to forge forward.</p><p>The Cluster API v1alpha3 release brought in lots of new capabilities with control plan upgrades, multi-master support for other clouds, and node health monitoring/recovery. The community is building its next release, v1alpha3+, slated to be released middle of this year with the following improvements:</p><ul><li>Cluster auto-scaling</li><li>Support for other load balancers</li><li>Spot instance supports</li></ul><p>More up-to-date roadmap for v1alpha3+ and beyond are available here: <a href="https://cluster-api.sigs.k8s.io/roadmap.html">https://cluster-api.sigs.k8s.io/roadmap.html</a></p><p>Cluster API is a Kubernetes SIG Cluster lifecycle subproject and while it has a growing community, it needs more involvement from more organizations and members. Most of the top contributors to the main Cluster API project are currently employed at VMware. One of the critical hallmarks of successful open-source projects includes the support and contributions from a diverse set of individuals and organizations. It would be great to have other small and large organizations join the project as it continues to mature.</p><p>We’re already seeing Kubicorn, Tanzu, Openshift, Airship, and NKE adopting the Cluster API project. It’s time to help this project along! This is a great example of a place where a concerted open-source push in an area just makes a lot of sense.</p><h3>More Info:</h3><p><a href="https://blogs.vmware.com/cloudnative/2019/03/14/what-and-why-of-cluster-api/">https://blogs.vmware.com/cloudnative/2019/03/14/what-and-why-of-cluster-api</a><br><a href="https://github.com/kubernetes-sigs/cluster-api/blob/master/docs/scope-and-objectives.md">https://github.com/kubernetes-sigs/cluster-api/blob/master/docs/scope-and-objectives.md</a><br><a href="https://github.com/kubernetes-sigs/cluster-api">https://github.com/kubernetes-sigs/cluster-api</a><br><a href="https://github.com/ramitsurana/awesome-kubernetes">https://github.com/ramitsurana/awesome-kubernetes</a><br><a href="https://cluster-api.sigs.k8s.io/">https://cluster-api.sigs.k8s.io/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=144c5e6df24b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/spectro-cloud/cluster-api-for-kubernetes-infrastructure-management-144c5e6df24b">You’re not using Cluster API for Kubernetes Infrastructure Management? Why not?</a> was originally published in <a href="https://medium.com/spectro-cloud">Spectro Cloud</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kubernetes: multi-tenant vs single tenant clusters?]]></title>
            <link>https://medium.com/spectro-cloud/kubernetes-multi-tenant-vs-single-tenant-clusters-e0a8f09c46f7?source=rss-4b253ccb3824------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0a8f09c46f7</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[kubernetes-cluster]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cloud]]></category>
            <dc:creator><![CDATA[Saad Malik]]></dc:creator>
            <pubDate>Tue, 24 Mar 2020 21:14:51 GMT</pubDate>
            <atom:updated>2020-03-24T21:14:51.026Z</atom:updated>
            <content:encoded><![CDATA[<h4>Deep-dive into how isolation, availability, and complexity requirements may influence your decision</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xQlCqWjP74E2uj5nHLCZPQ.jpeg" /><figcaption>Image by <a href="https://www.pexels.com/photo/different-types-of-sauce-3622479/">Jonathan Borba</a> via <a href="https://pexels.com/">Pexels</a></figcaption></figure><p>As Kubernetes matures into critical business technology infrastructure, IT teams are increasingly centralizing control, providing governance, and applying constraints to Kubernetes operations. A critical question that we are asked repeatedly is — should IT organizations run larger, multi-tenant clusters or would they be better suited running smaller clusters for each tenant? If you are a repeat reader of our blogs then you know that the answer is, “IT DEPENDS”. In this post, we’ll evaluate how Kubernetes isolation, application availability, and operational complexity may influence your decision one way or another.</p><h3>What is Multi-tenancy?</h3><p>Multi-tenancy is a deployment design, where different applications, teams, or even other departments, can run and operate in a shared environment; hence a “multi-tenant” system. A cluster “tenant” doesn’t necessarily break down into the typical organizational unit such as a team or department; it depends on how your organization defines it. For example, an extremely large multi-tenant cluster could have both dev and production workloads, across multiple different departments, where even components of a much larger application are all separated into different tenants — completely isolated and unaware of the presence of each other.</p><p>Proper isolation and application availability are key for multi-tenant systems to be feasible; would AWS have been as successful if there was even a sliver of doubt that other “tenants” (aka potentially malicious actors) could extract all your VM data? Even if you’re not concerned about malicious scripts stealing all your app data, multi-tenant systems are inherently less isolated; what if your sibling tenant’s <em>PrintSecret</em> benchmarking script accidentally pulls all the secrets out of your namespace and publishes sensitive user data to the company’s BB board (people still use those, right?). Similarly, performance consistency is important since you don’t want another team’s Jenkins CI job impacting your application.</p><p>In Kubernetes land, with proper configuration from the Infrastructure and Operations team, also known as Cluster Operators, it’s possible to virtually isolate most of these concerns but there are known limitations with what’s possible with Kubernetes’ soft-tenancy model. Please read-on if you’re interested in understanding these limitations and when it might be better to just separate each tenant into a separate cluster — and live with the added operational overhead of maintaining separate clusters.</p><h3>Isolation</h3><p>The highest level of isolation is achieved by system isolation, where each cluster is completely independent of other teams, applications, and even location boundaries. However, as you might expect, running and operating such a large number of clusters can <em>significantly</em> add to operational overhead. On the flip side, not having any isolation or partial isolation is easier to manage, but will come at the expense of isolation granularity and control.</p><p>Within a single cluster, Kubernetes provides logical isolation through different namespaces. The platform provides quite a few namespace policies to help with governance and control:</p><ul><li>RBAC: isolation and permissions,</li><li>LimitRange: default/limits on CPU and memory,</li><li>ResourceQuota: memory and CPU quotas for a namespace,</li><li>NetworkPolicy: network communication policies,</li><li>PodSecurityPolicy: fine-grained authorization of pod creation and updates.</li></ul><p>All of these policies help protect and isolate namespaces from each other — but at best provide <em>soft-tenancy</em> isolation. Not only are <em>all </em>tenant workloads running on shared infrastructure (compute nodes, networking, and storage) but they also share critical system Kubernetes components such as api-server, kube-proxy, kubelet, and others. As of <em>right now</em>, all known critical vulnerabilities have been resolved but it’s likely more critical escape vulnerabilities will be discovered (or introduced over time). If complete isolation is important to your applications and clusters, then you should probably be deploying more, and smaller, single-tenant clusters.</p><p>There are certain Kubernetes resources such as CRDs and Operators are by-design global to the cluster. You could add additional RBAC roles and permissions to limit only users in a certain namespace to be able to access such CRDs and Operators, but that is some extra work whenever some new CRDs and Operators are introduced into the cluster by admin. Also, because of their global nature, there is potential for name and version conflicts. For in-house designed CRDs and Operators, this could be addressed by applying unique prefixes to the name, but if you are using some 3rd party CRDs or Operators, it can be challenging if users from two different namespaces want to use two different versions of global resources of the same name/type.</p><h3>Availability</h3><p>As a container orchestration platform, Kubernetes does a fantastic job of orchestrating and maintaining your workloads — handling resiliency, scaling, and other application lifecycle management concerns with ease. However, if the underlying platform fails — either due to some misconfiguration, a bad upgrade, or a critical bug — then <em>all</em> workloads on the cluster will grind to a halt. Oftentimes, the downtime may not even be something of your own doing, but a misconfiguration or mistake on the part of your cloud provider.</p><p>Degraded application experience and downtime hurts end-user experience, so what actions should you take to mitigate the risk of cluster downtime? For one — don’t run your application on only <em>one </em>cluster! Properly designed cloud-native applications are designed to scale outwards — and should scale across multiple cluster boundaries — ideally in different regions, maybe even cross-cloud.</p><p>In addition to a more fault-tolerant, highly-available application, workloads deployed across different regions will also provide higher performance, lower latencies and a more pleasant user-experience for your global end-users.</p><p>Related to application availability is separating Kubernetes’ upgrade lifecycle from your application’s lifecycle. Cluster operators of large, multi-tenant clusters may find it more challenging to schedule and coordinate cluster and infrastructure upgrades, as cluster tenants may impose unique requirements to not impact their application’s SLAs/SLOs.</p><h3>Operational Complexity</h3><p>The advantages and benefits of deploying multiple clusters, hitherto compared to larger multi-tenant clusters have been promising and encouraging! The <em>not so hidden</em> cost of provisioning and operating multiple clusters is, of course, the management and operational burden of maintaining them…</p><p>Even a single Kubernetes cluster can be complex to operate. These complexities can be categorized as:</p><ul><li>Lifecycle management: complex and heavyweight lifecycle management (provision, upgrade, backup, restore),</li><li>Involved integrations for basic components such as storage, networking, security, and others,</li><li>Secure access to the clusters: user authentication and authorization, network policies, ingress,</li><li>Logging &amp; observability: centralized logging, metrics, tracing for apps and infrastructure.</li></ul><p>The complexities and overhead exponentially increase as you maintain more clusters. In addition to the concerns above, how do you bring consistency to the upgrades, security policies, and integrations you’re applying to similar purpose clusters? Many organizations want to control the operating system, e.g., a corporate security-hardened image of RHEL for the worker nodes. Others may require certain security agents such as AuditD or others to always run. Provisioning support for these components is already difficult without extensive custom automation — but supporting these components’ complex upgrade and maintenance lifecycle adds another level of complexity to the equation.</p><p>Operating multiple Kubernetes clusters costs more… literally, there is an <em>increase</em> in overall cloud costs. Clusters rarely fully utilize their allocated CPU and memory; there’s always some spare capacity available to handle the atypical bursty workload. However, across all your clusters, the VM and infrastructure costs attributed to idle and underused CPU/memory resources add up — and would surely warrant a tear or two from your CIO. Larger, multi-tenant clusters are not immune to resource wastage, but may fare better compared to multiple clusters since:</p><ul><li>Multi-tenant clusters’ workload capacity can be oversubscribed; apps across tenants don’t have the same traffic patterns and times,</li><li>Larger clusters increase the likelihood that it can make sense to do “reserved/dedicated” instances, which can mean heavier discounts for sustained usage,</li><li>IT teams monitoring a smaller set of shared clusters have more opportunities to optimize cluster auto-scaling policies and configuration.</li></ul><p>That said, the <em>added </em>cloud costs of running multiple clusters tend to be minuscule compared to the operational costs of running Kubernetes clusters. And in practice, even with the higher operational costs, most organizations are choosing to deploy single-tenant clusters to reap the isolation and availability benefits.</p><blockquote>Look for platforms that manage multiple clusters. Most Gartner customers, according to inquiries, are deploying multiple clusters as opposed to creating a large cluster consisting of multiple namespaces. Namespaces help avoid name clashing and create resource granularity across apps, but they do not provide the required isolation that creating multiple clusters does.<br><br>Assessing Kubernetes-Based Hybrid Container Management Platforms; G00377372, Simon Richard [Gartner]</blockquote><h3>Closing Thoughts</h3><p>The design choice between multi-tenant and single-tenant clusters will invariably depend on the purpose and requirements of your applications. While single-tenant deployment design makes sense for most production applications (since it enables greater isolation and control), however, during development the <em>same</em> applications might be deployed to shared multi-tenant dev/test clusters. There are fewer concerns of isolation between tenants (aka other engineers), and short cluster/infra downtimes are acceptable — and may even spark an impromptu Netrek match (Federation Captain, at your service)!</p><p>Over time as organizations continue to build and operate more Kubernetes clusters, they’ll look for tools and platforms to help support their multi-cluster deployments. Proper Kubernetes management platforms can help reign in the operational complexities, and provide simple, intuitive operations to manage Kubernetes clusters at scale.</p><p>Are there other killer use-cases or verticals which heavily favor multi-tenant clusters or single-tenant clusters? Let us know!</p><p>—</p><p>Looking for a pocket-card reference? — take a look here:</p><p><a href="https://docs.google.com/spreadsheets/d/1b13wPQcXqrhfatwwacpDosZ89gSIg4ZHvr_pNYu9ruw/edit?usp=sharing">Multi-Tenant vs Single Tenant Clusters</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0a8f09c46f7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/spectro-cloud/kubernetes-multi-tenant-vs-single-tenant-clusters-e0a8f09c46f7">Kubernetes: multi-tenant vs single tenant clusters?</a> was originally published in <a href="https://medium.com/spectro-cloud">Spectro Cloud</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>