-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Internal error occured: context deadline exceeded #3317
Comments
EDIT: This is the example to update the firewall rules for this case gcloud compute firewall-rules update <FIREWALL_NAME> --allow <OTHER_PORT>,tcp:8443 |
@fx2y is correct I had same issue look for your clusters master's ingress firewall rule. In the cloud console it looks like this. |
That's brilliant. Thanks for that. I suspected something like this was the case, but could not work out where the firewall rule needed updating. |
Thanks. @scott-kawaguchi
|
Expected Behavior
Create a new ClusterTask and TaskRun
Actual Behavior
Steps to Reproduce the Problem
Pre-requisites
Steps
Install Tekton
kubectl apply --filename https://storage.googleapis.com/tekton-releases/pipeline/latest/release.yaml
Create Kustomization template and resources
base/kustomization.yaml
base/task.yaml
Additional Info
Kubernetes version:
Output of
kubectl version
:Tekton Pipeline version:
Output of
tkn version
orkubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'
I have looked through this previously closed issue but it did not provide any fix for the problem. I also notice the service is trying to resolve DNS to
https://tekton-pipelines-webhook.tekton-pipelines.svc:443/defaulting?timeout=30s
does the service DNS need to behttps://tekton-pipelines-webhook.tekton-pipelines.svc.cluster.local:443/defaulting?timeout=30s
i.e. to include<SERVICE_NAME>.<NAMESPACE>.svc.cluster.local
or one of the other options for service DNS resolution as detailed here https://cloud.google.com/kubernetes-engine/docs/concepts/service-discovery?It says Tekton is ready off-the-shelf for GKE, so I wouldn't expect any DNS changes to be made, but the DNS it is attempting to resolve does not look correct, or at least I have not ever used or seen it in like this before i.e. without anything after the
.svc
The text was updated successfully, but these errors were encountered: