Our great sponsors
-
vcluster
vCluster - Create fully functional virtual Kubernetes clusters - Each vcluster runs inside a namespace of the underlying k8s cluster. It's cheaper than creating separate full-blown clusters and it offers better multi-tenancy and isolation than regular namespaces.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
devspace-plugin-loft
Loft Plugin for DevSpace - adds commands like `devspace create space` or `devspace create vcluster` to DevSpace
-
Puts Debuggerer
Ruby library for improved puts debugging, automatically displaying bonus useful information such as source line number and source code.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
There are several ways of implementing multi-tenancy in your cluster, including namespacing, vclusters, and so on. Furthermore, there are also Kubernetes tools like Loft and Argo CD that make implementation and management of multi-tenancy in your Kubernetes cluster a breeze. In this article, you’re going to learn about multi-tenancy, its benefits, and how Loft and Argo CD can help you achieve multi-tenancy in your cluster.
Loft is an advanced platform for implementing self-service and multi-tenancy in your Kubernetes cluster. It implements multi-tenancy using vclusters. Traditionally, namespacing is used to achieve multi-tenancy, thereby sharing resources like ETCD storage and the API server. In contrast, Loft spins up an entirely new cluster in the host cluster, without any of the complexities of spinning up new clusters.
#ApplicationName.yaml apiVersion: argoproj.io/v1alpha1 kind: Application metadata: name: application-name # The name of the application namespace: argocd spec: project: default source: repoURL: https://github.com/example-project/example-app.git # The git repository containing all the application YAML file targetRevision: HEAD path: example-directory # The directory within the repo where you want Argo CD to watch destination: server: https://kubernetes.default.svc # The API server of your vclusters namespace: app_namespace # The namespace where you want the application to be developed. If this namespace is not available, Argo CD automatically creates this namespace
There are several ways of implementing multi-tenancy in your cluster, including namespacing, vclusters, and so on. Furthermore, there are also Kubernetes tools like Loft and Argo CD that make implementation and management of multi-tenancy in your Kubernetes cluster a breeze. In this article, you’re going to learn about multi-tenancy, its benefits, and how Loft and Argo CD can help you achieve multi-tenancy in your cluster.
#ApplicationName.yaml apiVersion: argoproj.io/v1alpha1 kind: Application metadata: name: application-name # The name of the application namespace: argocd spec: project: default source: repoURL: https://github.com/example-project/example-app.git # The git repository containing all the application YAML file targetRevision: HEAD path: example-directory # The directory within the repo where you want Argo CD to watch destination: server: https://kubernetes.default.svc # The API server of your vclusters namespace: app_namespace # The namespace where you want the application to be developed. If this namespace is not available, Argo CD automatically creates this namespace
Related posts
- ArgoCD app-of-apps create the child app but don't deploy the manifests inside the app
- Git going with GitOps on AKS: A Step-by-Step Guide using FluxCD AKS Extension
- Ultimate EKS Baseline Cluster: Part 1 - Provision EKS
- Action-runner-controller & Enterprise Git
- Automating Kong API Gateway deployment with Flux