tall-monitor-77779
11/05/2018, 5:51 PMpulumi up
programatically?early-musician-41645
11/05/2018, 7:06 PMaws-node
.
I thought that it was managed outside the pulumi stack and raising the error, but that's not the case. I've now confirmed that it's failing even if the entire stack is managed by Pulumi.
I first destroyed all the resources, then I pulumi up
which creates an EKS cluster and a helm chart. The helm chart has a ServiceAccount and it fails with this:
Diagnostics:
kubernetes:core:ServiceAccount (kube-system/aws-node):
error: Plan apply failed: serviceaccounts "aws-node" already exists
The expected behavior is that the existing ServiceAccount would not raise an error and instead would get treated as a no-op.early-musician-41645
11/05/2018, 7:06 PMearly-musician-41645
11/05/2018, 7:15 PMcold-train-5848
11/05/2018, 8:43 PM127.0.0.1:5000
. It seems to login correctly with the credentials, but when it tries to push the built image, it seems like it's not passing on the servername to the docker push commands.
const myAppDocker = new docker.Image("myapp", {
build: {
context: '../',
dockerfile: '../docker/myapp/Dockerfile'
},
imageName: "myapp",
registry: {
server: "127.0.0.1:5000",
username: config.require("dockerUsername"),
password: config.require("dockerPassword")
},
});
error: Error: 'docker push myapp:f61cb689da...' failed with exit code 1
The push refers to repository [<http://docker.io/library/myapp|docker.io/library/myapp>]
early-musician-41645
11/05/2018, 9:20 PMkubectl apply -f $path_to_file
with Pulumi?agreeable-truck-14797
11/05/2018, 9:31 PMagreeable-truck-14797
11/05/2018, 9:31 PMagreeable-truck-14797
11/05/2018, 9:34 PMagreeable-truck-14797
11/05/2018, 9:34 PMagreeable-truck-14797
11/05/2018, 9:34 PMstocky-spoon-28903
11/05/2018, 9:35 PMagreeable-truck-14797
11/05/2018, 9:35 PMstocky-spoon-28903
11/05/2018, 9:35 PMagreeable-truck-14797
11/05/2018, 9:36 PMagreeable-truck-14797
11/05/2018, 9:37 PMstocky-spoon-28903
11/05/2018, 9:37 PMagreeable-truck-14797
11/05/2018, 9:39 PMagreeable-truck-14797
11/05/2018, 9:39 PMstocky-spoon-28903
11/05/2018, 9:39 PMstocky-spoon-28903
11/05/2018, 9:39 PMstocky-spoon-28903
11/05/2018, 9:39 PMagreeable-truck-14797
11/05/2018, 9:40 PMagreeable-truck-14797
11/05/2018, 9:40 PMagreeable-truck-14797
11/05/2018, 9:40 PMearly-musician-41645
11/05/2018, 9:40 PMkube-system/aws-auth
ConfigMap in my EKS kubernetes cluster via Pulumi. What's the route to doing that? I'm looking to add a couple roles into the data.mapRoles
agreeable-truck-14797
11/05/2018, 9:41 PM$Creds = (Use-STSRole -RoleArn $RoleArn -RoleSessionName "SandBoxSession" -SerialNumber $SerialNumber -TokenCode 123456).Credentials
stocky-spoon-28903
11/05/2018, 9:43 PMAWS_ACCESS_KEY_ID
, AWS_SECRET_ACCESS_KEY
and AWS_SESSION_TOKEN
in the environment. The provider does have native support for assuming a role thoughstocky-spoon-28903
11/05/2018, 9:44 PMagreeable-truck-14797
11/05/2018, 9:46 PM