Aggregate Barman Cloud Plugin's ClusterRole to Kubernetes default user-facing roles

Open Beginner friendly
#816 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
helm, kubernetes
Domain
authorization, devops

Research direction

Start with values.yaml and the Barman Cloud Plugin's ClusterRole template to see how RBAC options are defined and rendered. Add the requested aggregation option and verify that the rendered ClusterRole carries the view, edit, and admin aggregation labels so users can manage ObjectStore resources.

Written by the indexing model from the issue text.

Description

chart( plugin-barman-cloud )

The Barman Cloud Plugin does not allow the aggregation labels, as does the CloudNativePG operator. I would expect to see the option rbac.aggregateClusterRoles in values.yaml and the labels rbac.authorization.k8s.io/aggregate-to-view, rbac.authorization.k8s.io/aggregate-to-edit, and rbac.authorization.k8s.io/aggregate-to-admin to be set for the Barman Cloud Plugin's ClusterRole so that a Kubernetes admin can manage ObjectStore resources.

Dominant language
Go Template
Stars
622
Forks
264
Avg merge
6d 16h
Merged PRs (30d)
8

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudnative-pg/charts

All issues in cloudnative-pg/charts

Similar issues

More Security issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.