https://pulumi.com
Join Slack
This message was deleted.
s

Slackbot

almost 6 years ago
This message was deleted.
s
l
j
  • 3
  • 8
  • 134
This message was deleted.
s

Slackbot

over 3 years ago
This message was deleted.
s
f
i
  • 3
  • 9
  • 133
This message was deleted.
s

Slackbot

over 3 years ago
This message was deleted.
s
j
m
  • 3
  • 8
  • 133
This message was deleted.
s

Slackbot

almost 4 years ago
This message was deleted.
s
j
+2
  • 4
  • 12
  • 133
This message was deleted.
s

Slackbot

about 5 years ago
This message was deleted.
s
l
  • 2
  • 1
  • 133
Hi everyone, I'm trying to upgrade EKS NodeGroup from AL2 to AL2023, based on <documentation>: ```U...
d

Dang Huy Nguyen

6 months ago
Hi everyone, I'm trying to upgrade EKS NodeGroup from AL2 to AL2023, based on documentation:
Update the node group in place. Pulumi does this by first creating the new replacement nodes and then shutting down the old ones which will move pods to the new nodes forcibly. This is the default behavior when node groups are updated.
It seems does not happen to me. The preview shows the strategy is
replace
instead of
update
-> entire nodeGroup will be deleted first, then creating new nodeGroup, instead of update node by node.
pulumi:pulumi:Stack: (same)
    [urn=urn:pulumi:stack::eks::pulumi:pulumi:Stack::stack]
    --aws:eks/nodeGroup:NodeGroup: (delete-replaced)
        [id=stack:test-upgrade]
        [urn=urn:pulumi:stack::eks::aws:eks/nodeGroup:NodeGroup::test-upgrade]
    +-aws:eks/nodeGroup:NodeGroup: (replace)
        [id=stack:test-upgrade]
        [urn=urn:pulumi:stack::eks::aws:eks/nodeGroup:NodeGroup::test-upgrade]
      ~ amiType: "AL2_x86_64" => "AL2023_x86_64_STANDARD"
    ++aws:eks/nodeGroup:NodeGroup: (create-replacement)
        [id=stack:test-upgrade]
        [urn=urn:pulumi:stack::eks::aws:eks/nodeGroup:NodeGroup::test-upgrade]
      ~ amiType: "AL2_x86_64" => "AL2023_x86_64_STANDARD"
Am I missing something?
d
f
c
  • 3
  • 10
  • 132
Hello! Has anyone had success with using custom component resources across multiple projects that ar...
j

Jon Kusz

11 months ago
Hello! Has anyone had success with using custom component resources across multiple projects that are stored outside of those projects? Something like:
my-pulumi-project
├── s3.ts
├── index.ts
├── ...
components
└── aws
    └── s3
        └── PrivateS3BucketV2.ts
The project dir includes the following
tsconfig.json
...
    "baseUrl": ".",
    "paths": {
      "*": ["node_modules/*", "../components/*"]
    }
  },
  "include": ["index.ts", "../components/**/*.ts"]
}
And I am importing like this:
import { PrivateS3BucketV2 } from '../components/aws/s3/PrivateS3BucketV2';
Ive not had much luck with this, seeing errors like
13 INTERNAL: Request message serialization failure: b.Va is not a function
. I am somewhat new to Typescript, am I missing something? Does Pulumi support this sort of pattern?
j
t
p
  • 3
  • 24
  • 132
This message was deleted.
s

Slackbot

over 4 years ago
This message was deleted.
s
e
+2
  • 4
  • 4
  • 132
This message was deleted.
s

Slackbot

over 2 years ago
This message was deleted.
s
n
+2
  • 4
  • 13
  • 131
This message was deleted.
s

Slackbot

over 3 years ago
This message was deleted.
s
r
r
  • 3
  • 3
  • 131
Previous323334Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by