AFAIK, in addition to Calico configuration, Kubernetes components must also be ran with according arguments:
https://kubernetes.io/docs/concepts/services-networking/dual-stack/#configure-ipv4-ipv6-dual-stack
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
https://docs.tigera.io/calico/latest/networking/ipam/ipv6
AFAIK, in addition to Calico configuration, Kubernetes components must also be ran with according arguments:
https://kubernetes.io/docs/concepts/services-networking/dual-stack/#configure-ipv4-ipv6-dual-stack
FYI, this makes our hack of rotating outbound NAT IPs to escape Docker Hub ratelimit not work as Docker Hub is served also over IPv6