-
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
Getting Started instructions fail on GKE v 1.17 #3910
Comments
Experienced a similar problem with a private GKE cluster version v1.19.9-gke.1900. In my case I installed tektoncd v0.24.2 with the webhook controller running. The error: @paultiplady The problem was a firewall rule on the GCP which allows just traffic to ports 443 and 10250 from the control plane to Pods on worker nodes. |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
No news and even no comments on this... looks a bit weird... |
/remove-lifecycle rotten |
I think we've seen a very similar issue pop up occasionally in the past that we were a bit stumped by (e.g. #2207) but this might be different b/c in those cases I think the error was something like 'connection refused' vs this one has 'service not found' (could be the same underlying issue tho?). if it WAS a similar issue then i think you'd only see this happen very rarely and not consistently |
6 months ago together with @paolocarta we tried to deploy Tekton on a GKE private cluster a good amount of times. We were not able to see the same behaviour 2 times in a row. If I remember well we faced both "connection refused" and "service not found" issues, but I cannot be sure as passed too much time. After 2 weeks and many attempts we gave up and chose another CI/CD tool. |
I am facing the same issue on a private GKE cluster |
following the instructions at #3317 (comment) seems to solve the issue. |
Expected Behavior
Running the command in https://github.com/tektoncd/pipeline/blob/main/docs/install.md should succeed and produce a working install.
Actual Behavior
kubectl apply
command fails and does not produce a working install.Steps to Reproduce the Problem
kubectl apply -f https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.22.0/release.yaml
Additional Info
Looking at the failing webhook pods, it seems the ConfigMaps are not in place in time:
But the configmaps are being validated by the
tekton-pipelines-webhook
that cannot start because of the missing configmaps. Validation deadlock?I worked around this by moving the configmaps above the
ValidatingWebhookConfiguration
manifests in the file.Or alternatively, without destroying everything and re-creating, this worked too:
Kubernetes version:
Output of
kubectl version
:None (Tekton not installed yet)
The text was updated successfully, but these errors were encountered: