Verify Project Logging Stack Installation
How to verify the project logging stack installation for multi-tenant logging
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:
Determine the namespace of the workspace that your project is in. You can use the
dkp get workspaces
command to see the list of workspace names and their corresponding namespaces.CODEdkp get workspaces
Copy the value under the
NAMESPACE
column for your workspace.Export the
WORKSPACE_NAMESPACE
variable:CODEexport WORKSPACE_NAMESPACE=<WORKSPACE_NAMESPACE>
Execute the following command to get the namespace of your project
CODEkubectl get projects -n ${WORKSPACE_NAMESPACE}
Copy the value under
PROJECT NAMESPACE
column for your project. This may NOT be identical to the Display Name of theProject
.Export the
PROJECT_NAMESPACE
variable:CODEexport PROJECT_NAMESPACE=<PROJECT_NAMESPACE>
Run the following commands on the managed or attached cluster. For this, ensure you switch to the correct context or kubeconfig of the cluster for the following
kubectl
commands:Check the deployment status using this command on the attached cluster:
CODEkubectl get helmreleases -n ${PROJECT_NAMESPACE}
NOTE: It may take some time for these changes to take effect, based on the duration configured for the Flux GitRepository reconciliation.
When successfully deployed, you will see output that includes the followingHelmReleases
:CODENAMESPACE NAME READY STATUS AGE ${PROJECT_NAMESPACE} project-grafana-logging True Release reconciliation succeeded 15m ${PROJECT_NAMESPACE} project-grafana-loki True Release reconciliation succeeded 11m ${PROJECT_NAMESPACE} project-loki-object-bucket-claims True Release reconciliation succeeded 11m
Then, you can View Project Log Data within multi-tenant logging.