pulumi-community #pulumi-kubernetes-operator

Join the conversation Join Slack

pulumi-kubernetes-operator

white-balloon-205

11/20/2020, 9:43 PM

set the channel description: https://github.com/pulumi/pulumi-kubernetes-operator

sparse-park-68967

12/02/2020, 8:47 PM

👋

👋 2

white-balloon-205

12/03/2020, 6:54 PM

🚀 We just released

pulumi/pulumi-kubernetes-operator@v0.0.8

which includes the fixes for: • https://github.com/pulumi/pulumi-kubernetes-operator/issues/96 • https://github.com/pulumi/pulumi-kubernetes-operator/issues/98 • https://github.com/pulumi/pulumi-kubernetes-operator/issues/102 • https://github.com/pulumi/pulumi-kubernetes-operator/issues/83 • https://github.com/pulumi/pulumi-kubernetes-operator/issues/87 • https://github.com/pulumi/pulumi-kubernetes-operator/issues/104

dry-engine-17210

01/25/2021, 9:08 PM

...and wrong channel, sorry.

alert-mechanic-59024

08/11/2021, 6:13 PM

Heya all. I have a few questions regarding the Pulumi K8s Operator (PKO), which I’d really appreciate some feedback on. In no particular order: Does the PKO support checking out the head of branches, rather than specific commits - i.e. follow master (and what is the default branch it uses - it is complaining about not being able to find my master branch); Does PKO support local state management, rather than operating against the Pulumi API? (If so, how does one pass this requirement to the stack CR); I’m getting “Failed to setup Pulumi workdir”,“Request.Namespace”:“default”,“Request.Name”:“bow-poc”,“Stack.Name”:“bow-poc”,“error”:“failed to create local workspace: failed to create workspace, unable to enlist in git repo: unable to checkout branch: object not found”" when attempting to pull down a remote repo. Could someone point me in the right direction, please?

bored-vegetable-38523

09/13/2021, 5:25 PM

Hi Everyone. Cross posting from #general as this is the operator channel 🙂 https://pulumi-community.slack.com/archives/C84L4E3N1/p1631538788316700

prehistoric-kite-30979

09/15/2021, 1:26 PM

AFAICT you cant configure the operator to explicitly use yarn over npm. Will the operator autodetect yarn?

prehistoric-kite-30979

09/20/2021, 7:33 PM

How would I go about getting private github repos working with npm/yarn install?

"Stdout":"fatal: could not read Username for '<https://github.com>': No such device or address"

breezy-bear-50708

09/24/2021, 1:55 PM

Is it possible to get a new release? Would really like to get https://github.com/pulumi/pulumi-kubernetes-operator/pull/195 to fix the eviction issue 🙂

prehistoric-kite-30979

09/27/2021, 7:56 PM

Do I have to configure the secrets provider in the CRD if it already exists? I’m getting complaints about setting passphrase env var.

prehistoric-kite-30979

09/29/2021, 3:17 PM

It appears that this line of code doesn’t work as expected https://github.com/pulumi/pulumi-kubernetes-operator/blob/master/pkg/controller/stack/stack_controller.go#L874 If I run a pulumi stack output I can see my secrets are redacted, but they are still in the clear in the stack status.

ambitious-salesmen-39356

10/15/2021, 7:57 PM

How have experiences been so far with the operator? We are looking at adoption. Any big gotchas/caveats/things that didn't work quite the way you expected?

crooked-pillow-11944

10/15/2021, 10:43 PM

Before I start going down this road I'll ask: Does anybody have any Python examples for Blue/Green deployments using the Kubernetes operator? I know it would be a bit more code without

kubernetesx

but it's worth it to me to see this thru and validate if/that this will work for me

busy-house-95123

10/28/2021, 12:13 PM

hey everyone, is it possible to refer to a subpath in a git repo when using the Pulumi Stack CustomResource?

calm-agent-50232

01/18/2022, 6:29 AM

how do you get a Stack to use a non-main branch? i get this error using any non-main branch name or ref path

error":"failed to create local workspace: failed to create workspace, unable to enlist in git repo: unable to checkout branch: reference not found"

here’s the config:

spec:
  projectRepo: <https://gitlab.com/mycompany/sre/pko-poc.git>
  stack: mycompany/infra-apps/poc
  branch: "refs/heads/main"  #this works for some reason but /refs/heads/poc results in reference not found
  #branch: "poc"             #this also results in reference not found
  repoDir: infra-apps
    envRefs:
    PULUMI_ACCESS_TOKEN:
      type: Secret
      secret:
        name: pulumi-api-secret
        key: accessToken
  gitAuth:
    accessToken:
      type: Secret
      secret:
        name: git-secret
        key: privateToken

this is a private gitlab repo but i have confirmed auth is successful and if i point it at

/refs/heads/main

then it does update the pulumi project thanks

brainy-window-77332

01/20/2022, 2:16 PM

Does the operator support drift detection?

stocky-motorcycle-65008

02/07/2022, 2:07 PM

Hello there, can I use the the Stack CRD without PULUMI_ACCESS_TOKEN ?

stocky-motorcycle-65008

02/07/2022, 3:36 PM

Ok, I'm hooked! |'ve tested it with a simple guestbook app on a local kind cluster. https://github.com/tcrst/pulumi-k8s-operator-stacks very powerful Thinking on a solution to automate the images inside my k8s stack, any idea? :-?

early-notebook-60164

04/20/2022, 5:25 AM

I’m experimenting with the operator for a project at work. I can see that there is a way to set stack secrets via Kubernetes Secret. Is there a way to set stack config via ConfigMaps? From the docs, it looks like this can only be provided inline.

bored-processor-13571

04/21/2022, 8:18 PM

Hi everyone, i am trying to get the operator to work with a private git host using private key auth. There seems to be issues with knownhosts:

failed to create local workspace: failed to create workspace, unable to enlist in git repo: unable to clone repo: ssh: handshake failed: knownhosts: key is unknown"

I've even went into the operator container and tried

ssh-keyscan -p 4567 -H <http://git.host.com|git.host.com> >> ~/.ssh/known_hosts

but it doesn't do anything has anybody experienced something similar?

damp-honey-93158

04/25/2022, 4:00 PM

Hey operators 🙂 I'm wondering if someone can help me clarify what the big advantage of using the operator is over a more traditional ci/cd approach where pulumi up is run as part of a pipeline? Is it drift detection/repair or configuration or something else that I'm totally missing? Thanks in advance!

broad-parrot-78298

04/26/2022, 3:18 PM

Hey. I'm wondering if there is a preferred pattern for doing StackReferences (or something similar) when using the Kubernetes Operator. For example, I have one stack that creates an IAM Role and then I have other stacks that want to consume that role's name for performing policy attachment. I imagine I can write the role name out to a secret on the cluster or I can construct the fully qualified name for the stack with the role but I can't help but feel there is a nicer way to do it. I couldn't find anything in the operator docs.

narrow-translator-93508

06/09/2022, 4:38 PM

Hello guys, I have an issue with the

operator

, especially this error message

No permalink found

, I'm using a GCS backend FYI

narrow-translator-93508

06/09/2022, 4:39 PM

{
    "level": "error",
    "ts": "2022-06-09T16:33:51.377Z",
    "logger": "controller_stack",
    "msg": "No permalink found.",
    "Request.Namespace": "default",
    "Request.Name": "hello-stack-6c5ede73",
    "Namespace": "default",
    "error": "failed to get permalink",
    "errorVerbose": "failed to get permalink\<http://ngithub.com/pulumi/pulumi/sdk/v3/go/auto.init\n\t/home/runner/go/pkg/mod/github.com/pulumi/pulumi/sdk/v3@v3.30.0/go/auto/stack.go:694\nruntime.doInit\n\t/opt/hostedtoolcache/go/1.17.8/x64/src/runtime/proc.go:6498\nruntime.doInit\n\t/opt/hostedtoolcache/go/1.17.8/x64/src/runtime/proc.go:6475\nruntime.doInit\n\t/opt/hostedtoolcache/go/1.17.8/x64/src/runtime/proc.go:6475\nruntime.doInit\n\t/opt/hostedtoolcache/go/1.17.8/x64/src/runtime/proc.go:6475\nruntime.doInit\n\t/opt/hostedtoolcache/go/1.17.8/x64/src/runtime/proc.go:6475\nruntime.main\n\t/opt/hostedtoolcache/go/1.17.8/x64/src/runtime/proc.go:238\nruntime.goexit\n\t/opt/hostedtoolcache/go/1.17.8/x64/src/runtime/asm_amd64.s:1581|ngithub.com/pulumi/pulumi/sdk/v3/go/auto.init\n\t/home/runner/go/pkg/mod/github.com/pulumi/pulumi/sdk/v3@v3.30.0/go/auto/stack.go:694\nruntime.doInit\n\t/opt/hostedtoolcache/go/1.17.8/x64/src/runtime/proc.go:6498\nruntime.doInit\n\t/opt/hostedtoolcache/go/1.17.8/x64/src/runtime/proc.go:6475\nruntime.doInit\n\t/opt/hostedtoolcache/go/1.17.8/x64/src/runtime/proc.go:6475\nruntime.doInit\n\t/opt/hostedtoolcache/go/1.17.8/x64/src/runtime/proc.go:6475\nruntime.doInit\n\t/opt/hostedtoolcache/go/1.17.8/x64/src/runtime/proc.go:6475\nruntime.main\n\t/opt/hostedtoolcache/go/1.17.8/x64/src/runtime/proc.go:238\nruntime.goexit\n\t/opt/hostedtoolcache/go/1.17.8/x64/src/runtime/asm_amd64.s:1581>",
    "stacktrace": "<http://github.com/pulumi/pulumi-kubernetes-operator/pkg/controller/stack.(*ReconcileStack).Reconcile\n\t/home/runner/work/pulumi-kubernetes-operator/pulumi-kubernetes-operator/pkg/controller/stack/stack_controller.go:319\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.9.0/pkg/internal/controller/controller.go:298\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.9.0/pkg/internal/controller/controller.go:253\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.9.0/pkg/internal/controller/controller.go:214|github.com/pulumi/pulumi-kubernetes-operator/pkg/controller/stack.(*ReconcileStack).Reconcile\n\t/home/runner/work/pulumi-kubernetes-operator/pulumi-kubernetes-operator/pkg/controller/stack/stack_controller.go:319\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.9.0/pkg/internal/controller/controller.go:298\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.9.0/pkg/internal/controller/controller.go:253\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.9.0/pkg/internal/controller/controller.go:214>"
}

narrow-translator-93508

06/13/2022, 7:24 AM

message has been deleted

👍 2

strong-ability-43344

07/22/2022, 11:06 AM

Hello, did you experience this error with microk8s?

sparse-intern-71089

07/29/2022, 4:06 PM

This message was deleted.

future-exabyte-15821

08/01/2022, 12:58 PM

Hi, I have the following in the Pulumi.yaml

stackConfigDir: stacks/

When the operator is running I see the following message: `Missing stack config file. Will assume no stack config checked-in.`Ok.. thats weird, its surely in Git.. After that message its creating a file

Pulumi.foo.yml

in the root of the project with the content

{}

Thats an extra weird because

useLocalStackOnly: true

is set. But when its doing the

up

it is using the values in the

stacks/Pulumi.foo.yaml

stack: "foo"

is configured for the `Stack`resource. Im confused 😄

prehistoric-translator-89978

09/01/2022, 10:46 PM

Hello, is the pulumi operator still the way to go or should I be using something else, since I noticed that there hasn't been a new release since 10th of June

sparse-park-68967

09/07/2022, 8:58 PM

Hi Magnus, there was a release on Sept. 1st: https://github.com/pulumi/pulumi-kubernetes-operator/releases/tag/v1.8.0. We are working on some significant improvements in the coming weeks so it is still very much in active development

🎉 1