Expected Behavior
When installing the components via the helmchart i expect them all to run successfully
Actual Behavior
When installing the chart it has installed the components to tekton-pipelines namespace. Within that namespace the pvc was in pending state, because the storageClass was missing.
I couldn't find any place where to configure this, so what i did is manually editing the pvc and setting the storageClass.
Steps to Reproduce the Problem
- Install the chart
- Go to tekton-pipelines namespace pvs
- Describe the pvc for the result postgres
Additional Info
We deploy our stuff via flux, so here are the manifests that we used:
---
apiVersion: source.toolkit.fluxcd.io/v1
kind: GitRepository
metadata:
name: tektoncd-operator
namespace: tekton
spec:
interval: 10m
url: https://github.com/tektoncd/operator
ref:
tag: v0.78.1
---
apiVersion: source.toolkit.fluxcd.io/v1
kind: HelmChart
metadata:
name: tekton-operator
namespace: tekton
spec:
interval: 10m
chart: charts/tekton-operator
sourceRef:
kind: GitRepository
name: tektoncd-operator
---
apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
name: tekton-operator
namespace: tekton
spec:
chartRef:
kind: HelmChart
name: tekton-operator
namespace: tekton
interval: 10m
install:
crds: Create
values:
installCRDs: true
Expected Behavior
When installing the components via the helmchart i expect them all to run successfully
Actual Behavior
When installing the chart it has installed the components to tekton-pipelines namespace. Within that namespace the pvc was in pending state, because the storageClass was missing.
I couldn't find any place where to configure this, so what i did is manually editing the pvc and setting the storageClass.
Steps to Reproduce the Problem
Additional Info
Kubernetes version:
Tekton Pipeline version: v1.6.0
We deploy our stuff via flux, so here are the manifests that we used: