Create a project

Create a project to organize landscapes, vector templates, and promotion configurations in a dedicated namespace. You can assign a project to a team and grant its members access through project roles.

The creation steps use cluster-level Kubernetes permissions. After creation, role bindings control access through the Konfidence API; they do not grant Kubernetes permissions.

Prerequisites

• Access to the Konfidence cluster through kubectl with permission to create Project resources. Projects are cluster-scoped.
• A project name that is a valid DNS label. Konfidence derives the namespace name from it.

Create the project

Save the following manifest as project.yaml:

apiVersion: konfidence.cloud/v1alpha1
kind: Project
metadata:
  name: ecommerce-platform
spec:
  displayName: E-Commerce Platform

Apply it:

kubectl apply -f project.yaml

The command prints project.konfidence.cloud/ecommerce-platform created.

Verify the namespace

Konfidence creates the namespace kden-p-ecommerce-platform and reports it in the project's Ready condition:

kubectl get project ecommerce-platform \
  --output=jsonpath='{.status.conditions[?(@.type=="Ready")].status}{"\n"}'

The command prints True. Confirm the namespace exists:

kubectl get namespace kden-p-ecommerce-platform

Grant access

A new project has no role bindings, so nobody can use it through the Konfidence API. Add them in spec.roleBindings as described in Grant teams access to a project.

For the full field list, see the Project CRD reference.

Next steps

• Grant teams access to a project binds project roles to the groups that use it.
• Grant CI pipelines access gives automation a project role through its workload identity.
• Create a landscape prepares the first delivery environment inside the project using Kubernetes permissions.