purple-plumber-90981
05/03/2021, 9:08 PMaws eks --region us-east-1 update-kubeconfig
and pulumi config set kubernetes:context
outside of the stackkubeconfig = eks_cluster.kubeconfig
AttributeError: 'Cluster' object has no attribute 'kubeconfig'
<https://github.com/pulumi/examples/blob/master/aws-py-eks/utils.py>
and that looks like how to generate kubeconfig from eks cluster object…. i just assumed it would be built in to the cluster classgorgeous-egg-16927
05/03/2021, 9:25 PMprovider
attribute: https://www.pulumi.com/docs/reference/pkg/eks/cluster/#provider_pythonpurple-plumber-90981
05/03/2021, 9:34 PMDiagnostics:
kubernetes:core/v1:Namespace (mynamespace):
error: connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:50814: connect: connection refused"
pulumi:pulumi:Stack (aws_eks-itplat-aws-eks):
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0x291f5c2]
goroutine 40 [running]:
<http://github.com/pulumi/pulumi-kubernetes/provider/v3/pkg/provider.getActiveClusterFromConfig(0xc00010c600|github.com/pulumi/pulumi-kubernetes/provider/v3/pkg/provider.getActiveClusterFromConfig(0xc00010c600>, 0xc00032f680, 0xc0000add80)
gorgeous-egg-16927
05/03/2021, 10:13 PMpulumi_eks
is a good starting point because it handles a lot of the relevant IAM and networking bits as well. You can set all of that up using the aws provider directly as well, but it takes more work up front.purple-plumber-90981
05/03/2021, 10:37 PM