Cameron Braid
Cameron Braid
Sorry - looks like it was a copy/paste error as the original yaml doesn't have envFromen in it - so that is not the cause, editing above comment to reflect...
ok, looks like the cause is the following empty (and therefore null) `env:`. so the same issue as originally reported
> Cool! Can you share more about this setup? Where do you plan to run the bare metal nodes? Do you need to manage who has access to the VPN?...
Am now leaning towards using https://wails.app for UI
> I for one would love to see drago as an operator which could seed kubernetes edge workers. Something in combination with [metal3](https://github.com/metal3-io) > This could be killer functionality for...
At the moment using metallb and a CIDR that is within my WG VPN, I can create a LoadBalancer Service and access my services via vpn. Works well.
> I understand. Do you need a desktop client, or would it be ok to have the (simple and easy to install) Drago client serve a configuration UI on a...
Another important use case is to write a Envoy Proxy Filter https://istio.io/latest/docs/concepts/wasm/
I get the same error node 14.15.4 ``` FATAL ERROR: HandleScope::HandleScope Entering the V8 API without proper locking in place 1: 0xa04200 node::Abort() [/home/cameronbraid/.nvm/versions/node/v14.15.4/bin/node] 2: 0x94e4e9 node::FatalError(char const*, char const*)...
I tried a proof of concept with worker_threads directly and got the same error, so tiny may be the route to go. Is there any way to force tiny to...