Supported path for CSI drivers that need a node DaemonSet

Offen
  • Stimmt etwas nicht?
#3,056 4 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
25/100
Issue-Typ
Feature
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
go, kubernetes
Bereich
backend, devops

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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?

Vorherrschende Sprache
Go
Sterne
215
Forks
86
Ø Merge
1 T. 6 Std.
Gemergte PRs (30 T.)
124

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus operator-framework/operator-controller

Alle Issues in operator-framework/operator-controller

Ähnliche Issues

Weitere Issues zu Go

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.