Channels
welcome
pulumi-cdk
cloudengineering
yaml
blog-posts
localstack
pulumi-ai
package-authoring
general
pulumiup-booth-support
oracle-cloud-infrastructure
learn-pulumi-events
linen
registry
built-with-pulumi
pulumi-cloud
contribex
testingtesting321
hacktoberfest
pulumi-crosscode
content-share
finops
multi-language-hackathon
office-hours
workshops
gitlab
pulumi-kubernetes-operator
jobs
pulumi-deployments
dotnet
aws
golang
announcements
java
pulumiverse
python
install
getting-started
cloudengineering-support
testingtesting123
hackathon-03-19-2020
typescript
google-cloud
contribute
azure
kubernetes
docs
automation-api
status
Powered by
#kubernetes
Title
m
modern-city-46733
10/30/2021, 3:31 PM
What’s the current best practice for handling
kubectl
commands that just don’t convert to Pulumi yet? (for example Helm Chart deploys with hooks)
s
sparse-park-68967
10/30/2021, 4:00 PM
You could consider helm release:
https://www.pulumi.com/blog/full-access-to-helm-features-through-new-helm-release-resource-for-kubernetes/
It is in preview right now but will be GA this quarter
m
modern-city-46733
10/30/2021, 4:07 PM
Nice, didn’t catch this one - will see if I can get this working - Thanks
@sparse-park-68967
👍 1
4 Views
Post