This message was deleted.
# k3s
a
This message was deleted.
p
My suspicion is (as we're on an old k3s) the firewall rule isn't getting put in place in time so first attempt fails, then works but short lived pods that don't retry just fail once
I've got a workaround which I suspect will be negated when we have time to upgrade k3s:
Copy code
spec:
          containers:
          - args:
            - >-
              /bin/sleep 2 && longhorn-manager -d recurring-job snapshot
              --manager-url <http://longhorn-backend:9500/v1>
            command:
            - /bin/sh
            - "-c"
            env:
            - name: POD_NAMESPACE
the
sleep
gives enough time for iptables to be updated before the pod tries to connect to kubeapi