CCI Deployment kubectl not listing supervisor namespaces
search cancel

CCI Deployment kubectl not listing supervisor namespaces

book

Article ID: 433096

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

  • CCI has been successfully deployed
  • Leveraging kubectl in the context of CCI does not list any supervisors, despite being able to create these via UI:
    kubectl config use-context cci
    kubectl -n cci-config get supervisors

Environment

Aria Automation 8.18.x

Cause

The code fitlers the response of supervisors using the cloud account name.

In order to be leveraged in CCI the cloud account name needs to follow kubernetes format, which is less than 253 letters and only contain lower case letter or number, no dot, spaces or special characters, only hyphen, the regex is

[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)* 

Resolution

To resolve the issue for regular vSphere cloud accounts rename the cloud account in the UI to comply with the naming convention outlined above by removing any spaces or special characters.



For vCF cloud accounts it is not sufficient to rename the cloud account in the UI as this will only rename the vcf endpoint entry. In this scenario the vSphere endpoint must also be renamed via api:


Snapshot Aria Automation as best practise before proceeding.


1. Retrieve the relevant endpoint id:

With a GET request to URL:

https://<AriaAutomationURL>/provisioning/uerp/provisioning/mgmt/endpoints/

2. Rename the endpoint:

With a PATCH request to URL:

https://<AriaAutomationURL>/provisioning/uerp/resources/endpoints/<ID from step 1>

With body:

{
"name": "<NewNameWithoutSpaces/SpecialCharacters>"
}