on deploying a recent change to AWS Load Balancer Controller via helm, pulumi seems to be having issues with naming on one of the sub-resources

IngressClassParams

.... the first time i run pulumi the pulumi logical-name of this resource is

kube-system/alb-ingress-class-params

but any subsequent run tries to replace it with another instance with the name

alb-ingress-class-params

(ie without the namespace prefix as part of the logical name). ... thoughts ??? ..... more details in thread

Hi! I have k8s deployed on DigitalOcean via Pulumi, and I also deploy my Helm releases onto said cluster using Pulumi. If I try to update an existing Helm release, or create a new one, I get the following when I run `Pulumi up`:

error: can't create Helm Release with unreachable cluster: unable to load schema information from the API server: the server has asked for the client to provide credentials

I have my digital ocean access token set up, and I initially created the Helm release with Pulumi, so I'm not clear as to why it suddenly isn't working. Any guidance or help would be massively appreciated!

Hi all, Has anyone managed to use eks entirely from credentials stored in the stack config? I’ve got it working on up by actually retrieving the token and shoving it in a kubeconfig but destroy doesn’t appear to re-retrieve the token, just relies on the one stored in the state.

Hi all, At the moment I have a cronjob that makes a snapshot every x minutes of a given pvc in a namespace. It does this by using a new image using the Pulumi cli image as a base image and adds a small Pulumi project that makes a new snapshot and deletes the previous one every-time it runs. Now this is all working fine, but there is one small issue. I need the value

Snapshot Handle

from the volumesnapshotcontent resource that is generated automatically when making a new snapshot. Because it's generated automatically it is not a pulumi resource, so as far as I know I can't get that value using pulumi. I wanted to use pulumi for it so I can save it as a stackreference and use it in different places in my infrastructure. I tried using query-kubernetes, because I can get the name of this volumesnapshotcontent from the volumesnapshot itself, but this package does not support crd's. Anyone an idea on how I could achieve this? (I thought of using a kubectl container to get it, but I would prefer to keep it all pulumi)

Hi everybody, Question: What’s the best way to rename a helm release without downtime? Context: I made a mistake naming a

helm release

and wanted to renamed it. Ideally, I wish to prevent pulumi/helm from creating a replacement, so I tried to do so by using the

aliases

flag on the

ComponentResourceOptions

. However, after aliasing and changing both the name of the pulumi resource and the

helm.Release

component

name

field, I noted that no changes are being applied.

Hi there! 👋 Has anyone found way to install Flux v2 with Pulumi?

I broke out my various components in Go into seperate packages. I now am trying to eliminate any of the functions that are overriding the names. I thought i was using the autonaming, but deployment for example took my name and didn't append anything extra. So now, I want to know 2 main things (posting as seperate blocks so reply in threads will work for each...

1️⃣ Not Overriding the Autonaming, but still keeping it easy to share _edit_: removed main content and placed in How do you approach passing around ID's for resources without it becoming a hot mess? #9205 This is more involved so better to capture any ideas there for others. Welcome any insight/thoughts.

2️⃣ multicluster deployment Just modified my plan to do:

---
clusters:
  - name: cluster1
    kubeconfig:
        secure: .....
  - name: cluster2
    kubeconfig:
        secure: .....

Now I just added in main a new config object and wrapped the entire deployment setup I had in a for each. Boom. Loop over clusters and go. Due to pulumi's routinues and all the magic going on I figured I'd do a dumb old loop instead of trying concurrent deployments, but looking for a sanity check.

pulumi.Run(func(ctx *pulumi.Context) error {
  for _, cluster := range clusterList {
	cfgMap, err := configmap.ConfigMap(
				ctx,
				renderProvider,
				&configData,
				&appConfig,
				&sharedConfig,
			)
     err = ingress.NetworkingIngress(ctx, renderProvider, &configData, &sharedConfig)
     err = service.Service(ctx, renderProvider, &configData, &sharedConfig)
     //     etc....
	_ = <http://ctx.Log.Info|ctx.Log.Info>(fmt.Sprintf("finished processing cluster: %s", cluster.Name), &pulumi.LogArgs{})
    }
})

Make sense to do the same deployment this way on 2 clusters without concurrency or any other way you'd say is better? Multiple pulumi.Run or anything else you'd recommend? I love my experience overall, but it's a lot more complex initially than plain yaml, so I'm double check my approach here makes sense and is reasonable. Much appreciated!

kubernetes.networking.v1.Ingress

appears to expect a LB address to populate in status before accepting the resource as being healthy? I'm not seeing an opt-out for this which is causing difficulty behind noteport / hostport type ingress controllers. Am I missing something, or should I be trying to accomplish this another way?

Hello Community! I am trying to use the imported

kubeconfig

from another project to create a new provider on the new projct based on that file using the

ApplyT

golang method to convert the

AnyOutput

data type to a

pulumi.ProviderResource

type. Can someone explain to me how can I do it? A snippet of golang code is below.

// Create stack reference to prvious projct named  "ccmx/eks/dev"
stack_output, err := pulumi.NewStackReference(ctx, "ccmx/eks/dev", nil)
		if err != nil {
			log.Fatalf("error creating stack reference: %v", err)
		}
// Import kubeconfig from the stack "ccmx/eks/dev"
kubeconfig := stack_output.GetOutput(pulumi.String("kubeconfig"))

// Create Kuberntes provider
K8sProvider, err := kubernetes.NewProvider(ctx, "eks-provider", &kubernetes.ProviderArgs{
			//Kubeconfig: pulumi.String(kubeconfig),
			Kubeconfig: kubeconfig.ApplyT(func(s string) string { return s }).(pulumi.Provider),
		})

		if err != nil {
			log.Fatalf("error creating K8s provider: %v", err)
		}

Is there any good information or insight someone can give on the difference between helm/v3 charts vs releases? They seem to do the same thing?

Is it possible to tell pulumi about dependencies within resources in yaml files using NewConfigGroup? For example, the code below adds three yaml files of resources. The last file

eck_filebeats.yaml

has a resource named

filebeat

that should not be created until a specific service created by the

eck_operator.yaml

file has an endpoint.

Also, how can I tell pulumi to expect that the

eck_operator.yaml

file will deploy an operator pod that will, in turn, deploy a service outside of Pulumi, and that this service should be imported into Pulumi so it can be dependedOn by other Pulumi-managed resources downstream?

Hi everyone! How do you provision node-groups in EKS? I’ve tried to do same as noted in EKS Crosswalk, but have infinity preview state until I’ll remove NodeGroup opts (with provider settings). But then I’ll have problem with broken assume_role_policy as showed on screen (again, I’m still using example from link above). Then I’ll use my one custom assume_role_policy (see second screen), but after it provides EKS I’m getting error with Stack (third screen) I’m really need custom node-groups… How can I do that? Thanks! :)

Does pulumi have an approach to handle the k8s operator pattern? When operators are used for an app, they create resources outside of pulumi. How does pulumi deal with this? Is there a operator "monitor" mode where pulumi can pick up these dependencies dynamically from the operator's interaction with the k8s API?

Hi all, I had to add a resourcePrefix to my helm chart but it doesn’t install because a bunch of the resources within the helm chart already exist. Is there any way to do some kind of resourcePrefix alias?

Hello folks, We’re using secrets to store some sensitive data (namely serviceAccounts keys). I was wondering what would happen to pods (or workloads more generally) using those secrets when we rotate our serviceAccount keys. Pulumi would then try to recreate a new secret with new values. Will these be propagated to the workloads using them? Many thanks,

has anyone seen spurious

urn

name conflicts when creating a brand new resource…where there DEFINITELY isn’t an existing resource with that name?

is there a way to deploy to k8s and generate the yaml to a directory at the same time? currently you need to create a separate k8s provider and set the renderYamlToDirectory property as setting this property causes the other attributes like kubeconfig to be ignored. i could create two k8s objects with different providers, since you can only pass one provider, but it would be nice if you could pass multiple providers to k8s objects.

Hey guys, I’m trying to create a Helm Release on an already exist cluster (managed by Pulumi). For some reason i’m getting this error on my

pulumi up

action on Github Actions:

+  kubernetes:<http://helm.sh/v3:Release|helm.sh/v3:Release> eks-bootstrap creating error: can't create Helm Release with unreachable cluster: unable to load Kubernetes client configuration from kubeconfig file: invalid configuration: no configuration has been provided, try setting KUBERNETES_MASTER environment variable

Here is the code i’m creating my Helm Release (occurs after the eks k8s cluster creation)

export function createHelmBootstrapChart(stackName: string) {

    const releaseArgs: k8s.helm.v3.ReleaseArgs = {
        atomic: true,
        name: "eks-bootstrap",
        chart: "./charts/eks-bootstrap-chart",
        dependencyUpdate: true,
        namespace: "kube-system",
        valueYamlFiles: [new FileAsset(`./charts/eks-bootstrap-chart/values-${stackName}.yaml`)]
        
    }
    new k8s.helm.v3.Release("eks-bootstrap", releaseArgs)

}

Do you guys know how to set the Kubeconfig ? because it looks like the kubeconfig is missing during runtime on the github action.

Does anyone know how to handle updates in Helm Chart/Release ? I created a release using Pulumi but it never updates when i’m changing the chart or the pulumi code. For example, I changed the release namespace, it updates the Pulumi state but doesn’t create the release in the new namespace (neither delete the old release). Any hints with that ?

So, I've got about 160 helm releases in a stack connecting to an EKS cluster on aws. Trying to run it locally is now actually timing out telling me my upgrade token has expired. I suspect trying to build the state for my helm releases is being throttled by aws. Any advice, should I split my stack into substacks so that I don't have to poll quite as many for each op?

Yes

So I have a general k8s question, I have a Saas product that we are looking at modernizing in a lot of areas. It is a CRM for nonprofits that has 500-1k unique customers. We have them in a monolith app now with 1 shared database. We are looking at increasing isolation, improving scaling, noisy neighbor issues, etc. I have been told by a few that it would make sense to have a structure where each of our customer’s have their own name space to get better isolation. But I am curious if this is the best pattern? Is this what most people are doing now for multi-tenant apps?

I could use some help solving how to write kustomize transformations to remove a namespace object from being generated by @pulumi/kubernetes's kubernetes.kustomize.Directory where the namespace object is coming in from an upstream that is out of my control. Problem of kustomize generating the namespace object results in:

Updating (keycloak):
     Type                                                  Name                   Status                  Info
     pulumi:pulumi:Stack                                   tkl-keycloak-keycloak  **failed**              1 error
     └─ kubernetes:kustomize:Directory                     keycloak                                       
 +      ├─ kubernetes:core/v1:Namespace                    keycloak               **creating failed**     1 error

Got a weird error when trying to used my crd generated with crd2pulumi. Anyone has already that kind of a problem?

TypeError: Invalid Version:
        at new SemVer (/builds/${PROJECT}/pulumi/node_modules/semver/semver.js:332:11)
        at compare (/builds/${PROJECT}/pulumi/node_modules/semver/semver.js:647:10)
        at Function.eq (/builds/${PROJECT}/pulumi/node_modules/semver/semver.js:693:10)
        at sameVersion (/builds/${PROJECT}/pulumi/node_modules/@pulumi/runtime/rpc.ts:703:57)
        at register (/builds/${PROJECT}/pulumi/node_modules/@pulumi/runtime/rpc.ts:718:17)
        at Object.registerResourcePackage (/builds/${PROJECT}/pulumi/node_modules/@pulumi/runtime/rpc.ts:780:5)
        at Object.<anonymous> (/builds/${PROJECT}/pulumi/node_modules/@ticketmaster/pipelog-crds/build/index.js:25:16)
        at Module._compile (node:internal/modules/cjs/loader:1103:14)
        at Object.Module._extensions..js (node:internal/modules/cjs/loader:1155:10)
        at Module.load (node:internal/modules/cjs/loader:981:32)

I'm trying to use Command and run something on the create. There is already an EKS cluster and I have it's kubeconfig From the example on https://www.pulumi.com/registry/packages/command/#graceful-cleanup-of-workloads-in-a-kubernetes-cluster I'm getting an error

environment[KUBECONFIG] value: An error occurred decoding 'command.environment[KUBECONFIG] value': Cannot decode Object{} to type string; it isn't a struct, and no custom decoder exists

Is there some better way to provide kubeconfig to the command and I would like to avoid having it on filesystem.

Hello everyone, happy Monday! Maybe a silly question but how do you get the dynamic resource names created by

new k8s.helm.v3.Release(…)…

for

XYZ

Helm chart… if you don’t specify the

name

and leave Pulumi to autogenerate it, or even specify the

name

whichever… and use the resource names later on it the program without inferring the name based on the prefix and whatever the chart is?