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!

Hi, I am unable to download VEBA appliance . Error displayed page is currently down or permanently moved . KIndly , confirm on the same if any new URL to download it .

Hi Hemant,

Sorry about that, it should now be fixed

Thanks William for quick fix !!