Hello Pulumi Community! Dropping a line here to announce a blog post about how Pulumi ESC now has better support for Kubernetes tools. Looking forward to seeing how to community takes advantage of ESC to simplify access to Kubernetes clusters. https://www.pulumi.com/blog/esc-kubernetes-cluster-and-app/ Slack Conversation

hey @damp-airline-38442, I’m trying to use this myself but having an issue. when I run

esc env get <envname>

here’s the definition it gives me, which is copied straight from the blog post

stacks:
        fn::open::pulumi-stacks:
          stacks:
            eks-cluster:
              stack: infrastructure/prod
      kubeconfig: {'fn::toJSON': "${stacks.eks-cluster.kubeconfig}"}

but in the output section,

kubeconfig

and

stacks

are both

null

but

kubeconfig

def exists in

infrastructure/prod

, I just quadruple checked by doing

cd infrastructure; pulumi stack select prod; pulumi stack output kubeconfig

and it is indeed there

Hi @gifted-balloon-26385, I'll try to get an answer for you.

@gifted-balloon-26385 try

esc env open

@gifted-balloon-26385 are you using the

esc open

command? It is when you "open" an environment that the values are rendered.

esc env get

only provides a preview of the environment--it doesn't evaluate any of the

fn::open

calls--so the values it produces are incomplete.

ahhh got it. afk for a sec but will give that a try when i’m back

sg!

works! tyvm