Filip Křepinský

Hi @parispittman , I would like to sign up for this cohort with a preference for sig-apps and ackowledge the requirements.

/assign @atiratree

I think it should be enough to ouput a warning instead of an error: I started a PR that fixes that: https://github.com/kubernetes/kubernetes/pull/110752 nit: > kubectl auth can-i create pods/foobarbaz this...

@amarshall this seems like a duplicate of https://github.com/kubernetes/kubernetes/issues/91913. Can you please try again with latest kubectl? sidenote: I have also tested this with plain kubernetes (not aws-iam) and have not...

TY, I managed to reproduce #1152 on AWS EKS (1.21) with latest kubectl. Vanilla kubernetes works fine. seeing multiple connections: ``` kubectl 430171 user 18u IPv4 2968415 0t0 TCP p1:49786->ec2-IP.eu-central-1.compute.amazonaws.com:https...

This bug applies to all commands (create/apply/delete/describe) that use Exec credentials plugin Description of the current code flow and behaviour for kubectl delete: when running delete https://github.com/kubernetes/kubernetes/blob/267272efe0725e14b3c2c7bc6fa3dd64a922a6a7/staging/src/k8s.io/kubectl/pkg/cmd/delete/delete.go#L212 with client obtained...

^ I think the fix should be just to enable the TLS caching for this Exec plugin use case: - the dial is a basic Dial with just a connection...

posted a PR with a fix https://github.com/kubernetes/kubernetes/pull/108274 until that gets accepted a following workaround can be used: ```bash TOKEN="`AWS_PROFILE=my-profile aws --region my-region eks get-token --cluster-name my-cluster | jq ".status.token" |...

> I think the fix should be just to enable the TLS caching for this Exec plugin use case: This approach was discussed in https://github.com/kubernetes/kubernetes/pull/108274#discussion_r812046486 and was not shown as...

@brianpursley Thanks, I had to get down to the ConfigFlags to support also the DiscoverClient. Please see https://github.com/kubernetes/kubernetes/pull/108459 for the implementation.