Support ClusterTrustBundle v1 on clusters without v1beta1

Cerrado
#1,898 0 comentarios 3 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@ahmedtd ya está trabajando en esto.

Desde el 29/9/2026.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
52/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go, kubernetes, shell
Área
api, backend, devops

Línea de trabajo

Start by locating the ClusterTrustBundle callers in the signer, atelet, atecontroller, API client, ate-setup, and shell installer. Trace how each discovers or selects the served API version, then inspect the existing PodCertificateRequest version-handling coverage. Done means v1-only, v1beta1-only, both, and neither are covered, with a clear failure when neither is served and no indefinite wait.

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

Descripción

area/dev-infra area/security kind/bug prio/P1

Reproduced on AKS 1.37.0: PodCertificateRequest and ClusterTrustBundle are served at certificates.k8s.io/v1, but /apis/certificates.k8s.io/v1beta1 returns NotFound. With healthy nodes, hack/install-ate.sh --deploy-ate-system reaches:

Waiting for podcertificate ClusterTrustBundles to be ready...

Current scope: agent-substrate/substrate#1829 has since added API discovery, v1 preference, and v1beta1 fallback for the signer's PodCertificateRequest watch and status writes. The repro used an older image, whose logs showed failed to list *v1beta1.PodCertificateRequest; that particular error is no longer expected from current main on this cluster. ClusterTrustBundle callers still use v1beta1: the signer publishes bundles through it, atelet and atecontroller watch/read bundles through it, the API client reads them through it, and ate-setup waits for a v1beta1 bundle. The shell installer waits indefinitely for bundles the signer cannot publish on a v1-only cluster.

Expected: Select a served CTB version (prefer v1, fall back to v1beta1) across producers, consumers, and install checks. Preserve support for 1.36 clusters serving only v1beta1; fail clearly if neither API is served instead of waiting indefinitely. Add coverage for v1-only, beta-only, both, and neither.

Related: agent-substrate/substrate#1819 documents the same v1-only mismatch for bring-your-own 1.37 GKE clusters, but focuses on GKE setup and documentation.

Lenguaje dominante
Go
Estrellas
5.9k
Forks
637
Merge medio
2 d 1 h
PR fusionados (30 d)
523

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 agent-substrate/substrate

Todos los issues de agent-substrate/substrate

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.