Hi, can someone help me to configure Gitlab as registry ? I have an error :
Unable to fetch image "registry.gitlab.internal.intra/veba/kn-ps-host-check:1.0": failed to resolve image to digest: GET https://gitlab.internal.intra/jwt/auth?scope=repository%3Aveba%2Fkn-ps-host-check%3Apull&service=container_registry: DENIED: access forbidden
I don't understand this redirect, and why the permission denied

is internet access for the appliance mandatory or can I drive the EBA without internet access?

No, its air-gapped ready. However, to run your functions, it will need connectivity to the registry where the containers are hosted whether that is within your datacenter or public registry like docker or gcr

Hello William,
which private registry do you recommend for inexperienced users?

VMware Harbor, its free/OSS and its also what we recommend if you don't have a solution in place already. If you need commercial support, consider purchasing TAP or TKO

I have a veba appliance receiving events from multiple vcenter servers.
Is there a way to get the vcenter that the event is coming from through the CloudEventData? So I can target actions based on the vcenter sending the CloudEventData.

Yes, this is encoded in the headers and look at the ce-source field: http://vmweventbroker.io/kb/eventspec

Thank you that got me in the right direction. For other reference the kn-ps-echo example give all the info you will need to get the header info out.

using an customized powershell script and a private registry don't seems to work. when i apply the edited function.yaml nothing change under the vmware-functions when i monitor witfh kubectl get pods -A i don't know where to look for some errors

Can you manually do a pull on VEBA appliance, ensure it has connectivity and can communicate with your private registry, especially on resolution and/or certificate trusts ...

Hello William,
if I do a of pull from private registry, it seem to be good : 'Status: Image is up to date'.
And image is working fine when i launch docker run from test directory.
About certificate : i added the certificate of the private registry to the certificate store of the veba appliance and a curl command of the private registry is working fine. I have no idea where to look to see why kubectl doesn't seem to ingest function.yaml file. I may probably have missed something when using a private registry. The only modification in function.yaml file is about the image location like indicated in the readme.

Can you do a describe on function and see if there's any hints on issue? You may also want to join our public slack for easier debugging

There's also https://vmweventbroker.io/kb/troubleshoot-functions in case you've not seen it

Thanks for the links, i think i will start over try with docker hub, it seem the issue come from the certificate and the private registry... The function was just a little different from the example about vm restarted by HA. Maybe i will join slack if i can't make any progress.