Supported path for CSI drivers that need a node DaemonSet

Ouverte
  • Quelque chose ne va pas ?
#3,056 4 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
Active
Stack technique
go, kubernetes
Domaine
backend, devops

Piste de recherche

Read the registry+v1 validator at internal/operator-controller/rukpak/render/registryv1/validators/validator.go#L355-L364 and the supported resource list in operator-registry/pkg/lib/bundle/supported_resources.go#L33-L56, then review draft PR #3057 and discussion #2992. The issue asks maintainers to choose a supported direction for CSI DaemonSets, so clarify the v1 bundle and compatibility design before implementation.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

CSI drivers usually ship a controller Deployment and a node plugin DaemonSet. In registry+v1 the Deployment fits the CSV, but the renderer rejects the DaemonSet through operator-registry's supported kinds. So CSI operators create it at runtime from their own controller; I could not find a certified or community bundle that ships one.

I asked about this in 2023 on the closed #1022 and in discussion #2992. Since then the experimental Helm chart gate was removed (#2798) and the next bundle format is still open, so I would like to know the supported path in OLM v1 for a CSI driver that needs a node DaemonSet.

One option I tried, in draft PR #3057: an Alpha gate, off by default, that lets the registry+v1 renderer accept a DaemonSet with the alpha BoxcutterRuntime, plus a DaemonSet progression probe. It is about 50 lines of production code and does not touch operator-registry. OLM v0 cannot use such a bundle: opm accepts it into a catalog, but on install v0 creates the CSV, skips the DaemonSet as unsupported and fails the InstallPlan, leaving the operator half installed. So a bundle that uses the gate is v1 only, and nodeSelector and tolerations through spec.config are not covered yet. Is a gate like this a direction you would consider for v1, or should CSI operators keep creating the DaemonSet from their controller until the next bundle format?

Langage dominant
Go
Étoiles
215
Forks
86
Merge moyen
1 j 6 h
PR mergées (30 j)
124

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de operator-framework/operator-controller

Toutes les issues de operator-framework/operator-controller

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.