Proposal: Move the Tekton Operator Helm chart to a dedicated repository

Abierto
  • ¿Algo no está bien?
#3,977 2 comentarios 3 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
github-actions, helm, kubernetes
Área
ci-cd, devops, release

Línea de trabajo

La propuesta no nombra archivos, pruebas ni puntos de entrada. Empieza revisando el chart de Helm existente y su proceso de release actual; después, documenta las decisiones sobre ownership, compatibilidad de versiones, migración y distribución. Se considera terminado cuando los maintainers hayan acordado el plan de repositorio, release, pruebas y migración.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

kind/feature

Feature request

I would like to propose moving the Tekton Operator Helm chart into a dedicated repository—for example:

github.com/tektoncd/operator-helm-chart

The goal is to isolate the Helm chart from the operator source code and make it a standalone installation and distribution method.

Motivation

A dedicated repository could provide several benefits:

  • Make the chart easier to discover, use, test, and maintain.
  • Allow contributors to work on the chart without navigating the complete operator codebase.
  • Give the chart its own release lifecycle and versioning strategy.
  • Provide clearer documentation focused specifically on Helm-based installation.
  • Simplify automated chart validation, packaging, and publishing.
  • Make the chart easier to distribute through services such as Artifact Hub.

Distribution

As part of this work, we should define how the chart will be released and distributed to the wider community. This could include:

  • Publishing the chart as an OCI artifact to ghcr.io.
  • Listing the chart on Artifact Hub.
  • Signing releases and publishing provenance information.
  • Automating chart testing and publishing through GitHub Actions.
  • Documenting the relationship between the chart version and the Tekton Operator version.

For example, users could install the operator from an OCI registry with:

helm install tekton-operator \
  oci://ghcr.io/tektoncd/charts/tekton-operator \
  --version <version>

The OCI repository could also be consumed directly by GitOps tools such as Flux.

Compatibility and ownership

Before separating the chart, we would need to agree on:

  • Who maintains and reviews chart changes.
  • How chart changes are tested against Operator releases.
  • Whether chart and Operator versions should remain aligned.
  • How breaking changes are communicated.
  • How existing chart users are migrated to the new repository and registry location.

Contribution

I would be happy to help with this work, including:

  • Creating or restructuring the Helm chart repository.
  • Improving the chart structure and documentation.
  • Adding chart tests and release automation.
  • Setting up OCI publishing.
  • Preparing the chart for listing on Artifact Hub.
  • Documenting installation through Helm and GitOps tools such as Flux.

If the maintainers are open to this direction, I would be glad to help prepare a more detailed implementation and migration plan.

Lenguaje dominante
Go
Estrellas
606
Forks
270
Merge medio
1 d 7 h
PR fusionados (30 d)
159

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de tektoncd/operator

Todos los issues de tektoncd/operator

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.