Skip to content

Avoid generic name for Cluster wide resources #395

@Jean-Daniel

Description

@Jean-Daniel

The deployment manifest (v0.5) creates cluster wide resources (ClusterRole, ClusterRoleBinding, …) with generic name like metrics-auth and metrics-reader.

Using generic name for cluster wide resource is discouraged as they may conflict with other components deployed in the same cluster.

These resources name should probably be prefixed by barman-plugin- to avoid conflict with other cluster components.

Even the ClusterRole like objectstore-viewer-role should make it clear they are barman-objectstore and not related to any other objectstore (like CephObjectStore).

And even for the namespaced resources (leader-election-rolebinding, selfsigned-issuer) it may be an issue. If you try to deploy 2 CNPG plugins that both require specific leader-election-rolebinding, they may clash.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions