Mike Stefaniak

Adding some clarification here. Not the entire OIDC provider needs to be public to work with EKS. Only two particular URLs need to be publicly accessible, everything else can be...

Cluster access management controls are now the recommended replacement for aws-auth config map, and fully support by the EKS ACK controller https://aws.amazon.com/blogs/containers/a-deep-dive-into-simplified-amazon-eks-access-management-controls/

Newly created EKS v1.30+ clusters no longer add the default annotation to the storage class applied to the cluster.

Closing as this is now available in EKS v1.30, for example you will see this label on your nodes ```topology.k8s.aws/zone-id=usw2-az2```

https://github.com/eksctl-io/eksctl/blob/main/examples/27-oidc-provider.yaml

I have Pod Identity working with Argo CD, need to be using at least v2.10 ``` ArgoCDDeployerRole: Type: AWS::IAM::Role Properties: RoleName: "ArgoCDDeployerRole" Description: "Role for Argo CD deployment" AssumeRolePolicyDocument: Version:...

The latest version of the EKS Add-on for CoreDNS contains a parameter named `annotationTopologyMode` with possible values of `Disabled` or `Auto` (`Disabled` being the default). When set to Auto, Topology...

Closing as duplicate of #2274

Hey @1999Pra is this just an error log that shows in controller logs? Or are you actually noticing issues with the installation and process and functionality.

Our understanding is just a spurious log message gets printed that you can safely ignore ```E1220 20:48:11.694896 1 reflector.go:140] k8s.io/[email protected]/tools/cache/reflector.go:169: Failed to watch *v1.VolumeSnapshotContent: failed to list *v1.VolumeSnapshotContent: the server...