sparse-intern-71089
07/29/2021, 6:27 PMbillowy-army-68599
quiet-architect-91246
07/29/2021, 7:15 PM<http://github.com/pulumi/pulumi-eks/sdk/go/eks|github.com/pulumi/pulumi-eks/sdk/go/eks>
in comparison to <http://github.com/pulumi/pulumi-aws/sdk/v4/go/aws/eks|github.com/pulumi/pulumi-aws/sdk/v4/go/aws/eks>
as you linked in the example. Im kinda wondering here whats the difference between them since both expose somewhat comparable methods (for example .newCluster()), but also dont seem to be interchangable.billowy-army-68599
quiet-architect-91246
07/29/2021, 7:48 PMbillowy-army-68599
billowy-army-68599
cluster.Provider
object now!quiet-architect-91246
07/29/2021, 8:55 PM$ kubectl apply -f eks-console-full-access.yaml
(https://aws.amazon.com/de/premiumsupport/knowledge-center/eks-kubernetes-object-access-error/)?billowy-army-68599
aws-auth
configmap problem 🙂
this is handled by the rolemappings property: https://www.pulumi.com/docs/reference/pkg/eks/cluster/#rolemappingquiet-architect-91246
07/29/2021, 9:02 PMkubectl apply
right? Its just mapping and not creating the group configured in the .yaml or am I missing a crucial point here?billowy-army-68599
billowy-army-68599
ConfigFile
resource:
https://www.pulumi.com/docs/reference/pkg/kubernetes/yaml/configfile/quiet-architect-91246
07/29/2021, 9:31 PM