Deployment

Deployment applies the specified Helm Chart version to the App Environment. For the initial deployment, the system executes helm install, while subsequent deployments use helm upgrade.

Errors can occur during these operations.

App Helm Release Failure

If you encounter failures related to the App Helm Release in the Deployment operation logs, you can troubleshoot the issue using the following steps:

Validate Helm Chart Version

Ensure that the targeted Helm Chart version for the release is valid and functional. You can test this by installing the Helm Chart on a local Kubernetes cluster like minikube or kind. Alternatively, deploy it on a fully managed Kubernetes cluster in the cloud, such as AWS EKS, to verify its functionality. Use kubectl describe and kubectl logs commands to debug any issues encountered during installation.

Verify Helm Values

Check if the correct Helm Values required for your App Helm Chart are being passed. You can update Helm Values at both the App and Deployment levels to ensure correctness.

Health Check Failures

If the App Helm Release succeeds but health checks fail, then follow these steps:

Verify Health Endpoint

Confirm that the specified health endpoint provided during App creation exists within the application and is reachable.

Entry service type should be NodePort

Ensure that the entry service type is set to NodePort. If it is set to ClusterIP, the application will not be exposed, leading to health check failures and user access issues.

Confirm Entry Service and Port

Verify that the entry service and port specified for the App are correct and that the application is exposed through the same service and port as configured in the Helm chart.