Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Cohesity Cloud Scale Technology Manual Deployment Guide for Kubernetes Clusters
  3. Section IV. Maintenance
  4. Troubleshooting
  5. Troubleshooting AKS and EKS issues
  6. Helm installation failed with bundle error
Cohesity Cloud Scale Technology Manual Deployment Guide for Kubernetes Clusters

Helm installation failed with bundle error

Helm installation fails to continue with the following error message:

Unable to continue with install: Bundle "db-cert" in namespace "" exists and cannot be imported into the 
current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm";
annotation validation 
error: missing key "meta.helm.sh/release-name": must be set to <release-name>"; annotation validation error: missing key
"meta.helm.sh/release-namespace": must be set to <NetBackup namespace>

This issue occurs when db-cert bundle is not deleted from the "" empty namespace after Cloud Scale deployment is uninstalled.

To resolve the issue, perform the following:

  1. Use the following command to check if the db-cert bundle exists:

    kubectl get bundle -n ""

  2. Use the following command to delete the db-cert bundle:

    kubectl delete bundle db-cert -n ""

Feedback

Was this page helpful?
Previous

Extracting logs if the nbwsapp or log-viewer pods are down

Next

Deployment fails with private container registry and Postgres fails to pull the images

Feedback

Was this page helpful?