quiet-architect-9124607/29/2021, 6:27 PM
on the full code given in the walkthrough Im running in the following issue: The cluster (not in the scope of the walkthrough but I create it in the same .go file just before the repository), image and repository are created without problem, but when trying to create the service using the image it fails since its trying to use my local .kube/config to access the cluster which isnt updated. When I manually update it for the newly generated cluster and run
again the service is created without problem. Is there anyway to hand in the kubeconfig from the cluster by using
in the service declaration somehow? I looked through all the Parameters used in
but couldnt find anything suitable. If anyone has any idea on how this could be solved Id greatly appreciate it!
billowy-army-6859907/29/2021, 6:54 PM
quiet-architect-9124607/29/2021, 7:15 PM
in comparison to
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-6859907/29/2021, 7:23 PM
quiet-architect-9124607/29/2021, 7:48 PM
billowy-army-6859907/29/2021, 7:59 PM
quiet-architect-9124607/29/2021, 8:55 PM
$ kubectl apply -f eks-console-full-access.yaml
billowy-army-6859907/29/2021, 8:57 PM
configmap problem 🙂 this is handled by the rolemappings property: https://www.pulumi.com/docs/reference/pkg/eks/cluster/#rolemapping
quiet-architect-9124607/29/2021, 9:02 PM
right? Its just mapping and not creating the group configured in the .yaml or am I missing a crucial point here?
billowy-army-6859907/29/2021, 9:08 PM
quiet-architect-9124607/29/2021, 9:31 PM