Pipeline: Error from server (InternalError): error when creating "task.yaml": Internal error occurred: failed calling webhook "webhook.pipeline.tekton.dev": Post https://tekton-pipelines-webhook.tekton-pipelines.svc:443/defaulting?timeout=30s: dial tcp <IPADDR>:8443: i/o timeout

Created on 13 Jul 2020  路  2Comments  路  Source: tektoncd/pipeline

Expected Behavior

Be able to create a Task and TaskRun definition

Actual Behavior

Getting error:

Error from server (InternalError): error when creating "task.yaml": Internal error occurred: failed calling webhook "webhook.pipeline.tekton.dev": Post https://tekton-pipelines-webhook.tekton-pipelines.svc:443/defaulting?timeout=30s: dial tcp <IPADDR>:8443: i/o timeout

Steps to Reproduce the Problem

  1. Install Tekton Pipelines by:
kubectl apply --filename https://storage.googleapis.com/tekton-releases/pipeline/latest/release.yaml
  1. Add a Task definition (from the documentation):
$ cat hello-world-task.yaml 
apiVersion: tekton.dev/v1beta1
kind: Task
metadata:
  name: echo-hello-world
  namespace: tekton-pipelines
spec:
  steps:
    - name: echo
      image: ubuntu
      command:
        - echo
      args:
        - "Hello World"
$ kubectl apply -f hello-world-task.yaml
Error from server (InternalError): error when creating "task.yaml": Internal error occurred: failed calling webhook "webhook.pipeline.tekton.dev": Post https://tekton-pipelines-webhook.tekton-pipelines.svc:443/de
faulting?timeout=30s: dial tcp 10.100.4.33:8443: i/o timeout

Additional Info

  • Kubernetes version: GKE v1.16.10-gke.8
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.10", GitCommit:"f3add640dbcd4f3c33a7749f38baaac0b3fe810d", GitTreeState:"clean", BuildDate:"2020-05-20T14:00:52Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"16+", GitVersion:"v1.16.10-gke.8", GitCommit:"fd29f95f189cb16dd8fe0bd5dc8b485dfd049d2c", GitTreeState:"clean", BuildDate:"2020-06-23T23:44:30Z", GoVersion:"go1.13.9b4", Compiler:"gc", Platform:"linux/amd64"}
  • Tekton Pipeline version: v0.14.1
$ kubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'
v0.14.1

This is a fresh installation of both GKE and Tekton Pipelines.

kinbug

Most helpful comment

Issue solved and not really a Tekton per se problem (but maybe worth documenting about it?) Since my cluster is a "VPC Native" GKE cluster, it is required that the port is allowed on node pool (port 8443 in this case).

All 2 comments

Also commented on https://github.com/tektoncd/pipeline/issues/2831, maybe related?

Issue solved and not really a Tekton per se problem (but maybe worth documenting about it?) Since my cluster is a "VPC Native" GKE cluster, it is required that the port is allowed on node pool (port 8443 in this case).

Was this page helpful?
0 / 5 - 0 ratings

Related issues

bobcatfish picture bobcatfish  路  4Comments

csantanapr picture csantanapr  路  3Comments

chmouel picture chmouel  路  3Comments

r0bj picture r0bj  路  3Comments

sbwsg picture sbwsg  路  3Comments