Post "https://webhook.knative-servin │ │ g.svc:443/defaulting?timeout=10s": context deadline exceeded

[rajatgupta828-stem]

What version of Knative?

v1.17.8

Expected Behavior

Knative serving should be set up

Actual Behavior

Name:         knative-serving
Namespace:    knative-serving
Labels:       <none>
Annotations:  <none>
API Version:  operator.knative.dev/v1beta1
Kind:         KnativeServing
Metadata:
  Creation Timestamp:  2025-08-20T12:14:00Z
  Finalizers:
    knativeservings.operator.knative.dev
  Generation:        1
  Resource Version:  305903772
  UID:               367cc9fc-d917-487e-b578-9d0188b8a2a7
Spec:
  Config:
    Domain:
      xip.io:
    Network:
      ingress.class:  kourier.ingress.networking.knative.dev
  Ingress:
    Kourier:
      Enabled:  true
Status:
  Conditions:
    Last Transition Time:  2025-08-20T12:14:00Z
    Status:                Unknown
    Type:                  DependenciesInstalled
    Last Transition Time:  2025-08-20T12:14:47Z
    Status:                True
    Type:                  DeploymentsAvailable
    Last Transition Time:  2025-08-20T12:14:57Z
    Message:               Install failed with message: Internal error occurred: failed calling webhook "webhook.serving.knative.dev": failed to call webhook: Post "https://webhook.knative-serving.svc:443/defaulting?timeout=10s": context deadline exceeded
    Reason:                Error
    Status:                False
    Type:                  InstallSucceeded
    Last Transition Time:  2025-08-20T12:14:57Z
    Message:               Install failed with message: Internal error occurred: failed calling webhook "webhook.serving.knative.dev": failed to call webhook: Post "https://webhook.knative-serving.svc:443/defaulting?timeout=10s": context deadline exceeded
    Reason:                Error
    Status:                False
    Type:                  Ready
    Last Transition Time:  2025-08-20T12:14:00Z
    Status:                True
    Type:                  VersionMigrationEligible
  Observed Generation:     1
Events:
  Type     Reason           Age                 From                       Message
  ----     ------           ----                ----                       -------
  Normal   FinalizerUpdate  45m                 knativeserving-controller  Updated "knative-serving" finalizers
  Warning  InternalError    74s (x20 over 44m)  knativeserving-controller  failed to apply webhooks: Internal error occurred: failed calling webhook "webhook.serving.knative.dev": failed to call webhook: Post "https://webhook.knative-serving.svc:443/defaulting?timeout=10s": context deadline exceeded

Steps to Reproduce the Problem

used following - https://knative.dev/v1.17-docs/install/operator/knative-with-operators/#verify-the-knative-serving-deployment manual.

k get pods  -n knative-serving
NAME                                                     READY   STATUS      RESTARTS   AGE
3scale-kourier-gateway-bc6d7f8cf-4q2k2                   1/1     Running     0          46m
activator-78c869c44f-sqhkj                               1/1     Running     0          46m
autoscaler-7c8dbd7fb8-8mkzf                              1/1     Running     0          46m
autoscaler-hpa-5b8c5d965-sckdv                           1/1     Running     0          46m
cleanup-serving-serving-1.17.1-zw9ht                     0/1     Completed   0          2m50s
controller-7cd6d74f7c-k9mgb                              1/1     Running     0          46m
net-kourier-controller-666486975f-qj4ff                  1/1     Running     0          46m
storage-version-migration-serving-serving-1.17.1-b29j6   0/1     Completed   0          2m50s
webhook-fff7c8675-prq8s                                  1/1     Running     0          46m

k get pods  -n knative-operator
NAME                                READY   STATUS    RESTARTS      AGE
dns-debug-6ccfcc8968-hcw9d          1/1     Running   2 (26m ago)   146m
knative-operator-f46c65fb5-j86c7    1/1     Running   0             146m
operator-webhook-7d4947b667-dqvvz   1/1     Running   0             146m

[dprotaso]

What's your operator config set to?

[rajatgupta828-stem]

Hi I have used Helm chart to deploy operator helm charts following this huide - https://knative.dev/docs/install/operator/knative-with-operators/#install-the-knative-operator

helm get values knative-operator -n knative-operator --all
COMPUTED VALUES:
knative_operator:
  knative_operator:
    affinity: {}
    containerSecurityContext:
      allowPrivilegeEscalation: false
      readOnlyRootFilesystem: true
      runAsNonRoot: true
    image: gcr.io/knative-releases/knative.dev/operator/cmd/operator
    resources:
      limits:
        cpu: 1000m
        memory: 1000Mi
      requests:
        cpu: 100m
        memory: 100Mi
    tag: v1.17.8
  kubernetes_min_version: v1.25.0
  operator_webhook:
    affinity:
      podAntiAffinity:
        preferredDuringSchedulingIgnoredDuringExecution:
        - podAffinityTerm:
            labelSelector:
              matchLabels:
                app: operator-webhook
            topologyKey: kubernetes.io/hostname
          weight: 100
    containerSecurityContext:
      allowPrivilegeEscalation: false
      readOnlyRootFilesystem: true
      runAsNonRoot: true
    image: gcr.io/knative-releases/knative.dev/operator/cmd/webhook
    resources:
      limits:
        cpu: 500m
        memory: 500Mi
      requests:
        cpu: 100m
        memory: 100Mi
    tag: v1.17.8
nodeSelector:
  eks.amazonaws.com/compute-type: auto
  k8s.tpint.co/workload-type: infra
  kubernetes.io/os: linux
tolerations:
- effect: NoSchedule
  key: k8s.tpint.co/workload-type
  operator: Equal
  value: infra
- effect: NoSchedule
  key: eks-auto-mode
  operator: Exists
  value: ""