<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Setup on Capsule</title><link>https://deploy-preview-82--docs-projectcapsule.netlify.app/docs/operating/setup/</link><description>Recent content in Setup on Capsule</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="https://deploy-preview-82--docs-projectcapsule.netlify.app/docs/operating/setup/index.xml" rel="self" type="application/rss+xml"/><item><title>Installation</title><link>https://deploy-preview-82--docs-projectcapsule.netlify.app/docs/operating/setup/installation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deploy-preview-82--docs-projectcapsule.netlify.app/docs/operating/setup/installation/</guid><description>Requirements Helm 3 is required when installing the Capsule Operator chart. Follow Helm’s official documentation for installing Helm on your operating system. A Kubernetes cluster (v1.16+) with the following Admission Controllers enabled: PodNodeSelector LimitRanger ResourceQuota MutatingAdmissionWebhook ValidatingAdmissionWebhook A Kubeconfig file accessing the Kubernetes cluster with cluster admin permissions. Cert-Manager is required by default but can be disabled. It is used to manage the TLS certificates for the Capsule Admission Webhooks. Installation We officially only support the installation of Capsule using the Helm chart.</description></item><item><title>Configuration</title><link>https://deploy-preview-82--docs-projectcapsule.netlify.app/docs/operating/setup/configuration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deploy-preview-82--docs-projectcapsule.netlify.app/docs/operating/setup/configuration/</guid><description>The configuration for the capsule controller is done via it&amp;rsquo;s dedicated configration Custom Resource. You can explain the configuration options and how to use them:
CapsuleConfiguration The configuration for Capsule is done via it&amp;rsquo;s dedicated configration Custom Resource. You can explain the configuration options and how to use them:
kubectl explain capsuleConfiguration.spec administrators These entities are automatically owners for all existing tenants. Meaning they can add namespaces to any tenant. However they must be specific by using the capsule label for interacting with namespaces.</description></item><item><title>OpenShift</title><link>https://deploy-preview-82--docs-projectcapsule.netlify.app/docs/operating/setup/openshift/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deploy-preview-82--docs-projectcapsule.netlify.app/docs/operating/setup/openshift/</guid><description>Introduction Capsule is a Kubernetes multi-tenancy operator that enables secure namespace-as-a-service in Kubernetes clusters. When combined with OpenShift&amp;rsquo;s robust security model, it provides an excellent platform for multi-tenant environments.
This guide demonstrates how to deploy Capsule and Capsule Proxy on OpenShift using the nonroot-v2 and restricted-v2 SecurityContextConstraint (SCC), ensuring tenant owners operate within OpenShift&amp;rsquo;s security boundaries.
Why Capsule on OpenShift While OpenShift can be already configured to be quite multi-tenant (together with for example Kyverno), Capsule takes it a step further and easier to manage.</description></item><item><title>Rancher</title><link>https://deploy-preview-82--docs-projectcapsule.netlify.app/docs/operating/setup/rancher/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deploy-preview-82--docs-projectcapsule.netlify.app/docs/operating/setup/rancher/</guid><description>The integration between Rancher and Capsule, aims to provide a multi-tenant Kubernetes service to users, enabling:
a self-service approach access to cluster-wide resources to end-users.
Tenant users will have the ability to access Kubernetes resources through:
Rancher UI Rancher Shell Kubernetes CLI On the other side, administrators need to manage the Kubernetes clusters through Rancher.
Rancher provides a feature called Projects to segregate resources inside a common domain. At the same time Projects doesn&amp;rsquo;t provide way to segregate Kubernetes cluster-scope resources.</description></item><item><title>Managed Kubernetes</title><link>https://deploy-preview-82--docs-projectcapsule.netlify.app/docs/operating/setup/managed-kubernetes/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deploy-preview-82--docs-projectcapsule.netlify.app/docs/operating/setup/managed-kubernetes/</guid><description>Capsule Operator can be easily installed on a Managed Kubernetes Service. Since you do not have access to the Kubernetes APIs Server, you should check with the provider of the service:
the default cluster-admin ClusterRole is accessible the following Admission Webhooks are enabled on the APIs Server:
PodNodeSelector LimitRanger ResourceQuota MutatingAdmissionWebhook ValidatingAdmissionWebhook AWS EKS This is an example of how to install AWS EKS cluster and one user manged by Capsule.</description></item></channel></rss>