I hope the following instruction would help you to figure it out.
yaml files are in the zip file.
=================================================================================
I installed 5.1 on-prem last week and was given the following advice by the CCS DEs.
The external facing services type can be changed to NodePort for the services to be discoverable. For this to work, appropriate roles and role bindings are needed. Follow steps below.
- Create cluster role for node access
Copy the attached file suite-prod-mgmt-clusterrole.yaml to one of the k8s node or to the location where you've remote access to the k8s culster
- kubectl apply -f suite-prod-mgmt-clusterrole.yaml
- Create cluster role binding
Copy the attached file suite-prod-mgmt-clusterrolebinding.yaml to one of the k8s node or to the location where you've remote access to the k8s culster
- kubectl apply -f suite-prod-mgmt-clusterrolebinding.yaml
- Restart prod-management pod
- kubectl scale deployment common-framework-suite-prod-mgmt --replicas=0 -n cisco
- kubectl scale deployment common-framework-suite-prod-mgmt --replicas=1 -n cisco
- Change the below services type to NodePort
- cloudcenter-guacamole
- cloudcenter-rabbitmq-ext
- kubectl edit svc cloudcenter-guacamole -n cisco
Note: Manually change the type descriptor to 'NodePort' and save the service config
Now, add cloud/cloud account in WM/CO.
I did this to my installation, and can configure AWS regions successfully:
