Enable Native Public Cloud endpoints in VCF Automation

Products

• VCF Automation

Issue/Introduction

This article describes how to enable Native Public Cloud in order to migrate existing endpoints.

Environment

VCF Automation 9.1.1 or later

Cause

VCFA 9.1.1 disables Native Public Cloud endpoints by default

Resolution

A resolution is not included in the current release.

Workaround:

Important Note: Applying this change restarts the provisioning-service-app, catalog-service-app, and tango-blueprint-service-app deployments. These services will be briefly unavailable while their pods restart.

Apply this workaround during a maintenance window or during a period of low activity.

1. SSH into the VCFA node using 'vmware-system-user' account.
2. Log in as 'root' by running 'sudo -i'
3. Create the patch scripts 'toggle-public-clouds.sh' on the node by running the below command:

   mkdir -p ~/toggle-public-clouds && cd ~/toggle-public-clouds
   
   base64 -d <<< '/Td6WFoAAAFpIt42BMCBCIBQIQEcAAAAAAAAAOC7AHzgJ/8D+V0AFxfKhvNlswqB7YmVQeT1vEl8rWIPJOOyomzRhjK9BWOq0J08AXS+IX8apVvEm/eR9y+t+6JIf1pp6FWW4ShfGYFwihRys+SDlB/Dm2M0W+rvjq8lwjo6cAvBveQbU+D68OUN6tPTFrLmqdWYM/ekXp23VpXP8ViNhsVHvCJc0xtfxnx9zC5HbhPdqEup5Gs24b78Qv9RHdkjqpTQ94oSn9BnV6mMKLlO1lKC/ybDsYqguLTYTvHDes3B8pV8K6Kwln2ynvgevqSOHM1ugUUUlwHvlVF13UWqOxEhdwagFgnBHt5un6WhiGnrfYtwlHmCcJMzCbOzqaME+3OnXmrpKvvy7tEmnN2dWcDeTTtM0UfnthwOkOJbtR1hpvDiZucNn0YQv7z7XQj0qtHwFdmXthHdFJFq+oghMl6uSpdAuagG0XhPjJd8t7JB28Anvw9vUDTcPJMck6H9YSbiikCnW2yzWBiHZSMvKogzLoX+CfxdJZeEFnpwNk26LaLyUM6+5Lb49zWUpDYaDqT1GPQWCiiXkXoMpKC2UpKlLqLaM3T0pG8edsDTqNJUHnY79Hn+PMSl+pgAN77Dij/2jiInuf2m1wyVoeQ+PNk3KY8FqVH9sZ7ySrLmpNNReky1iLLZhLJq2B/SAhHPEze/QKcAKq0+H0OJ4mLRLraddGUeDwG/FcN91iniF4GhCowv11wRWY8oQIJaUBIJTEhbEtmDoooSIXq5oo8togwDkv+rfGv1wushS1W78VuSViiNhVNjyWc/yBQbb+WqfxP6EaeuyuFNJtJ2pS/rIn3YQtS8yvA95/WSa3TjoydOKLrQqQxL7Qrg7032lEe+ehQCvidgjnYais+xy8pGcemULETJoQblWXpiPGOx6rxxG38wuHcuTrW6yy384mZahbam/hLtPD7Bba2ZepVhVPiCG9PDsE9kXRwzJaDFFflprRqdBYBLwE9mtEikPC/WAzikMx6TkVtWPLSCRChQYd/5P063JShyNwqp13KFIQL3ZPwMfLJkIAxF9rJSls2aYn3uz2Ho1JIqywUio2kwQvNtygv6pZrtp0uNucrsZMCIcTYeBQfFRtdsTehVFl7PZeeQ+i6vhTei77Tb9H9mzDzeH75BiOd1uudLP6Dj/ErB81m/saNsOM+iCF0LAfnZPY85fBdho5cONOeKL8KGPwdnarXKYkWwqL1KjXalDpYIQyn4QZ4iwCcuy0bQQm/SWtCLfrB2+fI4H82+VLbJVdAhzNmV+ceVci4VImDu3KNmsx1YfTIF+QcWXqTPm1faPlTnCCGkQ2DHipwQ9S4KtNLgJmIG54mkGsexAfc35isiYI4qTA5LQredxGD+8o4AAAAAAIrLBlMAAZkIgFAAABxAqUg+MA2LAgAAAAABWVo=' | tar -xJ

4. Apply the script having argument `false` or `true` from the current directory:
   

      ./toggle-public-clouds.sh false
      # or
      ./toggle-public-clouds.sh true

   Note:
      To enable NPC set value as 'False'
      To disable NPC set value as 'True'
   

Steps to Rollback:

1. To revert this change, re-run the script with the opposite value from what was previously applied — e.g., if **./toggle-public-clouds.sh false** was used to enable NPC, run **./toggle-public-clouds.sh true** to disable it again.
   • Note: This restarts the same three deployments (provisioning-service-app, catalog-service-app, tango-blueprint-service-app) as the original change.

 

 

Additional Information

• VCFA 9.1.1 disables Native Public Cloud (NPC) endpoints by default, with a full removal planned for the next major VCFA release.