You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I try to create a Kubernetes cluster on Proxmox VM (created via Pulumi).
When I run pulumi up I need to wait a while until kubernetes resources show up in preview, I mean these:
When they finally show up, after about 10 seconds the pulumi preview fails with exception:
Exception: invoke of kubernetes:helm:template failed: invocation of kubernetes:helm:template returned an error: failed to generate YAML for specified Helm chart: could not get server version from Kubernetes: Get "https://192.168.1.101:6443/version?timeout=32s": dial tcp 192.168.1.101:6443: i/o timeout
192.168.1.101 is ip address of my master node that is not yet created (it should get created during pulumi up).
I made it so kubernetes provider depends on command that downloads kube config from master node. Namespace depends on the provider, and helm chart depends on the namespace... So I would expect the helm chart to request version from master node during pulumi up, when it's time to create the chart... Not during the preview .
Dependencies:
NAME VERSION
ansible 9.5.1
mypy 1.10.0
pip 23.3.1
pulumi_command 0.10.0
pulumi_kubernetes 4.11.0
pulumi_proxmoxve 6.4.1
Pulumi locates its logs in /tmp by default
Additional context
When I comment out the kubernetes stuff and run pulumi up, Pulumi successfully setups my master node - all pods (except coredns) are running, node is NotReady because no CNI installed yet.
After that I can uncomment kubernetes resources, run pulumi up again and it will successfully deploy Calico (after which my master node becomes Ready).
I cannot switch to using Helm Release, because it also doesn't work well - when I try to pulumi destroy resources, the command gets stuck on deleting the Release.
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered:
We currently fail to render a preview for Chart V3 if the cluster is
unreachable.
Instead of failing, we can emit a warning since Helm is still able to
generate the template without the version set.
Alternatively, we could check `k.clusterUnreachable` as part of `Invoke`
but we wouldn't be able to return a rich preview.
Added a failing E2E test.
Fixes#2985.
What happened?
I try to create a Kubernetes cluster on Proxmox VM (created via Pulumi).
When I run
pulumi up
I need to wait a while until kubernetes resources show up in preview, I mean these:When they finally show up, after about 10 seconds the pulumi preview fails with exception:
192.168.1.101 is ip address of my master node that is not yet created (it should get created during
pulumi up
).I made it so kubernetes provider depends on command that downloads kube config from master node. Namespace depends on the provider, and helm chart depends on the namespace... So I would expect the helm chart to request version from master node during
pulumi up
, when it's time to create the chart... Not during the preview .Example
Output of
pulumi about
CLI
Version 3.113.3
Go Version go1.22.2
Go Compiler gc
Plugins
KIND NAME VERSION
resource command 0.10.0
resource kubernetes 4.11.0
resource proxmoxve 6.4.1
language python unknown
Host
OS ubuntu
Version 22.04
Arch x86_64
This project is written in python: executable='/home/lol/repos/infra/.venv/bin/python3' version='3.12.1'
Current Stack: lolol/infra/dev
Found no resources associated with dev
Found no pending operations associated with dev
Backend
Name pulumi.com
URL https://app.pulumi.com/lolol
User lolol
Organizations lolol
Token type personal
Dependencies:
NAME VERSION
ansible 9.5.1
mypy 1.10.0
pip 23.3.1
pulumi_command 0.10.0
pulumi_kubernetes 4.11.0
pulumi_proxmoxve 6.4.1
Pulumi locates its logs in /tmp by default
Additional context
When I comment out the kubernetes stuff and run
pulumi up
, Pulumi successfully setups my master node - all pods (except coredns) are running, node is NotReady because no CNI installed yet.After that I can uncomment kubernetes resources, run
pulumi up
again and it will successfully deploy Calico (after which my master node becomes Ready).I cannot switch to using Helm Release, because it also doesn't work well - when I try to
pulumi destroy
resources, the command gets stuck on deleting the Release.Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: