Post Installation Sanity Check

Post Installation Sanity Check - Helm Test

Helm Test is a feature that validates successful installation of UDR along with its readiness (Readiness probe url configured is checked for success) of all the pods. The pods that are checked are based on the namespace and label selector configured for the helm test configurations.

This test also checks for all the PVCs to be in bound state under the Release namespace and label selector configured.

Note: You can use Helm Test feature only if you have Helm3.

To execute the Helm test functionality:

Note:

Before executing the Hem Test command, it is important to do the following configurations.

Configure the helm test configurations under the Global section of the values.yaml file as follows:
```
global:
  # Helm test related configurations
  test:
    nfName: ocudr
    image:
      name: ocudr/nf_test
      tag: 1.7.1
    config:
      logLevel: WARN
      timeout: 40
```
For more details, refer to the Configuring User Parameters
Ensure the label given below is part of all microservice deployments. The Helm Test feature takes the labelSelector internally, along with the helm release namespace, to select the pods and pvcs for verification.
app.kubernetes.io/instance: {{ .Release.Name }}
Usually, it is one of the Engineering labels present in the template of all NF charts. If it is not present, you need to add this label so that the helm test can work on specific helm release.
Execute the following Helm Test command:
helm test <helm_release_name> -n <k8s namespace>

Wait for the helm test job to complete. Check the output whether the test job is successful or not.

Note:
Readiness probe for all kubernetes deployment defined under the umbrella chart should be configured with httpGet parameter with proper url. If it is not configured, helm test for that pod is considered success. And if the Pod/PVC list to be verified, is fetched based on namespace and labelSelector is empty, then the Helm Test is success. If the Helm Test fails with errors, then you can refer to the Troubleshooting Unified Data Repository