R. P. Taylor

This issue just remained interesting.

This would benefit from a solution for https://github.com/helm/helm/issues/31269

Oh, this is the same as https://github.com/kube-vip/helm-charts/pull/20 , but for https://kube-vip.github.io/helm-charts/ - if anyone finds that? I'm not sure if anything refers to that page; the real documentation page is...

https://github.com/arvidn/libtorrent/pull/7890 ?

@Danny3 NATPMP and UPnP are different protocols (although they have a similar purpose for port forwarding). It looks like your gateway does not support NATPMP. Sounds like you're making some...

Personally I would say that initially updating and rebooting nodes when building the cluster is a less important subset of the ongoing operational task of keeping nodes up to date...

Still relevant.

The registry was changed: https://github.com/kyverno/kyverno/pull/12031 but the backport was reverted: https://github.com/kyverno/kyverno/pull/12125 Anyway the new registry still doesn't appear to support IPv6: ``` $ ping -6 reg.kyverno.io ping: reg.kyverno.io: Address family...

Still appears to be an issue: ``` $ host reg.kyverno.io reg.kyverno.io is an alias for gateway.scarf.sh. gateway.scarf.sh is an alias for k8s-ingressn-ingressn-0fdc8d8478-f7350678a57d879b.elb.us-west-2.amazonaws.com. k8s-ingressn-ingressn-0fdc8d8478-f7350678a57d879b.elb.us-west-2.amazonaws.com has address 54.244.195.224 k8s-ingressn-ingressn-0fdc8d8478-f7350678a57d879b.elb.us-west-2.amazonaws.com has address 52.33.86.107...

This is the same issue as https://github.com/helm/helm/issues/12911 and will be fixed by https://github.com/helm/helm/pull/12899/ so I think this can be closed.