search

pulumiverse / pulumi-talos

Pulumi provider for Talos
Mozilla Public License 2.0
41 stars 11 forks source link

`0.4.1` - Kubeconfig resource times out #112

Open muhlba91 opened 2 weeks ago

muhlba91 commented 2 weeks ago

When using the talos.cluster.Kubeconfig or talos.cluster.getKubeconfigOutput resource, the provider is not able to retrieve a working kubeconfig. Before 0.4.1 I was on 0.2.0 and used talos.cluster.getKubeconfigOutput with the same parameters. This worked flawlessly before the update. It just waits and times out now.

The code looks like:

new talos.cluster.Kubeconfig('talos-kubeconfig',
    {
          clientConfiguration: talosSecrets.clientConfiguration,
          node: talosConfig.machine.network.ip.v4,
    },
    {}
)

The error is (this goes on until Pulumi times out the resource creation):

    2024/11/06 07:59:20 [DEBUG] Waiting for state to become: [success]
    2024/11/06 07:59:20 [TRACE] Waiting 500ms before next try
    2024/11/06 07:59:20 [TRACE] Waiting 1s before next try
    2024/11/06 07:59:21 [TRACE] Waiting 2s before next try
    2024/11/06 07:59:23 [TRACE] Waiting 4s before next try
    2024/11/06 07:59:27 [TRACE] Waiting 8s before next try
shkarface commented 1 week ago

I have the same problem as well, any idea @ringods ?

xzizka commented 1 week ago

Could you please try to set the env variable export GRPC_ENFORCE_ALPN_ENABLED=false before you run the pulumi up? See more here: https://github.com/pulumiverse/pulumi-talos/issues/113

muhlba91 commented 1 week ago

thank you, this works now when setting the env variable.

shkarface commented 1 week ago

I can also confirm that the new go-grpc was the problem, setting the env var or upgrading to talos 1.8.3 fixed the issue.

xzizka commented 1 week ago

I can also confirm that the new go-grpc was the problem, setting the env var or upgrading to talos 1.8.3 fixed the issue.

@shkarface So if I use Talos 1.8.3 as an image, it does not need the env variable mentioned above?

shkarface commented 6 days ago

I can also confirm that the new go-grpc was the problem, setting the env var or upgrading to talos 1.8.3 fixed the issue.

@shkarface So if I use Talos 1.8.3 as an image, it does not need the env variable mentioned above?

No, as Talos 1.8.3 already contains the ALPN in the TLS extensions response