Mangle Vcenter Adapter help for Kubernetes deployment of Mangle about mangle HOT 10 CLOSED

mangle-vc-adapter is a plain micro service with no external dependencies. The container can be deployed as a pod with access to targeted VC environments. Please give us time to provide a tested Kubernetes deployment file from our side.

from mangle.

@anjalir-arkin please provide a sample K8s deployment file for vcenter-adapter. Would also recommend that you push it to the public git repository for future reference.

from mangle.

Any update on a K8s deployment for vcenter-adapter?

from mangle.

Thank you for your help getting these files. I was able to deploy the mangle-vc-adapter onto our container and it shows the pods running.

However, I am not able to get a connection to the vCenter host. When testing the connection I get the message "Authentication to VCenter ip failed." The error code in the logs is "Error Code : FIVC001, Error Message : Authentication to VCenter "

I went through the trouble shooting documentation and found the "Cannot connect to adapter while adding vCenter endpoint" section, but I am not getting the "cannot connect to vcenter adapter" error unless I enter wrong credentials or adapter info. I did however try to reach the endpoints listed and could not reach either the Swagger UI or the application/health endpoints. The mangle-vc-adapter pods say running and ready in OCP. I can reach the mangle-services/application/health endpoint with no issue.

Any ideas on what could be wrong? Any help is greatly appreciated. Thank you.

from mangle.

@teinertt we are looking into this. @rpraveen-vmware or @anjalir-arkin will provide you with the next steps for this.

from mangle.

Hi @teinertt
As part of troubleshooting this issue, I deployed the mangle-vcenter-adapter in our k8s cluster.
So, its running as pod in parallel to mangle pod.
Am able to add the vcenter adapter to Mangle.
But upon adding the vCenter Endpoint by providing the VC URL, I get the same error "Error Code : FIVC001".
Upon debugging, I see that Mangle is able to reach vcenter-adapter deployed but throwing "500 Internal Server error" while trying to reach the VC, the error is mapped to this error code.
The error code needs to be changed from our side as it is misleading.

Since the mangle is deployed in k8s in AWS, its unable to reach the vCenter server deployed in the datacenter and is reachable within Office Network.

I suspect it could be the similar issue in your case..
Does your k8s have access to target vCenter ?

You can reach the vcenter-adapter swagger url through this api:
https://VCENTER-ADAPTER-EXTERNAL-IP/mangle-vc-adapter/swagger-ui.html (admin/admin)

https://VCENTER-ADAPTER-EXTERNAL-IP/mangle-vc-adapter/application/health
which gives "status | "UP"

from mangle.

@teinertt Hope you were unblocked with the help of a comment from @rpraveen-vmware. Please post an update on your status.

from mangle.

@rpraveen-vmware Thank you for this information. @vhkilari I will forward this information and work with team who is working on this issue, and I will update with results.

from mangle.

@teinertt Any Updates?

from mangle.

@rpraveen-vmware Thank you for this information. @vhkilari I will forward this information and work with team who is working on this issue, and I will update with results.
Closing the issue as there is no reply from @teinertt, assuming the issue is resolved.

from mangle.