https://pulumi.com
Join Slack
This message was deleted.
# kubernetes
s
This message was deleted.
b
It will just transform that YAML into resources, so the end result will be the same
Here's an example of that with a single YAML file that contains multiple documents:
g
Both approaches will create the same resources, but there are several advantages to using the API directly: 1. You have more control over resource ordering 2. It’s easier to access resource values 3. It’s easier to refactor into components to abstract away details as needed
m
Thanks for your feedback. Looks the approach with yaml.ConfigGroup helps me with this issue https://github.com/pulumi/pulumi-kubernetes/issues/1242 Looks the pulumi system to control the PVC resource keeps waiting for PVC to be ready. but for the PVC to be ready needs the deployment resource to be deployed
g
Ah, thanks for the update. You should also be able to work around this issue by setting the 
<http://pulumi.com/skipAwait|pulumi.com/skipAwait>
annotation on the PVC. We occasionally run into circular dependencies like this, and that annotation tells Pulumi not to wait for it. https://www.pulumi.com/blog/improving-kubernetes-management-with-pulumis-await-logic/#new-annotations-to-customize-kubernetes-await-logic
👍 1
m
Thanks alot for the tip, it works
🎉 1
3 Views
Open in Slack
PreviousNext
Powered by

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