full-dress-10026
05/22/2020, 8:25 PMthe daily CPU utilization was 10% or less and network I/O was 5 MB or less on 4 or more daysSpecifically, why would they have network I/O 5mb or less on 4 or more days? Why not the whole duration they look over (2 weeks)? Why not 2 days? Do instances typically run some sort of small update every 5 days or something?
astonishing-gpu-37274
05/25/2020, 8:23 AMacceptable-stone-35112
05/25/2020, 5:23 PMrunning panic: fatal: An assertion has failed: Expected diff to not require deletion or replacement during Update of urn:pulumi:dev::my-stack::aws:apigateway/deployment:Deployment::
salmon-ghost-86211
05/27/2020, 2:42 PMExample Usage
code at <https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/aws/route53/#getZone>
when the hosted zone name does not exist. I can't even trap it with a try...catch statement (I'm using typescript).
Error messages are like
error: Running program '/home/bbaker/dev/infrastructure/eks/Pulumi' failed with an unhandled exception:
Error: invocation of aws:route53/getZone:getZone returned an error: invoking aws:route53/getZone:getZone: no matching Route53Zone found
at /home/bbaker/dev/infrastructure/eks/Pulumi/node_modules/@pulumi/pulumi/runtime/invoke.js:136:33
at Http2CallStream.<anonymous> (/home/bbaker/dev/infrastructure/eks/Pulumi/node_modules/@grpc/grpc-js/src/client.ts:155:9)
at Http2CallStream.emit (events.js:322:22)
at Http2CallStream.EventEmitter.emit (domain.js:482:12)
at /home/bbaker/dev/infrastructure/eks/Pulumi/node_modules/@grpc/grpc-js/src/call-stream.ts:186:14
at processTicksAndRejections (internal/process/task_queues.js:79:11)
How do I check if a hosted zone exists?delightful-controller-26409
05/27/2020, 3:41 PMPulumi up
with the new code on a new stack, I get:
Which makes sense - the bucket does already exist. I don't want to destroy and recreate anything - I just want to have these existing resources be managed by this new code and stack. I'd then like to be able to remove the creation of these resources from the old Typescript code. Is the answer something to do withError creating S3 bucket: BucketAlreadyOwnedByYou: Your previous request to create the named bucket succeeded and you already own it
pulumi stack import
?best-receptionist-98400
05/27/2020, 6:16 PMvar spotOutput = Pulumi.Aws.Ec2.SpotInstanceRequest.Get(spotRequest.GetResourceName(), spotRequest.Id, null, new CustomResourceOptions
{
DependsOn = spotRequest
});
But it keeps giving me an error: of
aws:ec2:SpotInstanceRequest (dev-request-1):
error: resource 'urn:pulumi:dev::aws-spot::aws:ec2/spotInstanceRequest:SpotInstanceRequest::dev-request-1' registered twice (create and read)
error: resource 'urn:pulumi:dev::aws-spot::aws:ec2/spotInstanceRequest:SpotInstanceRequest::dev-request-1' registered twice (create and read)
best-receptionist-98400
05/27/2020, 6:18 PMdazzling-sundown-39670
05/27/2020, 8:45 PMexternal-dns
pods but I'm not sure how I can allow it. Currently I'm getting this error: AccessDenied: User: arn:aws:sts::503405380068:assumed-role/k8s-pulumi-instanceRole-role-683d5cc/i-0a89701e04130e505 is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::503405380068:role/update-route53-4397bfb
I guess I need to attach it to my cluster somehow? I've tried serviceRole and instanceRole but the diff shows too many affected resourcesdazzling-sundown-39670
05/27/2020, 9:04 PMserviceRole
in @pulumi/eks
glamorous-printer-14057
05/28/2020, 2:46 AMpulumi up
is now stuck hanging for me, and I’m not quite sure what changed. is there some way to get out of this state?little-cartoon-10569
05/28/2020, 5:06 AMerror: error listing stacks: could not list bucket: blob (code=Unknown): MissingRegion: could not find region configuration
and don't know how to start diagnosing.wonderful-dog-9045
05/28/2020, 6:17 PMlittle-cartoon-10569
05/28/2020, 9:52 PMdazzling-sundown-39670
05/30/2020, 11:27 PMicy-napkin-56528
06/01/2020, 9:40 AMicy-napkin-56528
06/01/2020, 9:43 AMsparse-state-34229
06/01/2020, 4:50 PMvictorious-country-25661
06/01/2020, 10:19 PMpulumi config set aws:region <value>
.
I've configured the aws:region through pulumi config set aws:region value but I'm still blocked by this error.sparse-state-34229
06/01/2020, 10:21 PMpulumi config get aws:region
?victorious-country-25661
06/01/2020, 10:22 PMsparse-state-34229
06/01/2020, 10:22 PMhead -3 <your stack.yaml>
sparse-state-34229
06/01/2020, 10:22 PMvictorious-country-25661
06/01/2020, 10:23 PMsparse-state-34229
06/01/2020, 10:23 PMdazzling-sundown-39670
06/02/2020, 7:06 AMcalm-greece-42329
06/04/2020, 12:06 AMacceptable-stone-35112
06/05/2020, 10:14 AMhundreds-musician-51496
06/06/2020, 5:56 PMplain-park-4925
06/08/2020, 2:41 AM<http://localhost:4566>
so that it hits my LocalStack environment. I think I might have kind of got it to work but now I receive this error..
pulumi up
Enter your passphrase to protect config/secrets:
Re-enter your passphrase to confirm:
Previewing update (pulumi-localstack-test):
Type Name Plan Info
+ pulumi:pulumi:Stack s3bucket-localstack-pulumi-localstack-test create
+ ├─ pulumi:providers:aws provider create
+ ├─ aws:s3:Bucket jon-pulumi-localstack-bucket create
└─ aws:s3:BucketObject index.html 1 error
Diagnostics:
aws:s3:BucketObject (index.html):
error: could not validate provider configuration: 1 error occurred:
* : invalid or unknown key: endpoint_url
cold-coat-35200
06/08/2020, 5:50 AMconst autoScalingGroup = new aws.autoscaling.Group(
`${name}-autoScalingGroup`,
{
desiredCapacity: args.minSize,
launchConfiguration: nodeLaunchConfiguration,
minSize: args.minSize,
maxSize: args.maxSize,
vpcZoneIdentifiers: args.subnetIds,
tags: tags,
targetGroupArns: args.targetGroupArns,
loadBalancers: args.classicLoadBalancerNames,
},
{ parent: this, ignoreChanges: ['desiredCapacity'] }
)
args.targetGroupArns
defined as
readonly targetGroupArns?: pulumi.Input<pulumi.Input<string>[]>
Same as on the original pulumi aws resource.
Called this way:
const transcoderAzWorkerNodes = new eks.WorkerNodeGroup(`${stack}-transcoder-wg-1.14`, {
amiID: workerConfig.amiID,
subnetIds: vpcDliverOutput.vpc.publicIpSubnetIds,
clusterName: cluster.name,
clusterEndPoint: cluster.endpoint,
clusterCertificateAuthority: cluster.certificateAuthority,
clusterInstanceRole: cluster.sharedWorkerInstanceRole,
minSize: workerConfig.transcoder.minSize,
maxSize: workerConfig.transcoder.maxSize,
instanceType: workerConfig.transcoder.instanceType,
nodeSecurityGroupID: vpcDliverOutput.securityGroup.worker.rtmpTranscoder.id,
nodeRootVolumeSize: 25,
nodePublicKeyName: workerSSHKey.keyName,
kubeletExtraArgs: '--node-labels <http://dliver.com/stack=transcoder|dliver.com/stack=transcoder>',
targetGroupArns: [groupRtmp.targetGroupArn]
})
The problem is that when we deleted targetGroupArns: [groupRtmp.targetGroupArn]
from the calling code, pulumi does not update the resource, did not show any updates.
If we change to this targetGroupArns: []
instead of deleting, then works as expected.
Is this a normal behavior?
I assume not, pulumi should recognize the change in both cases.