> ## Documentation Index
> Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Fixing Issues and Deploying to Review Environment
> This guide resolves GitLab Auto DevOps review pipeline failures by configuring MongoDB secrets, adjusting Kubernetes probe ports, and performing deployment and cleanup procedures.
In this guide, we’ll resolve a failed GitLab Auto DevOps review pipeline by correctly injecting MongoDB secrets, aligning Kubernetes probe ports, and redeploying to the review environment. We’ll also cover performance testing and cleanup procedures.
## 1. Identifying the Pipeline Failure
The review stage failed because the application pod couldn’t access the MongoDB environment variables:
Pipeline Stages Overview:
| Stage | Status | Description |
| ----------- | --------- | ------------------------------ |
| build | ✅ Passed | Build and push container image |
| test | ✅ Passed | Run unit and integration tests |
| review | ❌ Failed | Deploy to review environment |
| performance | ⏳ Pending | Browser performance testing |
| cleanup | ⏳ Pending | Teardown review environment |
## 2. Configuring Kubernetes Secrets via CI/CD Variables
Store your MongoDB credentials as CI/CD variables in GitLab:
1. Go to **Settings > CI/CD > Variables** under the Auto DevOps customizer.
2. Prefix each key with `K8S_SECRET_` so Auto DevOps creates a Kubernetes Secret and injects it into pods.
Auto DevOps will map `K8S_SECRET_` to a Kubernetes secret named ``, making it available as an environment variable inside your pod.
Example (in CI/CD UI or via `curl` API):
```bash theme={null}
# Key: K8S_SECRET_MONGO_URI
# Value: mongodb://mongo.example.com:27017
# Key: K8S_SECRET_MONGO_USERNAME
# Value: appuser
# Key: K8S_SECRET_MONGO_PASSWORD
# Value: superpassword
```
## 3. Cleaning Up the Default Namespace
Before re-running the review job, remove any leftover review resources:
```bash theme={null}
kubectl get all -n default
kubectl get secret -n default
# Delete old review secret if present
kubectl delete secret review-feature--secret -n default
kubectl get secret -n default
# No resources found
```
Ensure you’re only deleting review-specific secrets. Running deletions in `default` can impact other workloads.
## 4. Rerunning and Monitoring the Review Job
Trigger the review job again in GitLab or via API. Then inspect:
```bash theme={null}
kubectl get all -n default
kubectl logs review-feature--xxxxx -n default
```
The app will start and connect to MongoDB successfully:
```plaintext theme={null}
Server successfully running on port - 3000
MongoDB Connection Successful
```
However, the liveness and readiness probes still fail.
## 5. Diagnosing Probe Failures
Describe the pod to view probe errors:
```bash theme={null}
kubectl describe pod review-feature--xxxxx -n default
```
By default, Auto DevOps probes port `5000`, but your app listens on `3000`:
```javascript theme={null}
// app.js
app.listen(3000, () => {
console.log("Server successfully running on port - " + 3000);
});
```
## 6. Troubleshooting Auto DevOps Timeouts
Auto DevOps may report a “timed out waiting for the condition” error due to mismatched probe ports:
The Helm chart defaults to port `5000` for readiness and liveness:
## 7. Customizing the Helm Chart Values
Create a `.gitlab/auto-deploy-values.yaml` at the root of your branch to override the probe ports:
You can refer to all available Kubernetes options here:
Example `auto-deploy-values.yaml`:
```yaml theme={null}
service:
internalPort: 3000
externalPort: 3000
```
Commit and push to trigger a new pipeline.
## 8. Verifying the Updated Pipeline
After pushing, your pipeline will rerun with the correct ports:
You can cancel unneeded jobs (e.g., Code Quality, SAST) to speed up **build**, **test**, and **review**.
## 9. Successful Deployment to Review Environment
Once the review job succeeds, you’ll see the application URL:
```plaintext theme={null}
Using helm values file '.gitlab/auto-deploy-values.yaml'
Release "review-feature-" does not exist. Installing it now.
…
NOTES:
Application should be accessible at
http://-review-feature-..nip.io/
```
Verify with Kubernetes:
```bash theme={null}
kubectl get pods -n default
kubectl get ingress -n default
```
## 10. Auto Browser Performance Testing
After deployment, Auto DevOps launches **Auto Browser Performance Testing** using sitespeed.io:
The job runs:
```bash theme={null}
sitespeed.io $CI_ENVIRONMENT_URL --outputFolder sitespeed-results
```
Inspect the artifact files:
Open the main HTML report to view asset analysis:
See detailed performance metrics by domain:
## 11. Manual Stop Review and Cleanup
When you’re done, manually trigger the **Stop Review** job to delete all review resources:
In **Pipelines**, click **Stop Review**:
This job removes the Helm release, pods, secrets, and ingress:
```bash theme={null}
kubectl get all -n default
# Should show only core resources
kubectl get secret -n default # No secrets
kubectl get ingress -n default # No ingress
```
## 12. Reviewing Deployment History
Finally, view the stopped environment and its deployment jobs for auditing:
## Links and References
* [GitLab CI/CD Variables Documentation](https://docs.gitlab.com/ee/ci/variables/)
* [Auto DevOps Configuration](https://docs.gitlab.com/ee/topics/autodevops/)
* [Kubernetes Probes](https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes)
* [Helm Chart Values](https://helm.sh/docs/chart_template_guide/values_files/)