Talos k8s cluster: Create a VM failed calling webhook "virtualmachines-mutator.kubevirt.io"

[Rammurthy5]

What happened: when i try kubectl apply -f https://kubevirt.io/labs/manifests/vm.yaml I get error as below,

Error from server (InternalError): error when creating "https://kubevirt.io/labs/manifests/vm.yaml": Internal error occurred: failed calling webhook "virtualmachines-mutator.kubevirt.io": failed to call webhook: Post "https://virt-api.kubevirt.svc:443/virtualmachines-mutate?timeout=10s": context deadline exceeded

What you expected to happen: virtualmachine.kubevirt.io "testvm" created virtualmachineinstancepreset.kubevirt.io "small" created

How to reproduce it (as minimally and precisely as possible): create a talos cluster with cilium CNI installed and OpenEBS for storage.

Environment:

• KubeVirt version (use virtctl version): v1.2.0
• Kubernetes version (use kubectl version): v1.28.0
• VM or VMI specifications: N/A
• Cloud provider or hardware configuration: Talos Linux on AWS ec2
• OS (e.g. from /etc/os-release): Talos Linux v1.5.5
• Kernel (e.g. uname -a): Linux
• Install tools: Cilium CNI, OpenEBS for storage
• Others: N/A

[fabiand]

@smira @andrewrynhard is there anybody from your side who has an idea?

[smira]

This has nothing to do with Talos or kubevirt most probably, but webhooks don't work, so it should be CNI or networking in general

[kubevirt-bot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[xpivarc]

This has nothing to do with Talos or kubevirt most probably, but webhooks don't work, so it should be CNI or networking in general

I agree, this looks like CNI issue. Is any other webhook working?

[kubevirt-bot]

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[kubevirt-bot]

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

[kubevirt-bot]

@kubevirt-bot: Closing this issue.

In response to [this](https://github.com/kubevirt/kubevirt/issues/11669#issuecomment-2334178395): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.