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
o
orange-autumn-61493
05/15/2021, 8:11 AM
Is this something that Pulumi can internalise? Is Pulumi clever enough to determine which k8s APIs to use based on k8s server version?
s
straight-cartoon-24485
05/16/2021, 6:46 AM
Hm, you can get the stack name programmatically, that might be a start:
https://www.pulumi.com/docs/intro/concepts/stack/#getting-the-current-stack-programmatically
You then have this operator, so if I understand correctly, you might be able to know the k8s version, and alter your deployments accordingly
https://www.pulumi.com/docs/guides/continuous-delivery/pulumi-kubernetes-operator/
I suppose you're going to use a feature-flag-like programming model for all that if'ing between API versions...
o
orange-autumn-61493
05/17/2021, 10:08 AM
Thanks for the heads up, I’ll read thorough these.
5 Views
Post