Running Cluster API Provider out-of-cluster does not load AWS Shared Config for some controllers

[adammw]

/kind bug

What steps did you take and what happened:
Trying to run cluster-api-provider-aws out-of-cluster under a debugging IDE, the AWS Shared Config is partially loaded for some clusters, but for others Reconciler errors occur:

E0906 14:38:57.113013    1102 controller.go:329] "Reconciler error" err=<
        failed to create scope: failed to create aws session: Failed to retrieve identity credentials: NoCredentialProviders: no valid providers in chain. Deprecated.

What did you expect to happen:
Shared config is read where the session is created.

Anything else you would like to add:
It appears that all other parts of the codebase pass through SharedConfigEnable (example) however pkg/cloud/scope/session.go#L176 does not.

This can be worked-around by setting the AWS_SDK_LOAD_CONFIG environment variable to a truthy value.

Environment:

• Cluster-api-provider-aws version: master branch
• Kubernetes version: (use kubectl version): 1.30
• OS (e.g. from /etc/os-release): macOS

[k8s-ci-robot]

This issue is currently awaiting triage.

If CAPA/CAPI contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[bingikarthik]

We are experiencing same error:

I0917 06:12:17.996661       1 eksconfig_controller.go:220] "Control Plane has not yet been initialized" controller="eksconfig" controllerGroup="bootstrap.cluster.x-k8s.io" controllerKind="EKSConfig" EKSConfig="sbx-clusters/bkarthikcapa01-sbx-va6-system" namespace="sbx-clusters" name="bkarthikcapa01-sbx-va6-system" reconcileID="6aabadd5-4dd0-4a26-8c5b-9f1dc3e0823b"
E0917 06:12:30.825554       1 controller.go:329] "Reconciler error" err=<
	failed to create scope: failed to create aws session: Failed to retrieve identity credentials: NoCredentialProviders: no valid providers in chain. Deprecated.
		For verbose messaging see aws.Config.CredentialsChainVerboseErrors
 > controller="awsmanagedcontrolplane" controllerGroup="controlplane.cluster.x-k8s.io" controllerKind="AWSManagedControlPlane" AWSManagedControlPlane="sbx-clusters/bkarthikcapa01-sbx-va6" namespace="sbx-clusters" name="bkarthikcapa01-sbx-va6" reconcileID="eeedd573-e900-458b-878a-176cb7ac1877"

Is there any ETA for this?

[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

[k8s-triage-robot]

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

This bot triages 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:

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

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages 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:

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

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

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.