Hi, I have tried to deploy VEBA, now the VM seems like working well. However, I cannot find plugin in vCenter (I have tried in VC6.7 and 7.0). I followed the doc: https://williamlam.com/2021/10/heads-up-no-healthy-upstream-error-with-veba-vsphere-ui-plugin-with-vsphere-7-0-update-3.html, but no "veba" found on step #3. I can get output from https://veba.gsslab.bj/stats/vcenter. Any suggestion on this situation? Thanks in advance.

BTW, I don't find any veba-ui pod in my env

root@veba [ ~ ]# kubectl get pod -A
NAMESPACE NAME READY STATUS RESTARTS AGE
cert-manager cert-manager-7c6f78c46d-zhrcb 1/1 Running 0 22h
cert-manager cert-manager-cainjector-668d9c86df-dsftx 1/1 Running 0 22h
cert-manager cert-manager-webhook-764b556954-x89qv 1/1 Running 0 22h
contour-external contour-9856c957b-cg4mg 1/1 Running 0 22h
contour-external contour-9856c957b-gwb68 1/1 Running 0 22h
contour-external envoy-9vsn6 2/2 Running 0 22h
contour-internal contour-7588b8dd5b-s5lbn 1/1 Running 0 22h
contour-internal contour-7588b8dd5b-tsc97 1/1 Running 0 22h
contour-internal envoy-tvwz5 2/2 Running 0 22h
knative-eventing eventing-controller-56ccd89cd8-gsp9q 1/1 Running 0 22h
knative-eventing eventing-webhook-76b66cd56c-mmtd4 1/1 Running 0 22h
knative-eventing rabbitmq-broker-controller-846868886-v64n7 1/1 Running 0 22h
knative-eventing rabbitmq-broker-webhook-7d76d887ff-tkc9x 1/1 Running 0 22h
knative-serving activator-6fb68fff7b-4jgst 1/1 Running 0 22h
knative-serving autoscaler-54f48f5bb7-8fcsm 1/1 Running 0 22h
knative-serving controller-66cb4b556b-v9zlz 1/1 Running 0 22h
knative-serving domain-mapping-66f8d5bc4c-g7zjq 1/1 Running 0 22h
knative-serving domainmapping-webhook-55bdf595dd-4bllm 1/1 Running 0 22h
knative-serving net-contour-controller-676d484b95-4qzcf 1/1 Running 0 22h
knative-serving webhook-6d5c77f989-85pc2 1/1 Running 0 22h
kube-system antrea-agent-jgdqx 2/2 Running 0 22h
kube-system antrea-controller-959968b4-xbzl2 1/1 Running 0 22h
kube-system coredns-558bd4d5db-8cvtp 1/1 Running 0 22h
kube-system coredns-558bd4d5db-pmc2s 1/1 Running 0 22h
kube-system etcd-veba.gscn.local 1/1 Running 0 22h
kube-system kube-apiserver-veba.gscn.local 1/1 Running 0 22h
kube-system kube-controller-manager-veba.gscn.local 1/1 Running 0 22h
kube-system kube-proxy-7m62p 1/1 Running 0 22h
kube-system kube-scheduler-veba.gscn.local 1/1 Running 0 22h
local-path-storage local-path-provisioner-5696dbb894-mgdxb 1/1 Running 0 22h
rabbitmq-system messaging-topology-operator-76dd775d46-5r2qg 1/1 Running 0 22h
rabbitmq-system rabbitmq-cluster-operator-7cbf865f89-nnhbj 1/1 Running 0 22h
vmware-functions default-broker-ingress-654769cf76-l5dn4 1/1 Running 0 22h
vmware-functions sockeye-65697bdfc4-xxc2b 1/1 Running 0 22h
vmware-functions sockeye-trigger-dispatcher-84f5c9d558-7k7c7 1/1 Running 0 22h
vmware-system cadvisor-c85lj 1/1 Running 1 22h
vmware-system tinywww-65d679f864-dxs75 1/1 Running 0 22h
vmware-system veba-rabbit-server-0 1/1 Running 0 22h
vmware-system vmware-event-router-vcenter-d6bc8bbd6-85rkv 1/1 Running 8 22h

Veba "looks" to have deployed ok... however if I visit https://vebafqdn/status/vcenter i get "404 page not found" and no plugin within the vSphere UI (vSphere 7.0.3d). I looked at Williams workaround for "no healthy upstream" but don't this fix will work on my config (using latest veba ova also).

Ignore this folks, I've redeployed and fixed :)

If I wanted to pull images from an internal harbor, how would I configure this to accept that internal CA? I know we can skip tag resolving altogether with the registriesSkippingTagResolving tag by editing the config-deployment but I would like to add my CA cert properly if possible but can't figure out how

Hey Pete, does this help? https://rguske.github.io/post/using-harbor-with-the-vcenter-event-broker-appliance/

Hi Michael,
I did see that but the new KNative version of the appliance seems to ignore the docker settings and has its own. I did find this, but I can't figure out how to apply it in this appliance because their example is missing the selector, which makes sense since it would be different in every appliance. https://knative.dev/docs/serving/tag-resolution/#custom-certificates

Hi, I was able to deploy VEBA and I received welcome screen with Appliance configuration and Appliance Provider Status.

However veba did not integrate with vCenter. I don't have plugin in and if I am go to https://applaince/status/vcenter I am receiving info "no healthy upstream".

I used user with more then read rights, so there should be no issue.

Maybe some service did not started, however I reboot appliance and still no joy.

Any hints, please?

What version is your vCenter Server?

If its vSphere 7.0 Update 3, you'll need to follow https://williamlam.com/2021/10/heads-up-no-healthy-upstream-error-with-veba-vsphere-ui-plugin-with-vsphere-7-0-update-3.html and apply the workaround

Thank you!