- Changed the build process to include a web UI build stage using Node.js. - Updated Go build stage to copy web UI files to the correct location. - Removed the main.go file as it is no longer needed. - Added SQLite database configuration to example config. - Updated dependencies in go.mod and go.sum, including new packages for JWT and SQLite. - Modified .gitignore to include new database and configuration files. Signed-off-by: zhenyus <zhenyus@mathmast.com> |
||
|---|---|---|
| .. | ||
| freeleaps-controls-system | ||
| freeleaps-data-platform | ||
| freeleaps-devops-system | ||
| freeleaps-infra-system | ||
| freeleaps-logging-system | ||
| freeleaps-monitoring-system | ||
| freeleaps-storage-system | ||
| helm-repos | ||
| rbac | ||
| init-helm-repos.sh | ||
| rbac-guide.md | ||
| 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.