Closed nullset2 closed 1 year ago
Geez, it actually seems that in my specific setup, I actually need no LOCAL_NETWORK
variable. Removing the assignment of LOCAL_NETWORK, I think, finally solved it. Just tried forcing an eviction after I redeployed without LOCAL_NETWORK
and it all works flawlessly, ingress and VPN included.
No, the previous didn't work. The ingress eventually stopped working...
Hi,
I have a feeling that this is not about the chart but about the upstream project. I guess it sometimes for some reason cannot do a proper cleanup when it is terminating, so it fails to start on the next run.
I'd suggest taking the latest upstream project image tag from here https://haugene.github.io/docker-transmission-openvpn
and specifying image.tag
in the chart. It seems they did some fixes on the startup/shutdown scripts, so it might actually help.
Ah bingo, changing to latest solved it, and it even got me a completely different, new version of the application. Fantastic.
Hi. Apologies if this is answered elsewhere, but I've been stuck on this for a very long while and I really want to solve it. I have googled to no avail. I know the charts are deprecated but any comment helps.
This is how I install and configure the chart on my cluster:
my values.yaml...
This runs perfectly, but then once the kubelet evicts the pod (several days later, at random) and creates a new one, the pod creation Crashloops when trying to add routes with:
Deleting the pod and then letting it restart solves the issue, but this shouldn't happen --this takes my transmission server down until I manually delete the crashlooping pod.
I have seen many explanations around:
LOCAL_NETWORK
(tried that, by using the three different CIDRs listed above, to no avail).OPENVPN_CONFIG
, set it toca_vancouver
, this also didn't fix the issue.Please advise.