Hello everyone,
I am trying out the Kuberentes ope...
# generalr
rich-application-35618
10/11/2024, 10:57 AMHello everyone,
I am trying out the Kuberentes operator, and I have some problems I can't solve.
1. Does the operator only apply stacks that exist? Or can I use it to create a new stack with the configuration provided in the Stack CRD?
2. I have run into a situation where the pod starts, installs dependencies, and then exits without logging anything useful. (logs in thread). Is there a way to increase the logging level of the pods so I can tell what it's doing?
rich-application-35618
10/11/2024, 10:58 AM Copy code
Defaulted container "pulumi" out of: pulumi, bootstrap (init), fetch (init)
2024-10-11T11:00:34.952Z INFO cmd.serve Pulumi Kubernetes Agent {"version": "v2.0-beta.0"}
2024-10-11T11:00:35.600Z INFO cmd.serve opened a local workspace {"workspace": "/share/source/pulumi/fastly/service", "project": "service", "runtime": "nodejs"}
2024-10-11T11:00:35.600Z INFO cmd.serve installation skipped {"project": "service", "runtime": "nodejs"}
2024-10-11T11:00:35.601Z INFO server project serving {"project": "service", "runtime": "nodejs"}
2024-10-11T11:00:35.601Z INFO cmd.serve starting the RPC server {"address": "0.0.0.0:50051"}
2024-10-11T11:00:35.601Z INFO cmd.serve.grpc [core][Server #1]Server created {"system": "grpc", "grpc_log": true}
2024-10-11T11:00:35.601Z INFO cmd.serve server listening {"address": "[::]:50051", "workspace": "/share/source/pulumi/fastly/service"}
2024-10-11T11:00:35.601Z INFO cmd.serve.grpc [core][Server #1 ListenSocket #2]ListenSocket created {"system": "grpc", "grpc_log": true}
2024-10-11T11:00:35.921Z INFO server installing the project dependencies
2024-10-11T11:00:36.025Z INFO pulumi Installing dependencies...
2024-10-11T11:00:36.025Z INFO pulumi
2024-10-11T11:00:43.755Z INFO pulumi
2024-10-11T11:00:43.755Z INFO pulumi added 427 packages, and audited 428 packages in 8s
2024-10-11T11:00:43.755Z INFO pulumi
2024-10-11T11:00:43.755Z INFO pulumi 60 packages are looking for funding
2024-10-11T11:00:43.755Z INFO pulumi run `npm fund` for details
2024-10-11T11:00:43.755Z INFO pulumi
2024-10-11T11:00:43.755Z INFO pulumi found 0 vulnerabilities
2024-10-11T11:00:43.755Z WARN pulumi npm notice
2024-10-11T11:00:43.755Z WARN pulumi npm notice New minor version of npm available! 10.5.1 -> 10.9.0
2024-10-11T11:00:43.755Z WARN pulumi npm notice Changelog: <<https://github.com/npm/cli/releases/tag/v10.9.0>>
2024-10-11T11:00:43.755Z WARN pulumi npm notice Run `npm install -g npm@10.9.0` to update!
2024-10-11T11:00:43.755Z WARN pulumi npm notice
2024-10-11T11:00:43.764Z INFO pulumi Finished installing dependencies
2024-10-11T11:00:43.764Z INFO pulumi
2024-10-11T11:00:46.219Z WARN pulumi [resource plugin docker-4.5.5] installing
2024-10-11T11:00:53.905Z WARN pulumi [resource plugin aws-6.52.0] installing
2024-10-11T11:00:56.850Z INFO server installation completed
2024-10-11T11:00:56.850Z INFO cmd.serve.grpc finished unary call with code OK {"grpc.start_time": "2024-10-11T11:00:35Z", "system": "grpc","span.kind": "server", "grpc.service": "agent.AutomationService", "grpc.method": "Install", "peer.address": "10.42.0.12:38976", "grpc.code": "OK", "grpc.time_ms": 20929}
2024-10-11T11:00:56.874Z INFO cmd.serve.grpc shutting down the server
2024-10-11T11:00:56.874Z INFO cmd.serve.grpc [core][Server #1 ListenSocket #2]ListenSocket deleted {"system": "grpc", "grpc_log": true}
2024-10-11T11:00:56.874Z INFO cmd.serve server stoppedrich-application-35618
10/11/2024, 11:49 AMI have figured out what's going on. If I change the stack definition, then something breaks. If I delete and create again, then it seems to log some relevant message. My problem was that the stack's name, the organisation part of the name has to be "organization" for some reason. It can't be my own value. That makes no sense.
rich-application-35618
10/11/2024, 11:49 AMAlso, now that I have fixed that problem, I can see that the answer to my first question is that, yes, you can define your own stack, and it will be created as expected.
rich-application-35618
10/11/2024, 4:20 PMIt would still be nice to know if it's possible to get better log messages than the above because it seems to happen a lot and debugging these are basically impossible.
9 Views