Closed DavideWalder closed 2 years ago
Thanks for putting this together. How did you test this? Are there any problems at all with the chart?
Thanks for putting this together. How did you test this? Are there any problems at all with the chart?
I tested it by deploying it with different values to a private cluster. More specifically I tested that the configuration for OpenVPN and both proxies is created correctly (secrets and env vars correctly created and referenced).
In terms of behaviour of the image in the k8s environment: I tested that OpenVPN, both proxies and authentication work as intended (tested by port-forwarding the two ports to my local machine and sending requests through the pod using cURL). Also tested the KILL_SWITCH
and SUBNET
options by by passing the address of the DNS server in /etc/resolv.conf
as subnet (without it OpenVPN can't connect and with it it can, as intended).
Things left to do:
readinessProbe
, which is currently the same as the healthcheck in the Dockerfile. This should anyway be replaced by a better check that pings both proxies (it can also be used as a livenessProbe
then).Other than that I didn't notice any other issue with the chart (also only used it for a few days)
Added a chart to deploy the client to K8s, comprised of:
The documentation for the chart is autogenerated via the pre-commit hook
helm-docs
.The chart would also have to be distributed and hosted (for example through GitHub pages, as explained here), but this requires admin rights to the repo.