EKSAuthentication takes in AWSSessionCredentialsProvider instead of StsAssumeRoleCredentialsProvider

[JuiceW4H]

Describe the bug
EKSAuthentication() takes in AWSSessionCredentialsProvider class instead of StsAssumeRoleCredentialsProvider as per the example provided.

Client Version
24.0.0

Kubernetes Version
1.32

Java Version
Java 21

To Reproduce
Steps to reproduce the behavior: Simply use the EKSAuthentication() method with a variable of type StsAssumeRoleCredentialsProvider

[brendandburns]

I'm pretty sure that this is because the examples are for HEAD and you are using library version 24.0.0

If you are using the 24.0.0 version of the library, the examples can be found in that branch:

https://github.com/kubernetes-client/java/blob/release-24/examples/examples-release-latest/src/main/java/io/kubernetes/client/examples/EKSAuthenticationExample.java

[JuiceW4H]

In the v24.0.0 sample I think it still uses the AWS SDK v1 not v2

[JuiceW4H]

Upon checking there is already a fix in v25.0.0 tag but that version is not yet on maven as maven still only has v24.0.0

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten