⚠️ Archived - Official Microsoft Sample

Archived

⚠️ With Flux's move to Flux v2, we recommend reviewing the multitenancy example found at flux2-multi-tenancy.

This repo contains sample implementaions of soft multi-tenant scenarios described in this design doc using Azure Arc for K8s for GitOps enablement.

IMPORTANT: The design doc in this repository is meant to inform the thinking around your own design as different projects and organizations have different requirements.

Scenarios - Overview

The scenarios that typically lead users to seek a soft multi-tenant solution for their kubernetes clusters are the following:

1. Enabling multiple teams to develop in a single cluster

   • Deployment requirements:
     • Need to be able to dedicate namespace or cluster to a tenant
     • Need to provide as much Tenant autonomy as possible without compromising other tenants

2. Enabling multiple instances of the same application in a cluster

   • Deployment requirements:
     • Need to deploy different configurations for a single application
     • Need to manage at least prod and dev versions and environments

Sample Limits/Constraints

This sample does not include:

• networking, security, or resource policies necessary for namespace isolation.
• managing secrets

Contents

Outline the file contents of the repository. It helps users navigate the codebase, build configuration and any related assets.

File/folder	Description
scenario1	Sample for Scenario 1
scenario1	Sample for Scenario 2
CODE_OF_CONDUCT.md	Microsoft's code of conduct for open source.
README.md	This README file.
LICENSE	The license for the sample.

Prerequisites

• Arc connected cluster(s). Find out more information on how to onboard your clusters with Arc here: Azure Arc for K8s Preview

Key concepts

• Kubernetes
• GitOps

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.