IgalSc

@olemarkus that's just lol But as for the `kops update cluster` - it doesn't work

@olemarkus thank you for this response I copied the actual CIDR from the AWS VPC console. I can see the error in the AWS Cloudtrail. I will reach out to...

So, it look like there's no need to specify the IPv6 CIDR for the VPC, ` networkCIDR: 172.30.0.0/16 additionalNetworkCIDRs: - 2600:abcd:efg:9000::/56` because 'additionalNetworkCIDRs' is IPv4 CIDR format. Specifying the 'ipv6CIDR'...

Following my previous update, I tried deleting the cluster, running the `kops create cluster` , then `kops edit cluster`, update the ipv6CIDRs for the subnets, and change the loadbalancer type...

Hi @olemarkus I actually figured out how to set up the cluster with Network LB and IPv6 Following my previous update, I was wrong with associating the Dashboard with the...

This problem was resolved by not touching the Master loadbalncer, but introducing the following `metadata: name: svc-nginx1 annotations: service.beta.kubernetes.io/aws-load-balancer-type: "nlb" service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: "ip" service.beta.kubernetes.io/aws-load-balancer-ip-address-type: "dualstack" ` under the nginx service deployment

Thank you !

@olemarkus By "load balancer controller addon" you mean spec.api.LoadBalancer? And network load balancer on a service config?

@olemarkus thank you! Where do I use the NLB then?

When I try to run` kubectl taint nodes --all node-role.kubernetes.io/control-plane` I get `error: at least one taint update is required ` `kubectl describe nodes | grep -i taint` ``` Taints:...