Ion Nistor

It seems there's another issue for this, as well: #2386

One more 'vote' for this. We are running an on-prem IPv6 vanilla K8s so I can assist with testing, if needed.

Hi there, Has anyone taken a look over the issue described above? Thanks, Ion

@repeatedly hi there; any updates here?

Correct - the first item refers to how a numeric address is handled, while the second involves DNS resolution.

You'll find upgrade instructions here: https://github.com/kadalu/kadalu/blob/devel/doc/upgrade.adoc In short, you're "applying" the new yaml manifests for the newer versions of Kadalu Operator and Kadalu CSI Nodeplugin. Make sure you're using the...

Same issue here - cannot deploy Envoy Gateway using Flux, for the same reason

Are there plans to update the version naming for compliance with Flux2?

In the meantime, Envoy Gateway `v1.1.0` was released; I am trying to use it with the Gateway API 1.1.0 CRDs and get the same error: ``` Error: failed to create...

Thanks for the quick response. Sure, here goes: ``` ➜ ~ kubectl get crd backendtlspolicies.gateway.networking.k8s.io -o jsonpath='{.spec.versions[*].name}' v1alpha2 ``` `v1alpha2` seems to be the one included with GW API CRD...