You must wait for the Project’s logging stack HelmReleases to deploy before configuring or using the Project-level logging features, including multi-tenancy:
Run the following commands on the management cluster:
-
Execute the following command to get the namespace of your workspace
kubectl get workspacesCopy the value under
WORKSPACE NAMESPACEcolumn for your workspace. This may NOT be identical to the Display Name of theWorkspace. -
Export the
WORKSPACE_NAMESPACEvariable:export WORKSPACE_NAMESPACE=<WORKSPACE_NAMESPACE> -
Execute the following command to get the namespace of your project
kubectl get projects -n ${WORKSPACE_NAMESPACE}Copy the value under
PROJECT NAMESPACEcolumn for your project. This may NOT be identical to the Display Name of theProject. -
Export the
PROJECT_NAMESPACEvariable:export PROJECT_NAMESPACE=<PROJECT_NAMESPACE>Run the following commands on the attached cluster:
Ensure you switch to the correct context or kubeconfig of the attached cluster for the following kubectl commands:
-
Check the deployment status using this command on the attached cluster:
kubectl get helmreleases -n ${PROJECT_NAMESPACE}
When successfully deployed, you will see output that includes the following HelmReleases:
NAMESPACE NAME READY STATUS AGE
${PROJECT_NAMESPACE} grafana-logging True Release reconciliation succeeded 15m
${PROJECT_NAMESPACE} loki-distributed True Release reconciliation succeeded 11m
Then, you can view project log data within multi-tenant logging.
Kommander Documentation