• h

    hundreds-article-77945

    8 months ago
    We’ve been having issues with empty diffs when using the Go SDK + kubernetes provider (I’ll post a pair of examples in the thread). Has anyone seen this before?
    h
    3 replies
    Copy to Clipboard
  • m

    modern-boots-64313

    8 months ago
    Hi there, 1 of my k8s service is missing after
    pulumi up
    , checked pulumi log file it did shows the resources still in the state. Any idea why ?
    m
    q
    3 replies
    Copy to Clipboard
  • f

    fast-easter-23401

    8 months ago
    Hello there folks, I'm facing this issue while trying to
    pulumi up
    :
    warning: resource plugin kubernetes is expected to have version >=3.13.0, but has 3.13.0-alpha.1640142079+cb2803c5.dirty; the wrong version may be on your path, or this may be a bug in the plugin
    How can I determine whether the root problem is a misconfigured value in my environment or a problem in the underlying plugin?
    f
    1 replies
    Copy to Clipboard
  • b

    bumpy-summer-9075

    8 months ago
    I deployed a helm chart using pulumi and on every
    up
    , pulumi recreates a secret for a reason that escapes me:
    --kubernetes:core/v1:secret: (delete-replaced)
                    [id=sonarqube/sonarqube-postgresql]
                    [urn=urn:pulumi:dev::infra-do-cluster::company:kubernetes:Sonarqube$kubernetes:<http://helm.sh/v3:Chart$kubernetes:core/v1:secret::sonarqube/sonarqube-postgresql|helm.sh/v3:Chart$kubernetes:core/v1:secret::sonarqube/sonarqube-postgresql>]
                    [provider=urn:pulumi:dev::infra-do-cluster::pulumi:providers:kubernetes::doks::01acb2ec-8062-4904-9f58-b2144e4043f3]
                +-kubernetes:core/v1:secret: (replace)
                    [id=sonarqube/sonarqube-postgresql]
                    [urn=urn:pulumi:dev::infra-do-cluster::company:kubernetes:Sonarqube$kubernetes:<http://helm.sh/v3:Chart$kubernetes:core/v1:secret::sonarqube/sonarqube-postgresql|helm.sh/v3:Chart$kubernetes:core/v1:secret::sonarqube/sonarqube-postgresql>]
                    [provider=urn:pulumi:dev::infra-do-cluster::pulumi:providers:kubernetes::doks::01acb2ec-8062-4904-9f58-b2144e4043f3]
                  ~ data: {
                    }
                ++kubernetes:core/v1:secret: (create-replacement)
                    [id=sonarqube/sonarqube-postgresql]
                    [urn=urn:pulumi:dev::infra-do-cluster::company:kubernetes:Sonarqube$kubernetes:<http://helm.sh/v3:Chart$kubernetes:core/v1:secret::sonarqube/sonarqube-postgresql|helm.sh/v3:Chart$kubernetes:core/v1:secret::sonarqube/sonarqube-postgresql>]
                    [provider=urn:pulumi:dev::infra-do-cluster::pulumi:providers:kubernetes::doks::01acb2ec-8062-4904-9f58-b2144e4043f3]
                  ~ data: {
                    }
    Anyone know why this occurs? It doesn't break anything but is an annoyance 😕
    b
    b
    3 replies
    Copy to Clipboard
  • b

    busy-island-31180

    8 months ago
    I’m trying to use the Kubernetes provider for Pulumi to deploy several resources, and I’m using patterns like
    myService.metadata.name
    in order to pass information around. I’ve found that this ends up creating dependencies, and in some cases, deadlock situations. In this example, a service will not become “healthy” until there are pods registered to it. Yet, when I’m using something like ArgoRollouts, there’s a pointer back to my service name:
    strategy:
    
        # Blue-green update strategy
        blueGreen:
    
          # Reference to service that the rollout modifies as the active service.
          # Required.
          activeService: active-service
    So, because of this, the pulumi wants to deploy the service first, and rollout second. But the service never becomes healthy, as it’s waiting on the rollout. The workaround is to define a variable and pass the value of that to all places that need the service name. I was also thinking of a way to tell Pulumi to not block other resources from being created while this one becomes healthy? The data is available regardless of health state. For k8s resources, I feel like, a lot of the data is static, and yet it’s treated as dynamic, thus I can’t easily make these references. (I coming from Jsonnet, which makes this quite easy). Has anyone else run into these types of problems? Do you have any patterns or practices that makes the code feel “refactor proof”? What about the case when you don’t know the service name? (maybe it’s being returned as part of higher-level function)
    b
    b
    21 replies
    Copy to Clipboard
  • m

    microscopic-library-98015

    8 months ago
    Has anyone experience a segfault like this?
    FirmNav/firmnav/staging (pulumi:pulumi:Stack)
    panic: runtime error: invalid memory address or nil pointer dereference
     
    [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1ec736c]
     
    goroutine 61 [running]:
     
    <http://k8s.io/apimachinery/pkg/apis/meta/v1/unstructured.(*Unstructured).GetNamespace(...)|k8s.io/apimachinery/pkg/apis/meta/v1/unstructured.(*Unstructured).GetNamespace(...)>
     
    	/home/runner/go/pkg/mod/k8s.io/apimachinery@v0.22.1/pkg/apis/meta/v1/unstructured/unstructured.go:234
     
    <http://github.com/pulumi/pulumi-kubernetes/provider/v3/pkg/await.(*deploymentInitAwaiter).Await(0xc0037b7078|github.com/pulumi/pulumi-kubernetes/provider/v3/pkg/await.(*deploymentInitAwaiter).Await(0xc0037b7078>, 0x0, 0x0)
     
    	/home/runner/work/pulumi-kubernetes/pulumi-kubernetes/provider/pkg/await/deployment.go:153 +0xec
     
    <http://github.com/pulumi/pulumi-kubernetes/provider/v3/pkg/await.glob..func2(0xc0003025e8|github.com/pulumi/pulumi-kubernetes/provider/v3/pkg/await.glob..func2(0xc0003025e8>, 0x2897aa0, 0xc0005b41c0, 0xc000e9ea80, 0x7a, 0xc00379b050, 0x7, 0xc0035e1100, 0xc000726960, 0xc001967d58, ...)
     
    	/home/runner/work/pulumi-kubernetes/pulumi-kubernetes/provider/pkg/await/awaiters.go:147 +0x125
     
    <http://github.com/pulumi/pulumi-kubernetes/provider/v3/pkg/await.Update(0x2897aa0|github.com/pulumi/pulumi-kubernetes/provider/v3/pkg/await.Update(0x2897aa0>, 0xc0005b41c0, 0xc0003025e8, 0xc000e9ea80, 0x7a, 0xc00379b050, 0x7, 0x0, 0x0, 0xc000726960, ...)
     
    	/home/runner/work/pulumi-kubernetes/pulumi-kubernetes/provider/pkg/await/await.go:430 +0xb35
     
    <http://github.com/pulumi/pulumi-kubernetes/provider/v3/pkg/provider.(*kubeProvider).Update(0xc0002e0f00|github.com/pulumi/pulumi-kubernetes/provider/v3/pkg/provider.(*kubeProvider).Update(0xc0002e0f00>, 0x2897b48, 0xc0037d6060, 0xc00376b700, 0xc0002e0f00, 0x21cf001, 0xc0037d13c0)
     
    	/home/runner/work/pulumi-kubernetes/pulumi-kubernetes/provider/pkg/provider/provider.go:2166 +0xfc5
     
    <http://github.com/pulumi/pulumi/sdk/v3/proto/go._ResourceProvider_Update_Handler.func1(0x2897b48|github.com/pulumi/pulumi/sdk/v3/proto/go._ResourceProvider_Update_Handler.func1(0x2897b48>, 0xc0037d6060, 0x23ef780, 0xc00376b700, 0x23db960, 0x3ab62a8, 0x2897b48, 0xc0037d6060)
     
    	/home/runner/go/pkg/mod/github.com/pulumi/pulumi/sdk/v3@v3.19.0/proto/go/provider.pb.go:2638 +0x8b
     
    <http://github.com/grpc-ecosystem/grpc-opentracing/go/otgrpc.OpenTracingServerInterceptor.func1(0x2897b48|github.com/grpc-ecosystem/grpc-opentracing/go/otgrpc.OpenTracingServerInterceptor.func1(0x2897b48>, 0xc003799380, 0x23ef780, 0xc00376b700, 0xc0037a0540, 0xc0037894e8, 0x0, 0x0, 0x284d6a0, 0xc0003a8e70)
     
    	/home/runner/go/pkg/mod/github.com/grpc-ecosystem/grpc-opentracing@v0.0.0-20180507213350-8e809c8a8645/go/otgrpc/server.go:57 +0x30a
     
    <http://github.com/pulumi/pulumi/sdk/v3/proto/go._ResourceProvider_Update_Handler(0x247e9a0|github.com/pulumi/pulumi/sdk/v3/proto/go._ResourceProvider_Update_Handler(0x247e9a0>, 0xc0002e0f00, 0x2897b48, 0xc003799380, 0xc00378b740, 0xc000704a00, 0x2897b48, 0xc003799380, 0xc0037a4000, 0x2d84)
     
    	/home/runner/go/pkg/mod/github.com/pulumi/pulumi/sdk/v3@v3.19.0/proto/go/provider.pb.go:2640 +0x150
     
    <http://google.golang.org/grpc.(*Server).processUnaryRPC(0xc000421880|google.golang.org/grpc.(*Server).processUnaryRPC(0xc000421880>, 0x28b48f8, 0xc0002e1500, 0xc00379d200, 0xc0007e3b60, 0x3a52770, 0x0, 0x0, 0x0)
     
    	/home/runner/go/pkg/mod/google.golang.org/grpc@v1.38.0/server.go:1286 +0x52b
     
    <http://google.golang.org/grpc.(*Server).handleStream(0xc000421880|google.golang.org/grpc.(*Server).handleStream(0xc000421880>, 0x28b48f8, 0xc0002e1500, 0xc00379d200, 0x0)
     
    	/home/runner/go/pkg/mod/google.golang.org/grpc@v1.38.0/server.go:1609 +0xd0c
     
    <http://google.golang.org/grpc.(*Server).serveStreams.func1.2(0xc000777b70|google.golang.org/grpc.(*Server).serveStreams.func1.2(0xc000777b70>, 0xc000421880, 0x28b48f8, 0xc0002e1500, 0xc00379d200)
     
    	/home/runner/go/pkg/mod/google.golang.org/grpc@v1.38.0/server.go:934 +0xab
     
    created by <http://google.golang.org/grpc.(*Server).serveStreams.func1|google.golang.org/grpc.(*Server).serveStreams.func1>
     
    	/home/runner/go/pkg/mod/google.golang.org/grpc@v1.38.0/server.go:932 +0x1fd
     
    error: update failed
     
    app-staging-deployment (firmnav:app:App$kubernetes:apps/v1:Deployment)
    error: transport is closing
    It’s consistently failing in CI, though it did work once out of like 10 tries.. I can’t see what should’ve changed on our end to suddenly cause it. For info we’re using the GCP and kubernetes providers
    m
    1 replies
    Copy to Clipboard