This message was deleted Pulumi Community #kubernetes

Join Slack

This message was deleted.

# kubernetes

sparse-intern-71089

02/19/2020, 11:58 PM

This message was deleted.

chilly-photographer-60932

02/20/2020, 12:02 AM

@gorgeous-egg-16927 Do you have any thoughts?

chilly-photographer-60932

02/20/2020, 12:02 AM

cc @incalculable-angle-91273

millions-judge-24978

02/20/2020, 3:47 PM

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

millions-judge-24978

02/20/2020, 3:48 PM

You could even translate the

operator.yaml

into native pulumi, it’s only a few resources.

chilly-photographer-60932

02/20/2020, 5:19 PM

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

chilly-photographer-60932

02/20/2020, 5:20 PM

We are not comfortable with experimental tool for managing our production workloads

millions-judge-24978

02/20/2020, 5:26 PM

Fair, although I’m not sure

istioctl

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

gorgeous-egg-16927

02/20/2020, 5:32 PM

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

gorgeous-egg-16927

02/20/2020, 5:37 PM

I strongly prefer working with the resource definitions directly (either YAML manifests, or native Pulumi code), because it’s much clearer when things change, and how to fix when something breaks.

268 Views

Open in Slack

Previous Next