tall-beard-99429
12/02/2021, 12:55 PMcreate_before_destroy
as a flag in the configuration sectionbillions-hospital-77217
12/02/2021, 8:06 PMpulumi up
I'm getting issues with getting this error: error: failed to discover plugin requirements: 'dotnet build -nologo .' exited with non-zero exit code: 1
Here's my verbose log...
EDIT: Nvm I figured out I was doing weird stuff with my dependencies.steep-window-60101
12/02/2021, 8:18 PMambitious-salesmen-39356
12/05/2021, 1:16 AMpulumi preview --diff
with regard to IAM policies? It's basically unreadable in default form =\ambitious-salesmen-39356
12/05/2021, 2:54 AMdamp-school-17708
12/06/2021, 10:14 AMthankful-father-68341
12/06/2021, 12:46 PMpurple-application-23904
12/06/2021, 9:18 PMquaint-portugal-34880
12/07/2021, 6:15 AMbillowy-army-68599
wonderful-twilight-70958
12/08/2021, 1:12 PMuseDefaultVpcCni: false
it still gets installed 😕 Which, OK fine. But then I also can't 'import' it inline and annotate it without manual intervention (once to import without the annotation, then add the annotation, then run up
again).boundless-telephone-75738
12/08/2021, 1:55 PMaws eks describe-addon-versions --addon-name vpc-cni --kubernetes-version 1.21
) at least outputs v1.10.1, Default: true. Any hints for how to achive this?dry-teacher-74595
12/08/2021, 6:10 PMdry-teacher-74595
12/08/2021, 6:10 PMdry-teacher-74595
12/08/2021, 6:11 PMdry-teacher-74595
12/08/2021, 6:16 PMwonderful-twilight-70958
12/08/2021, 9:59 PMlemon-salesclerk-6224
12/09/2021, 2:36 AMstack.up()
output is now empty. Before i'd get the gateway url when deploying gateway + 2 lambdas. Now when deploying gateway + 4 lambdas i get an empty Outputs: {}
Any ideas?magnificent-battery-62880
12/09/2021, 4:24 PMeks = Cluster(
'eks-locust',
vpc_id=vpc.id,
public_subnet_ids=[subnet.id for subnet in dmz_subnets],
private_subnet_ids=[subnet.id for subnet in private_subnets],
cluster_security_group=sg,
kubernetes_service_ip_address_range='192.168.0.0/16',
vpc_cni_options=VpcCniOptionsArgs(cni_custom_network_cfg=True),
node_group_options=ClusterNodeGroupOptionsArgs(
min_size=2,
max_size=150,
node_associate_public_ip_address=False,
node_security_group=sg),
provider_credential_opts=KubeconfigOptionsArgs(
profile_name='671822246166_Admin'),
tags=common_tags
)
but I keep getting the error
Setting nodeGroupOptions, and any set of singular node group option(s) on the cluster, is mutually exclusive. Choose a single approach.I read through the source and can't figure out what's conflicting with
node_group_options
, anyone got any ideas what I'm doing wrong?
https://github.com/pulumi/pulumi-eks/blob/master/nodejs/eks/cluster.ts#L361-L375wide-jackal-86020
12/09/2021, 11:19 PMType Name Status Info
pulumi:pulumi:Stack control_api-staging **failed** 1 error
- └─ aws:apigateway:Deployment control_api **deleting failed** 1 error
Diagnostics:
aws:apigateway:Deployment (control_api):
error: deleting urn:pulumi:staging::control_api::aws:apigateway:x:API$aws:apigateway/deployment:Deployment::control_api: 1 error occurred:
* error deleting API Gateway Deployment (5ad3rk): BadRequestException: Active stages pointing to this deployment must be moved or deleted
pulumi:pulumi:Stack (control_api-staging):
error: update failed
Has anyone experienced this and knows how to fix it?rapid-keyboard-69273
12/10/2021, 5:07 PMsalmon-fish-42319
12/10/2021, 5:51 PMmammoth-airline-91759
12/10/2021, 11:02 PMnew awsx.ec2.Vpc("vpc-dev-1", {
cidrBlock: "10.0.0.0/16",
instanceTenancy: "default",
numberOfAvailabilityZones: 3,
numberOfNatGateways: 2,
});
I now realize I need some tags on each public and private subnet. Is there a way to easily go back and add those tags to each subnet without destroying and re-creating the entire stack?nutritious-tent-64795
12/14/2021, 1:17 AMdetails = "Setting nodeGroupOptions, and any set of singular node group option(s) on the cluster, is mutually exclusive. Choose a single approach."
We hit a number of failures on Friday, it began working again this weekend, and is now not working again.
Our code in question is here:
• https://github.com/nginxinc/kic-reference-architectures/blob/master/pulumi/aws/eks/__main__.py#L61-L65
• https://github.com/nginxinc/kic-reference-architectures/blob/master/pulumi/aws/eks/__main__.py#L73-L83
There is nothing being set outside of the node options that should cause this error (based on the logic in https://github.com/pulumi/pulumi-eks/blob/master/nodejs/eks/cluster.ts#L361-L375).
The output looks like this:
• https://gist.github.com/qdzlug/931c07928dca1c3ad6097d89227edc16
This issue started following the issues with AWS, but I don’t know if it’s related. This is under Pulumi v3.19.0 and all current versions of the pulumi python modules.mysterious-whale-31506
12/14/2021, 7:30 PMdefaultCapacityProviderStrategies
with a base of 1 and weight of 100, while adjusting my service definition from a testing desiredCount
of 1 to no desiredCount
entry at all.
I'm wondering which resource configuration I should be paying attention to. Any insights that may lead me to water are greatly appreciated!freezing-umbrella-5483
12/15/2021, 5:02 PMlittle-cartoon-10569
12/16/2021, 1:19 AMgreat-sunset-355
12/16/2021, 9:35 AMaws_native.ecs.Service
and I added replaceOnChanges: ["*"]
and the pulumi have been trying to create a replacement Service for more than 30 minutes and nothing is happening.nutritious-shampoo-16116
12/17/2021, 11:18 AM++aws:ec2/flowLog:FlowLog: (create-replacement)
[id=fl-XXX]
[urn=urn:pulumi:staging::XXX-vpc::XXX:AWS:Network$aws:ec2/vpc:Vpc$aws:ec2/flowLog:FlowLog::stusea1-XXX-vpc-flowlog]
[provider=urn:pulumi:staging::XXX-vpc::pulumi:providers:aws::default_4_26_0::XXX]
+ iamRoleArn: "arn:aws:iam::XXX:role/stusea1-XXX-vpc-flowlog-role-972cb33"
+-aws:ec2/flowLog:FlowLog: (replace)
[id=fl-XXX]
[urn=urn:pulumi:staging::XXX-vpc::XXX:AWS:Network$aws:ec2/vpc:Vpc$aws:ec2/flowLog:FlowLog::stusea1-XXX-vpc-flowlog]
[provider=urn:pulumi:staging::XXX-vpc::pulumi:providers:aws::default_4_26_0::XXX]
+ iamRoleArn: "arn:aws:iam::XXX:role/stusea1-XXX-vpc-flowlog-role-972cb33"
--aws:ec2/flowLog:FlowLog: (delete-replaced)
[id=fl-XXX]
[urn=urn:pulumi:staging::XXX-vpc::XXX:AWS:Network$aws:ec2/vpc:Vpc$aws:ec2/flowLog:FlowLog::stusea1-XXX-vpc-flowlog]
[provider=urn:pulumi:staging::XXX-vpc::pulumi:providers:aws::default_4_26_0::XXX]
seems pulumi wants to replace the ARN (which is the same) and this fails cause the resource already exist
this happens on every upnutritious-shampoo-16116
12/17/2021, 11:46 AM