Closed Rammurthy5 closed 1 day ago
@smira @andrewrynhard is there anybody from your side who has an idea?
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
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
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?
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
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
/close
@kubevirt-bot: Closing this issue.
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:
virtctl version
): v1.2.0kubectl version
): v1.28.0uname -a
): Linux