How are you all deploying

istio

within

k8s

using

pulumi

? Especially with the new recommended way of using

istioctl

over

helm

?

Istio

and

helm

don’t work very well together IMO.

I’ve had good luck recently with the operator. https://istio.io/operator.yaml with

k8s.yaml.ConfigGroup

, then just create the

k8s.apiextensions.CustomResource

We see it is https://istio.io/docs/setup/install/standalone-operator/ experimental.

Fair, although I’m not sure

istioctl

or any of the installation methods could be described as much better

I have no experience with production Istio deployments, but I’m generally a bit leery of using yet another standalone tool to manage k8s resources. It looks like you can use

istioctl

to generate manifests [1], so that could be an option for deploying with Pulumi. In other words, run

istioctl manifest generate ...

and then manage the output in Pulumi with a

k8s.yaml.ConfigGroup

. [1] https://istio.io/docs/setup/install/istioctl/#generate-a-manifest-before-installation