janre

Same for me. `docker run -d --name eksa_1655969613989358333 --network host --entrypoint sleep public.ecr.aws/eks-anywhere/cli-tools:v0.7.2-eks-a-10 infinity` `docker exec -i -e HELM_EXPERIMENTAL_OCI=1 -e HTTP_PROXY=10.192.xxx.xxx:3128 -e HTTPS_PROXY=10.192.xxx.xxx:3128 eksa_1655969613989358333 helm template oci://public.ecr.aws/isovalent/cilium --version 1.9.13-eksa.2 --insecure-skip-tls-verify...

For me this works with lens v2023.3.171731-latest: ``` apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: some-really-cool-name rules: - apiGroups: - "" resources: - "namespaces" - "nodes" verbs: - "get" - "list"...

@etungsten Thank you! Same applies to vsphere-csi-driver in combination with eks anywhere. ``` kind: DaemonSet apiVersion: apps/v1 metadata: name: vsphere-csi-node namespace: vmware-system-csi spec: selector: matchLabels: app: vsphere-csi-node updateStrategy: type: "RollingUpdate"...

Same for me. The only workaround for us currently is to create a server with public ip and manually add it to a network with a static IP, then disable...

For me this works with lens v2023.3.171731-latest: ``` apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: some-really-cool-name rules: - apiGroups: - "" resources: - "namespaces" - "nodes" verbs: - "get" - "list"...

Any news on this?