full-dress-10026
05/31/2019, 2:51 AMnew aws.iam.RolePolicyAttachment("eks-node-role-assignment", {
policyArn: nodePolicy.arn,
role: eksCluster.instanceRole
})
This is throwing an exception:
Running program '/home/kenny/compute_software/infrastructure/pulumi-k8s-src' failed with an unhandled exception:
Error: Missing required property 'role'
Any idea why? Do I need to explicitly pass the role when creating the EKS cluster?.instanceRole
is undefined.instanceRoles
on my eks.Cluster
, I receive:
error: Running program '/home/kenny/compute_software/infrastructure/pulumi-k8s-src' failed with an unhandled exception:
Error: an instanceProfile is required
at Object.createNodeGroup (/home/kenny/compute_software/infrastructure/pulumi-k8s-src/node_modules/@pulumi/nodegroup.ts:238:15)
at new Cluster (/home/kenny/compute_software/infrastructure/pulumi-k8s-src/node_modules/@pulumi/cluster.ts:597:37)
at Object.<anonymous> (/home/kenny/compute_software/infrastructure/pulumi-k8s-src/src/index.ts:123:18)
at Module._compile (module.js:653:30)
at Module.m._compile (/home/kenny/compute_software/infrastructure/pulumi-k8s-src/node_modules/ts-node/src/index.ts:439:23)
at Module._extensions..js (module.js:664:10)
at Object.require.extensions.(anonymous function) [as .ts] (/home/kenny/compute_software/infrastructure/pulumi-k8s-src/node_modules/ts-node/src/index.ts:442:12)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
instanceRole
on the eks.Cluster
works but breaks lots of other things (i.e. coredns cannot be pulled from ECR). Looking at the code for Cluster
, I see there is a eksRole
and a instanceRole
. Not sure what the difference is.shy-receptionist-99213
05/31/2019, 6:02 AMfull-dress-10026
05/31/2019, 3:01 PMdamp-book-35965
05/31/2019, 3:46 PMfull-dress-10026
05/31/2019, 3:54 PMcreateNodeGroup
. I'm surprised how fragile this is.deployDashboard: true,
when using createNodeGroup
?createNodeGroup
because there are no nodes in the cluster. Unfortunately the dashboard code is not exposed as an API in the eks package either 😞damp-book-35965
05/31/2019, 4:15 PMfull-dress-10026
05/31/2019, 4:16 PMdamp-book-35965
05/31/2019, 4:16 PMfull-dress-10026
05/31/2019, 4:16 PMdamp-book-35965
05/31/2019, 4:17 PMdeployDashboard: false
and then change to true
in a second pulumi up
full-dress-10026
05/31/2019, 4:18 PMdamp-book-35965
05/31/2019, 4:19 PMfull-dress-10026
05/31/2019, 4:20 PMdamp-book-35965
05/31/2019, 4:22 PMshy-receptionist-99213
05/31/2019, 5:50 PMfull-dress-10026
05/31/2019, 7:25 PMnew k8s.helm.v2.Chart("k8s-dashboard", {
repo: "stable",
chart: "kubernetes-dashboard",
version: "1.10.1"
}, {providers: {kubernetes: k8sProvider}});
but I get
Error: Command failed: helm fetch stable/kubernetes-dashboard --untar --version 1.10.1 --destination /tmp/tmp-13188EbwU1rymTPCU
Error: chart "kubernetes-dashboard" matching 1.10.1 not found in stable index. (try 'helm repo update'). No chart version found for kubernetes-dashboard-1.10.1
According to https://hub.helm.sh/charts/stable/kubernetes-dashboard the latest version is either 1.10.1 or 1.5.2. I tried both and they both result in the above error.helm fetch stable/kubernetes-dashboard --version 1.5.2
locally, it works.