pulumi-community #general

rough-parrot-6341

10/04/2020, 8:03 PM

Simply put, attempting to deploy a helm chart with pulumi that fails to create some resources (due to the healthcheck failing, not because the resources aren't actually created) makes Pulumi think the resources don't exist when they do

rough-parrot-6341

10/04/2020, 8:03 PM

and bam you already have configuration drift

rough-parrot-6341

10/04/2020, 8:03 PM

an example trying to deploy a helm chart that refused to deploy properly on the DO kubernetes

rough-parrot-6341

10/04/2020, 8:04 PM

now Pulumi thinks these 3 failed resources don't exist on the cluster while they do, but just have failing healthchecks

rough-parrot-6341

10/04/2020, 8:04 PM

e.g.

rough-parrot-6341

10/04/2020, 8:07 PM

my understanding from the docs was that Pulumi somehow tries to ensure consistency between resources managed by Pulumi and what it has tracked in it's state, but this doesn't seem to be the case? I can see that the failing resource has a

managed-by: pulumi

label, yet Pulumi didn't clean it up when there should be no resources deployed on the cluster anymore by Pulumi

rough-parrot-6341

10/04/2020, 8:08 PM

so I'm wondering what are you supposed to do in this kind of a scenario. Getting to a state of configuration drift (accidentally at that) was surprisingly easy just by using Pulumi, which makes me a bit afraid to use it for production purposes

rough-parrot-6341

10/04/2020, 8:09 PM

understandably Kubernetes is the kind of resource Pulumi can't wish to completely keep track of, but I'd expect it to properly track the resources it itself deploys (and labels even)

rough-parrot-6341

10/04/2020, 8:11 PM

the actual issue (and why I noticed this) is that if I now try to re-deploy the chart, it will fail due to name conflicts (as Pulumi didn't clean up properly after the previous installation was removed)

rough-parrot-6341

10/04/2020, 8:12 PM

on the other hand, had I used helm for this operation, I'm fairly certain it would have cleaned up after itself correctly

rough-parrot-6341

10/04/2020, 8:48 PM

also how are cluster version upgrades supposed to be handled? is there a way to say

use version x for creating the cluster if it doesn't exist yet, otherwise ignore version difference

rough-parrot-6341

10/04/2020, 8:48 PM

I tried using "latest" on the cluster version as I saw in some guide, but that wanted to replace the cluster every time I ran

pulumi up

rough-parrot-6341

10/04/2020, 9:45 PM

is there a way I can test/debug stack outputs without doing deployment steps? so I just want to fetch a value from the existing configuration without changing anything, which doesn't seem to work and I'd like to debug what is it doing

rough-parrot-6341

10/04/2020, 9:45 PM

Copy code

const nginxIngress = new k8s.yaml.ConfigFile("nginx-ingress", {
    file: "./kubernetes/yamls/nginx-ingress-v0.40.1.yaml",
}, { provider });
const nginxLoadBalancer = nginxIngress.getResource("v1/Service", "ingress-nginx-controller");

export const externalIps = nginxLoadBalancer.spec.externalIPs;

rough-parrot-6341

10/04/2020, 9:45 PM

so this is what I have now but

externalIps

is empty and the stack output says

No output values currently in this stack

rough-parrot-6341

10/04/2020, 9:45 PM

I'm guessing the way I try to get the external IP is not correct, but I have no idea how would I start debugging this

rough-parrot-6341

10/04/2020, 10:50 PM

I didn't figure out a better way to test this, but the issue itself was resolved by adding the correct namespace to the

getResource

call and the actual IP was found from

nginxLoadBalancer.status.loadBalancer.ingress

rough-parrot-6341

10/04/2020, 11:18 PM

can I somehow dynamically build a kubernetes resource without defining it in yaml and importing from configfile?

rough-parrot-6341

10/04/2020, 11:18 PM

something not built in

rough-parrot-6341

10/04/2020, 11:19 PM

I want to define a cert-manager ClusterIssuer

rough-parrot-6341

10/04/2020, 11:20 PM

https://www.pulumi.com/docs/reference/pkg/kubernetes/apiextensions/customresource/ ah

rough-parrot-6341

10/04/2020, 11:39 PM

well this is unfortunate

rough-parrot-6341

10/04/2020, 11:39 PM

a helm chart is creating a random certificate on install, which pulumi naturally diffs on every execution and correctly identifies as having changed

rough-parrot-6341

10/04/2020, 11:40 PM

but since the chart is rendered during runtime, I don't really know how should I write the

ignoreChanges

clause for that

rough-parrot-6341

10/04/2020, 11:40 PM

rough-parrot-6341

10/04/2020, 11:41 PM

how would I go about ignoring this change?

rough-parrot-6341

10/04/2020, 11:41 PM

given that I'm just refering a helm chart

rough-parrot-6341

10/04/2020, 11:46 PM

I suppose one option is to generate the dynamically generated parts myself and get a handle on them that way, but that feels like a workaround that shouldn't be required

rough-parrot-6341

10/05/2020, 12:02 AM

I can see they're listed under the chart resource as "children" according to pulumi

rough-parrot-6341

10/05/2020, 12:02 AM