calm-kitchen-4682
11/15/2022, 2:15 PMnodeSelector
to restrict where the pod should be placed but I see Pulumi adding extra fields for me in the resulting YAML which leads to no node being selected during scheduling phase (please note the node_selector
field in the Python snippet below).
Does Pulumi add its own nodegroup
selector as filtering criteria in addition to what I'm trying to filter on and if yes how do I prevent it from happening?
p_k8.apps.v1.Deployment(
'{}-deployment-{}'.format(service, customer),
metadata=p_k8.meta.v1.ObjectMetaArgs(
name=app,
namespace=name_space,
),
spec=p_k8.apps.v1.DeploymentSpecArgs(
replicas=1,
strategy=p_k8.apps.v1.DeploymentStrategyArgs(
type='RollingUpdate',
),
selector=p_k8.meta.v1.LabelSelectorArgs(
match_labels={
'app': app,
},
),
template=p_k8.core.v1.PodTemplateSpecArgs(
metadata=p_k8.meta.v1.ObjectMetaArgs(
labels={
'app': app,
},
),
spec=p_k8.core.v1.PodSpecArgs(
termination_grace_period_seconds=5,
image_pull_secrets=[{
'name': 'my-secrets',
}],
containers=[
p_k8.core.v1.ContainerArgs(...omitted...),
],
node_selector={
'<http://kubernetes.io/os|kubernetes.io/os>': 'linux' # <--- This gets expanded into 2 selectors: a 'nodegroup' one and mine
},
),
),
))
The relevant section of the resulting yaml of the Pod which fails to be scheduled due to the extra nodegroup
label added by Pulumi looks something like this. Why is the extra nodegroup
label being added and how do I prevent it from happening?delightful-computer-48592
11/15/2022, 2:47 PMpulumi stack --show-urns
I’m getting in the output something like this:
TYPE NAME
pulumi:pulumi:Stack infra
│ URN: urn:pulumi:xxxx
├─ pulumi:providers:aws cluster
│ URN: urn:pulumi:xxxx
├─ pulumi:providers:aws default
│ URN: urn:pulumi:xxxx
├─ infra:k8s-cluster-v2 cluster-2
│ │ URN: urn:pulumi:xxxx
and I would like to get results only by NAME=cluster
.
Is it possible to do it without using a third-party tool like grep, sed, etc?hundreds-jackal-10148
11/15/2022, 6:13 PMfast-easter-23401
11/16/2022, 1:45 AMgreat-jackal-59572
11/16/2022, 6:13 PMlittle-soccer-5693
11/16/2022, 7:10 PMsalmon-motherboard-78006
11/16/2022, 8:38 PMid
of a specific Pulumi run/exeuction?
Let’s say I run pulumi up
I’m sure there is a unique ID attached to this run, how can I grab it?rapid-eve-24229
11/17/2022, 2:17 AMpulumi==3.46.1
pulumi-aws==5.21.0
pulumi-docker==3.1.0
python-dotenv==0.21.0
What can I do to deploy the stack? Thanksclever-soccer-98174
11/17/2022, 2:32 AMtall-crowd-93084
11/17/2022, 11:05 AMorg/repo-template
forked to org/{name}-repo
where name
parameterizes a load of other infra that's set up (one per customer).
Questions:
• Can I specify where to fork from when creating a github.Repository
or do I need to use a template
• What kind of access token do I need?
• How do I specify which organisation to create the repo in?delightful-camera-97029
11/17/2022, 11:08 AMdelightful-camera-97029
11/17/2022, 11:08 AMdelightful-camera-97029
11/17/2022, 11:09 AMdelightful-camera-97029
11/17/2022, 11:10 AMdelightful-camera-97029
11/17/2022, 11:10 AMdelightful-camera-97029
11/17/2022, 11:10 AMdelightful-camera-97029
11/17/2022, 11:11 AMbillions-xylophone-85957
11/17/2022, 11:59 AMnew pulumiResource
?careful-apartment-69053
11/17/2022, 3:36 PMMicrosoft.Compute/virtualMachines : azure-native:compute:VirtualMachine
hallowed-printer-89159
11/17/2022, 3:42 PMfuture-france-34957
11/17/2022, 6:16 PMrequirements.txt
pulumi_aws_native>=0.41.0<1.0.0
But that doesn’t seem to be the case for aws-native
Pulumi version used: v3.43.1
$ pulumi up
Previewing update (sitka/uat)
View Live: <https://app.pulumi.com/sitka/env-app/uat/previews/5631a648-bebb-4f25-b6bd-bd739dd68b2a>
error: could not load plugin for aws-native provider 'urn:pulumi:uat::env-app::pulumi:providers:aws-native::default': Could not automatically download and install resource plugin 'pulumi-resource-aws-native'at version v0.22.1-alpha.1661750811, install the plugin using `pulumi plugin install resource aws-native v0.22.1-alpha.1661750811`.
Underlying error: error downloading plugin aws-native to file: failed to download plugin: aws-native-0.22.1-alpha.1661750811: 403 HTTP error fetching plugin from <https://get.pulumi.com/releases/plugins/pulumi-resource-aws-native-v0.22.1-alpha.1661750811-darwin-amd64.tar.gz>
I have aws-native
0.41.0
installed
$ pulumi plugin ls | grep 'NAME\|aws-native'
NAME KIND VERSION SIZE INSTALLED LAST USED
aws-native resource 0.41.0 92 MB 2 hours ago 30 minutes ago
aws-native resource 0.39.0 92 MB 3 weeks ago 3 weeks ago
aws-native resource 0.29.0 84 MB 2 months ago 2 months ago
aws-native resource 0.19.1-alpha.1660828085+dfb123ac 86 MB 3 months ago 3 months ago
aws-native resource 0.19.1-alpha.1660126749+9e28f183 84 MB 3 months ago 3 months ago
aws-native resource 0.19.1-alpha.1659013975+9c6f4698 84 MB 3 months ago 3 months ago
aws-native resource 0.19.1-alpha.1656019149+c2daf7c7 87 MB 4 months ago 4 months ago
aws-native resource 0.19.0 87 MB 4 months ago 2 months ago
Why is pulumi attempting to use aws-native-0.22.1-alpha.1661750811
, which no longer exists, locally or on get.pulumi.com?salmon-motherboard-78006
11/17/2022, 6:55 PMDeliveryStreamType
with the aws
sdk, but it’s only available with aws-native
. Any idea why?
https://www.pulumi.com/registry/packages/aws-native/api-docs/kinesisfirehose/deliverystream/
CF seems to have this field:
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-kinesisfirehose-deliverystream.html#cfn-kinesisfireh[…]eliverystreamtypeglamorous-australia-21342
11/17/2022, 9:38 PMsticky-bear-14421
11/18/2022, 7:52 AMdelightful-computer-48592
11/18/2022, 2:33 PM--supress-outputs
in Pulumi GitHub actions? There is no option and I can’t find an environment variable to set either.little-library-54601
11/18/2022, 2:40 PMerror: the stack is currently locked by 1 lock(s). Either wait for the other process(es) to end or delete the lock file with `pulumi cancel`.
I had to cancel a workflow run because of an error in the workflow file. I'm sure that's why the lock file is hanging around.
But I can't "pulumi cancel" in the workflow itself. Can I run "pulumi cancel" from the command line to get the required effect? Or is it safe to delete the lock file from the place where it lives (azure storage blob)?
Thanks.echoing-dress-72742
11/18/2022, 2:42 PMvar resourceGroup = new Pulumi.AzureNative.Resources.ResourceGroup("rg-nicolai", new ResourceGroupArgs()
{
ResourceGroupName = "tst-rg-nicolai",
Location = "Norway East"
}, new CustomResourceOptions(){Provider = azProv});
What are the differences here, I mean ResourceGroup(“what are inside here”)
And compared to ResourceGroupNamefew-carpenter-12885
11/18/2022, 3:56 PMcustomTimeouts
on each individual resource, but I was not able to find anything about an overall stack timeout. For my use-case, I'm wanting to run the automation API inside AWS Lambda - so I want to stay within the Lambda timeout.chilly-plastic-75584
11/18/2022, 5:56 PMfierce-dinner-64337
11/18/2022, 8:05 PMfierce-dinner-64337
11/18/2022, 8:05 PMstocky-restaurant-98004
11/18/2022, 8:38 PMnew
something up, it will create it (or change if necessary). If something is in Pulumi state and it's not longer in your Pulumi program, it will delete it.fierce-dinner-64337
11/18/2022, 8:40 PMstocky-restaurant-98004
11/18/2022, 8:41 PMnew
up, Pulumi will manage its lifecycle.fierce-dinner-64337
11/18/2022, 8:42 PMstocky-restaurant-98004
11/18/2022, 8:42 PMfierce-dinner-64337
11/18/2022, 8:43 PMstocky-restaurant-98004
11/18/2022, 8:44 PMfierce-dinner-64337
11/18/2022, 8:45 PMstocky-restaurant-98004
11/18/2022, 8:45 PMfierce-dinner-64337
11/18/2022, 8:45 PMstocky-restaurant-98004
11/18/2022, 8:46 PMfierce-dinner-64337
11/18/2022, 8:47 PMstocky-restaurant-98004
11/18/2022, 8:47 PMfierce-dinner-64337
11/18/2022, 8:48 PMstocky-restaurant-98004
11/18/2022, 8:50 PMfierce-dinner-64337
11/18/2022, 8:51 PMstocky-restaurant-98004
11/18/2022, 8:52 PMfierce-dinner-64337
11/18/2022, 8:53 PMstocky-restaurant-98004
11/18/2022, 8:53 PMfierce-dinner-64337
11/18/2022, 8:56 PMstocky-restaurant-98004
11/18/2022, 8:56 PMfierce-dinner-64337
11/18/2022, 8:56 PMstocky-restaurant-98004
11/18/2022, 8:56 PMfierce-dinner-64337
11/18/2022, 8:57 PMstocky-restaurant-98004
11/18/2022, 8:58 PMfierce-dinner-64337
11/18/2022, 9:00 PMstocky-restaurant-98004
11/18/2022, 9:01 PMfierce-dinner-64337
11/18/2022, 9:01 PM