icecheng/freeleaps-ops
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
de23dff37e
freeleaps-ops/cluster/manifests
History
Eason Zhao de23dff37e feat: alert manager config update
2025-10-21 16:20:57 -04:00
..
freeleaps-controls-system ci(bump): update reconciler image version for alpha to 1.0.2 2025-07-31 15:30:16 +08:00
freeleaps-data-platform chore(starrocks): increase fe resources to 2c4g and limits to 4c8g 2025-09-10 11:10:57 +08:00
freeleaps-devops-system fix: update Jenkins token in gitea webhook configuration 2025-07-24 16:51:35 +08:00
freeleaps-infra-system fix: update Jenkins token in gitea webhook configuration 2025-07-24 16:51:35 +08:00
freeleaps-logging-system feat: enable log collection for prod environment 2025-08-13 09:41:25 +08:00
freeleaps-monitoring-system feat: alert manager config update 2025-10-21 16:20:57 -04:00
freeleaps-storage-system ci(bump): bump reconciler image version for alpha to snapshot-9f1a2bc 2025-08-04 15:59:50 +08:00
helm-repos Remove Flink and Metabase manifests from the freeleaps-data-platform directory, including CRDs, RBAC configurations, deployments, and associated resources. This cleanup streamlines the project by eliminating unused components. 2025-09-02 10:38:40 +08:00
rbac feat: update RBAC configurations for data platform and mathmast roles 2025-05-12 10:56:58 +08:00
init-helm-repos.sh fix(pipeline): change file permissions to executable for Ansible and script files 2025-02-10 15:39:49 +08:00
rbac-guide.md feat: update RBAC configurations for data platform and mathmast roles 2025-05-12 10:56:58 +08:00
README.md feat: update RBAC configurations for data platform and mathmast roles 2025-05-12 10:56:58 +08:00

README.md

Manifests of Freeleaps Cluster

Intro

This directory contains the manifests of Freeleaps cluster. The manifests are used to deploy the cluster on Azure. The manifests are written in YAML format and can be applied using kubectl command line tool or Helm package manager.

Structure

All directories in this directory are named with namespaces. Each directory contains the manifests for that namespace. The manifests are organized into subdirectories based on their services.

RBAC with Azure AD for each namespace

RBAC for each namespace is defined in the rbac/rbac.yaml file that store in the subdirectory of each namespace.

We restrict the access to the namespace by using Azure AD groups.

This document may help you to figure out how to using Azure AD groups to restrict the access to the namespace.