Pipeline: Run the kubectl apply command to install Tekton Pipelines and its dependencies failed

Created on 17 Feb 2020  路  2Comments  路  Source: tektoncd/pipeline

Expected Behavior

Run the kubectl apply command to install Tekton Pipelines and its dependencies successed.

Actual Behavior

namespace/tekton-pipelines unchanged
podsecuritypolicy.policy/tekton-pipelines configured
clusterrole.rbac.authorization.k8s.io/tekton-pipelines-admin unchanged
clusterrolebinding.rbac.authorization.k8s.io/tekton-pipelines-controller-admin unchanged
customresourcedefinition.apiextensions.k8s.io/clustertasks.tekton.dev unchanged
customresourcedefinition.apiextensions.k8s.io/conditions.tekton.dev unchanged
customresourcedefinition.apiextensions.k8s.io/images.caching.internal.knative.dev unchanged
customresourcedefinition.apiextensions.k8s.io/pipelines.tekton.dev unchanged
customresourcedefinition.apiextensions.k8s.io/pipelineruns.tekton.dev unchanged
customresourcedefinition.apiextensions.k8s.io/pipelineresources.tekton.dev unchanged
customresourcedefinition.apiextensions.k8s.io/tasks.tekton.dev unchanged
customresourcedefinition.apiextensions.k8s.io/taskruns.tekton.dev unchanged
clusterrole.rbac.authorization.k8s.io/tekton-aggregate-edit unchanged
clusterrole.rbac.authorization.k8s.io/tekton-aggregate-view unchanged
Error from server (Forbidden): error when creating "release.yaml": serviceaccounts "tekton-pipelines-controller" is forbidden: unable to create new content in namespace tekton-pipelines because it is being terminated
Error from server (Forbidden): error when creating "release.yaml": services "tekton-pipelines-controller" is forbidden: unable to create new content in namespace tekton-pipelines because it is being terminated
Error from server (Forbidden): error when creating "release.yaml": services "tekton-pipelines-webhook" is forbidden: unable to create new content in namespace tekton-pipelines because it is being terminated
Error from server (Forbidden): error when creating "release.yaml": configmaps "config-artifact-bucket" is forbidden: unable to create new content in namespace tekton-pipelines because it is being terminated
Error from server (Forbidden): error when creating "release.yaml": configmaps "config-artifact-pvc" is forbidden: unable to create new content in namespace tekton-pipelines because it is being terminated
Error from server (Forbidden): error when creating "release.yaml": configmaps "config-defaults" is forbidden: unable to create new content in namespace tekton-pipelines because it is being terminated
Error from server (Forbidden): error when creating "release.yaml": configmaps "config-logging" is forbidden: unable to create new content in namespace tekton-pipelines because it is being terminated
Error from server (Forbidden): error when creating "release.yaml": configmaps "config-observability" is forbidden: unable to create new content in namespace tekton-pipelines because it is being terminated
Error from server (Forbidden): error when creating "release.yaml": deployments.apps "tekton-pipelines-controller" is forbidden: unable to create new content in namespace tekton-pipelines because it is being terminated
Error from server (Forbidden): error when creating "release.yaml": deployments.apps "tekton-pipelines-webhook" is forbidden: unable to create new content in namespace tekton-pipelines because it is being terminated

Steps to Reproduce the Problem

  1. Exec kubectl apply --filename https://storage.googleapis.com/tekton-releases/pipeline/latest/release.yaml

2.Failed

Additional Info

The public cloud I used is Alibaba Cloud.

kinquestion

Most helpful comment

/kind question

@hantmac from the logs, it seems there was a previous installation of Tekton Pipelines and it is still being terminated (unable to create new content in namespace tekton-pipelines because it is being terminated). This is a kubernetes problems I feel, for some reason the tekton-pipelines namespace doesn't get terminated (or maybe with time it did).

Yeah, the namespace still being terminated since I delete it, and I followed this page https://medium.com/@newtondev/how-to-fix-kubernetes-namespace-deleting-stuck-in-terminating-state-5ed75792647e to force to delete the namespace of tekton-pipeline and re-install successfully. Thanks for your reply very much!

All 2 comments

/kind question

@hantmac from the logs, it seems there was a previous installation of Tekton Pipelines and it is still being terminated (unable to create new content in namespace tekton-pipelines because it is being terminated). This is a kubernetes problems I feel, for some reason the tekton-pipelines namespace doesn't get terminated (or maybe with time it did).

/kind question

@hantmac from the logs, it seems there was a previous installation of Tekton Pipelines and it is still being terminated (unable to create new content in namespace tekton-pipelines because it is being terminated). This is a kubernetes problems I feel, for some reason the tekton-pipelines namespace doesn't get terminated (or maybe with time it did).

Yeah, the namespace still being terminated since I delete it, and I followed this page https://medium.com/@newtondev/how-to-fix-kubernetes-namespace-deleting-stuck-in-terminating-state-5ed75792647e to force to delete the namespace of tekton-pipeline and re-install successfully. Thanks for your reply very much!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

objectiveous picture objectiveous  路  3Comments

castlemilk picture castlemilk  路  4Comments

JCzz picture JCzz  路  3Comments

r0bj picture r0bj  路  3Comments

pritidesai picture pritidesai  路  4Comments