tektoncd / tektoncd/operator

TektonConfig CRD - Capability to add pipeline and triggers namespace as dashboard properties

Open
#1,620 10 comments 1 reaction 1 assignee View on GitHub

@T3-git is already working on this.

Since Dec 11, 2023.

good first issue Hacktoberfest help wanted kind/feature lifecycle/frozen
Dominant language
Go
Stars
608
Forks
263
Avg merge
1d 3h
Merged PRs (30d)
125

Description

Feature request

Currently by default the dashboard install using the operator is setting the default namespace for tekton pipelines and tekton triggers to 'tekton-pipelines' . In certain use cases if the operator is installing tekton resources in a different namespace the dashboard is failing to read the pipeline and triggers config due to the below setting.

args:
'--port=9097'
- '--logout-url='
- '--pipelines-namespace=tekton-pipelines'
- '--triggers-namespace=tekton-pipelines'
- '--read-only=true'
- '--log-level=info'
- '--log-format=json'
- '--namespace='
- '--stream-logs=true'

It would we helpful if all these options can be parameterized as dashboard properties in the TektonConfig CRD while installing and setting properties for dashboard.

Currently it supports only readonly mode and external logs feature as of now
https://github.com/tektoncd/operator/blob/main/pkg/apis/operator/v1alpha1/tektondashboard_types.go#L88

Use case

If we want to install tekton components in a different namespace other than the default namespace 'tekton-pipelines'.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.