Skip to content
This repository was archived by the owner on Oct 8, 2025. It is now read-only.
This repository was archived by the owner on Oct 8, 2025. It is now read-only.

Kubeconfig file is not written during EKS project; exits with error #47

@qdzlug

Description

@qdzlug

Describe the bug
In certain configuration environments, the EKS build project fails to write to the kubeconfig file. The project aborts with this error:

Using AWS profile [f5] from Pulumi configuration
adding eks-sample-pulumi361-eksCluster-8dd5b98 cluster to local kubeconfig

'NoneType' object is not iterable

To Reproduce
Steps to reproduce the behavior:

  1. In an environment where you have custom kubeconfig contexts including GCP clusters.
  2. Select any context.
  3. Run the build.

I am doing additional work to drill this down to what is happening, but so far it seems to be tied to the way the gcloud utility updates the configuration.

Expected behavior
The project should run to completion w/o errors (ie, the kubeconfig should be created).

Your environment

  • Linux amd64
  • Master Branch
  • Pulumi / AWS

Additional context
None

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions