Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: DOC-646 and Venkat


To address this issue, be sure to complete the SSO Setup, add the ADFS user to the Suite Admin Group before any session timeout. 

Deployment Repo Uses the Public Repo Even if Kubernetes was Restarted

If you initially use the public repository to install the CloudCenter Suite, the repo for deployments and other activities may continue to point to the public repository. If so, your deployments may continue to reference the public repo even for cases where the Kubernetes nodes were restarted. 

After an offline repo is registered with the CloudCenter Suite, users may expect Deployments to automatically and immediately pickup images from the offline repo. This is not the natural behavior.

During product installation/upgrade events, the repository settings are set to Helm (the package manager for Kubernetes). Consequently, offline repository settings are only registered after the next upgrade or new product installation event.

To workaround this natural behavior, you can opt to start a new cluster with the offline repository during the first event to ensure that your environment continues to use this offline repository.

PVC Cleanup

When you uninstall the Workload Manager or Cost Optimizer modules in the Suite Admin, the Kubernetes Persistent Volume Claims (PVCs) are not deleted – they are retained as is for the Suite Administrator to take appropriate steps to backup or manually delete the PVC. The secrets for the Workload Manager and the Cost Optimizer are not deleted when you uninstall the product. To work around this issue, the Suite Administrator must clean up their instances using one of the following suggestions


Terms & Conditions Privacy Statement Cookies Trademarks