Project provides a logical separation of applications、environments and delivery targets, this is helpful when VelaUX is used by multiple teams. Project can provide the following features:
- restrict where applications can be deployed to (target clusters and namespaces).
- restrict which integrated configurations can be used (trusted Helm repositories, docker registries or cloud providers).
- restrict the different permission of each user, and provide a multiple-level permission control (RBAC).
The Default Project
Once installed VelaUX has one default project with name
Default owned by the
admin user. At the same time, the default delivery target and environment are also generated automatically and bound to the project.
Users with project management permissions can go to
Platform/Projects page for settings，in this page you could create and delete project.
New Project button for creating a project. Each project should set name and owner, the owner user will be granted the project admin role automatically after the project created.
Creating Environments for the Project
A project can have multiple associated environments. An environment is a logical concept that points to a namespace in the cluster. By default, if not specified, the namespace of an environment has the same name as the environment itself. When creating an environment, you need to associate it with a project.
Project owner, alias, and description fields can be updated. Click the project name and go to the project detail page, you can manage the members and roles in this project.
If there are applications and environments living in one project, then deleting the project is not allowed. You must clean up the applications, environments, and targets in the project before you can delete.