API Connect

 View Only

 Kubernetes Lab Environment – Kyverno Webhook Error

Autumn Falls's profile image
Autumn Falls posted 02/23/26 03:35 PM

Hello everyone, I am currently working on the Kubernetes lab in the IBM Full Stack Software Engineering course on Coursera. After restarting the lab environment, I am unable to create any Kubernetes resources.

Even a basic command such as:

kubectl run test --image=nginx --restart=Never

fails with the following error:

Error from server (InternalError): Internal error occurred: failed calling webhook "mutate.kyverno.svc-fail":

failed to call webhook: Post "https://kyverno-svc.kyverno.svc:443/mutate/fail?timeout=10s":

no endpoints available for service "kyverno-svc"

Additionally, running:

kubectl get pods

returns:

No resources found in sn-labs-autumnfalls6 namespace.

This indicates that the Kyverno admission controller service (kyverno-svc) in the cluster has no active endpoints, which is preventing the Kubernetes API server from completing admission requests. As a result, all pod creation requests are being rejected at the admission control stage.

Since this is a managed lab environment, I do not have cluster-admin permissions to inspect or restart the Kyverno pods or modify the webhook configuration. The lab has already been restarted, but the issue persists.

This appears to be a backend cluster infrastructure issue rather than a configuration problem within my project.

Could you please:

Reassign my lab session to a healthy Kubernetes cluster, or

Repair the Kyverno service in the current cluster?

I have attempted multiple troubleshooting steps beyond restarting the lab environment:

  1. I fully restarted the lab session and waited several minutes before running any commands to ensure the cluster had time to initialize.

  2. I tested the cluster using a basic command:

    kubectl run test --image=nginx --restart=Never

    This fails immediately with:

    failed calling webhook "mutate.kyverno.svc-fail":
    no endpoints available for service "kyverno-svc"
  3. I confirmed that no pods are being created in my namespace:

    kubectl get pods

    Output:

    No resources found in sn-labs-autumnfalls6 namespace.
  4. Since this error occurs before any project-specific deployment steps, it indicates the issue happens at the Kubernetes admission control stage.

The error suggests that the Kyverno admission controller service (kyverno-svc) has no active endpoints in the cluster. Because this is a managed lab environment, I do not have cluster-admin permissions to inspect or restart the Kyverno pods or modify webhook configurations.

At this point, even the most basic pod creation request fails, which makes it impossible to proceed with the lab tasks.

Could you please verify whether the backend cluster assigned to my lab session is healthy, or reassign me to a functioning Kubernetes cluster?

Chris Dudley's profile image
Chris Dudley

Sorry this is not something anyone in this forum can help with - it doesn’t appear to have anything to do with IBM API Connect?