Dec 04, 2019

A few things I've noticed where my results have varied and the information isn't posting to slack.

1. Inside of stack.yml I was receiving an error on the provider name faas, when I changed that to openfaas the build proceeded.

2. When I ran the deploy I received a "Deployed. 202 Accepted." message. The article said 200.

3. When I go into Openfaas the function has Invoke grayed out and the Status is set to Not ready. - Is that normal?

4. The webhook URL looks different than the example and the example ends with a / Mine looks like

Thanks for reading, hopefully I can get this working because we really need a solution for auditing VM change events.

Dec 04, 2019

Just a question, which sites does the appliance try and reach?

Dec 04, 2019

Not sure I understand the question. Are you interested in the request flow or specific calls VEBA makes to the outside world?

Dec 04, 2019
Dec 04, 2019

Yes, there are a number of Docker Containers that setups k8s and VEBA and those must be whitelist or accessible. For the complete list, see which is code I've put in place to pre-fetch the containers so internet access (either direct or proxy) isn't required.

If you're interested, we've got a preview version at

If you deploy functions that haven't been cached or must go out to say Dockerhub, then you'll still need connectivity.

Hope this helps

Nov 26, 2019

having trouble with DNS resolution regardless of what i put into the vApp config at deployment. 'resolvectl status' shows the DNS server i entered but where is the search domain stored so i can verify that?

Nov 26, 2019

Check out:

root@veba [ ~ ]# cat /etc/systemd/network/


You can also check /var/log/bootstrap.log or if you've toggled debug /var/log/bootstrap-debug.log to see what's being passed in and where things are going

Nov 26, 2019

deployed the early build posted below by William and all is well.

Nov 24, 2019

hi, i have deployed the ova today but when it boots it only seems to show the ipv6 ip in vcenter and no ipv4.
the console displays https://[IP]/status

any ideas pls.

Nov 25, 2019

1) Did you confirm the Appliance is on a network that can connect to the Internet?
2) You can login via the console and take a look at /var/log/bootstrap.log to see if there's any errors. If you don't see anything, please re-deploy and toggle the "debug" option at the very bottom and then take a look at /var/log/bootstrap-debug.log which will have more verbose logging

Nov 25, 2019

the log shows the below:-
removed /etc/systemd/system/
w1125 07:10:53.699529 712 common.go:140] warning: could not obtain a bind address for the api server: no default routes found in "/proc/net/route" or "/proc/net/ipv6_route"; using:
I1125 07:10:53.704723 712 verion.go:96] could not fetch a kubernetes version from the internet: unable to get url "": get dial tcp: lookup on server misbehaving
I1125 07:10:53.704747 712 version.go:97] falling back to the local client version: v1.14.6 cannot use "" as the bind address for the api server.

when i try to ping anything from the cli i get "network is unreachable"

Nov 25, 2019


It looks like the networking wasn't setup correctly and/or it can't reach the internet. Can you please double check all your input settings? You should be able to ping the appliance from your desktop as well as being able to ping say

I'm working on a version of the appliance that doesn't need internet and will have the containers pre-downloaded, but in your case, it looks like networking just isn't setup correctly which is all based on you input during deployment. Please check that first and we can then provide you with an early build which doesn't require internet connectivity if you're interested in testing that out

Nov 26, 2019

Hi, the networking inputs are all correct - I have tried to deploy several times with different networks i know has internet access.
I would be interested in getting an early build version to see how that fairs.

Dec 02, 2019

hi, this has now worked for me :) thankyou