wide-judge-30323
04/24/2019, 4:25 AMstack:Stack::cluster-nodes: UPDATE_ROLLBACK_COMPLETE: ["The requested instance type's architecture (x86_64) does not match the architecture in the manifest for ami-0deb321f7b1c07d4c (arm64). Launching EC2 instance failed."]
The stack usually applies cleanly, and the changes were not directly related to the eks config.
I have noted that randomly the ami for nodes in the eks cluster have updated when I've done a pulumi up
- although a little disconcerting, I haven't worried about it - but now it's selected an invalid ami (it's not clear when / how it looks this up) and won't update. I don't see any way to lock this down to only change when explicitly updated. Has anyone else run into the error above?better-rainbow-14549
04/24/2019, 8:15 AMawait
an Output<>busy-umbrella-36067
04/24/2019, 3:23 PMoutput
as a placeholder for the value update, is this normal?
taskDefinition : "arn:aws:ecs:eu-west-1:xxxxx:task-definition/xxxxxr:18" => {"Element":{"V":""}}
jolly-lifeguard-22556
04/24/2019, 4:05 PMbusy-umbrella-36067
04/24/2019, 4:11 PM<http://app.pulumi.com|app.pulumi.com>
previews?full-dress-10026
04/24/2019, 5:14 PM.metrics
from a FargateService
?busy-umbrella-36067
04/24/2019, 6:12 PM[Object Object]/*
for me, is there any workaround for this?
let rolePolicy = new aws.iam.RolePolicy(`${name}-s3-access`, {
role: role.id,
policy: pulumi.output({
Version: "2012-10-17",
Statement: [{
Effect: "Allow",
Action: [
"s3:ListBucket",
"s3:HeadBucket",
"s3:PutObject",
"s3:GetObject"
],
Resource: [ bucket.arn, `${bucket.arn}/*` ]
}]
}).apply(JSON.stringify)
}, {
parent: role
});
better-rainbow-14549
04/24/2019, 7:32 PMcold-painting-74540
04/24/2019, 9:02 PMshy-army-45455
04/25/2019, 7:15 AMblue-dentist-627
04/25/2019, 9:49 AMconst cluster = new eks.Cluster('staging-auth', {
nodeAmiId: 'ami-0bfedee6a7845c26d',
vpcId,
subnetIds: subnet.split(','),
deployDashboard: false,
instanceType: 't2.medium',
desiredCapacity: 2,
nodeAssociatePublicIpAddress: false,
minSize: 2,
maxSize: 2,
nodekeyName: 'aws_tokyo',
storageClasses: 'gp2',
labels: {
cluster: 'proxy',
},
});
is somethings in my conf ?rapid-eye-32575
04/25/2019, 10:39 AMC¹
, C²
and C³
. Now I implemented two components called B¹
and B²
which now have C¹
and C²
and C³
as subordinated components respectively and those two components have the parent A
. When running pulumi up
the preview shows that this would cause Pulumi to tear down C¹
, C²
and C³
and create them new under B¹
and B²
.
Since those primitives represent important production infrastructure this would cause a brief service disruption for end users which I would like to avoid. Is there a way to tell Pulumi to just move the components without actually modifying the underlying infrastructure?busy-pizza-73563
04/25/2019, 12:59 PMbusy-pizza-73563
04/25/2019, 1:01 PMbetter-rainbow-14549
04/25/2019, 1:38 PMpulumi new
for the templatewonderful-noon-94894
04/25/2019, 2:06 PMmy-project-k8s
postgres.yml
ingress.yml
...
my-api
deployment.yml
wonderful-noon-94894
04/25/2019, 2:06 PMmy-project-k8s
repository?bitter-island-28909
04/25/2019, 4:09 PMhelpful-vegetable-35581
04/25/2019, 6:30 PMorange-tailor-85423
04/25/2019, 10:52 PMadamant-dress-73325
04/25/2019, 11:17 PMwonderful-noon-94894
04/26/2019, 11:46 AMearly-intern-90238
04/26/2019, 1:59 PMearly-intern-90238
04/26/2019, 2:00 PMearly-intern-90238
04/26/2019, 2:01 PMearly-intern-90238
04/26/2019, 2:01 PMearly-intern-90238
04/26/2019, 2:02 PMthousands-solstice-45099
04/26/2019, 4:27 PMhcloud
). What would be the release strategy for making it public? 🙂 I saw some deployment scripts in the boilerplate repository which transfer the provider plugin to a Pulumi S3 bucket, etc. I guess this is for the "official providers". What about community providers? 🙂full-dress-10026
04/26/2019, 6:55 PMcalm-greece-42329
04/26/2019, 7:52 PM