Empty manifest editor file when deploying containers in Cloud director Content Hub

Products

• VMware Cloud Director

Issue/Introduction

Symptoms:

• When using Content Hub to deploy a container, some images like kubeapps, nginx-ingress, etc. are having issues
• The manifest files for the affected images are found empty
• The container images are provided by VMware Market Place
• Different browser (Firefox, Edge, Chrome etc) displays the same behavior
• There are no input forms, and the manifests editor is empty!

Environment

VMware Cloud Director 10.x

Cause

This issue occurs due to the Content-Security-Policy Headers

Resolution

This is currently a known issue and will be resolved in a future release of VMware Cloud Director. Continue using the workaround provided below.
 
To be alerted when this article is updated, click Subscribe to Article in the Actions box.​

Workaround:

To work around this issue, one of the following methods can be carried out:

1. Download the helmchart file and paste its values.yaml content into Manifests Editor:
   1. Find the file transfer link from the browser console, for example, "https://vcd.example.com/transfer/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/file".
      1. The link appears after you click Show Advanced Settings as per Working with Container Applications in Your VMware Cloud Director Tenant Portal.
   2. Copy the link from Step a into the browser address bar to download the file.
   3. Extract values.yaml from the downloaded file binary and paste its content into Manifests Editor.
2. Add the public bitnami helm chart repository https://repo.broadcom.com/bitnami-files as catalog source and import the charts,

Note: Bitnami helm charts on Marketplace are available on public bitnami repository.