Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

helm: Always add nodes read permissions to provisioner ClusterRole (backport #4798) #4810

Merged
merged 1 commit into from
Aug 27, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Aug 27, 2024

Describe what this PR does

--immediate-topology=false not stopping registry.k8s.io/sig-storage/csi-provisioner from attemps list nodes, like --feature-gates=Topology=false do, because of errors in csi-provisioner container will paper and it will not work. More details are described here: #4790 (comment)

This PR adds permissions to allow csi-provisioner list nodes and csinodes even when .Values.topology.domainLabels is [] which fixes mentioned above issue.

Is there anything that requires special attention

Do you have any questions?
No

Is the change backward compatible?
Yes

Are there concerns around backward compatibility?
No

Provide any external context for the change, if any.
N/A

Related issues

Mention any github issues relevant to this PR. Adding below line
will help to auto close the issue once the PR is merged.

properly fixes: #4777

Future concerns

List items that are not part of the PR and do not impact it's
functionality, but are work items that can be taken up subsequently.

Checklist:

  • Commit Message Formatting: Commit titles and messages follow
    guidelines in the developer
    guide
    .
  • Reviewed the developer guide on Submitting a Pull
    Request
  • Pending release
    notes

    updated with breaking and/or notable changes for the next major release.
  • Documentation has been updated, if necessary.
  • Unit tests have been added, if necessary.
  • Integration tests have been added, if necessary.

Show available bot commands

These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:

  • /retest ci/centos/<job-name>: retest the <job-name> after unrelated
    failure (please report the failure too!)

This is an automatic backport of pull request #4798 done by [Mergify](https://mergify.com).

Signed-off-by: Dmytro Alieksieiev <1865999+dragoangel@users.noreply.github.com>
(cherry picked from commit 601c40b)
@mergify mergify bot added ok-to-test Label to trigger E2E tests component/deployment Helm chart, kubernetes templates and configuration Issues/PRs labels Aug 27, 2024
@ceph-csi-bot
Copy link
Collaborator

/test ci/centos/upgrade-tests-cephfs

@ceph-csi-bot
Copy link
Collaborator

/test ci/centos/upgrade-tests-rbd

@ceph-csi-bot
Copy link
Collaborator

/test ci/centos/k8s-e2e-external-storage/1.29

@ceph-csi-bot
Copy link
Collaborator

/test ci/centos/k8s-e2e-external-storage/1.30

@ceph-csi-bot
Copy link
Collaborator

/test ci/centos/mini-e2e-helm/k8s-1.29

@ceph-csi-bot
Copy link
Collaborator

/test ci/centos/mini-e2e-helm/k8s-1.30

@ceph-csi-bot
Copy link
Collaborator

/test ci/centos/mini-e2e/k8s-1.29

@ceph-csi-bot
Copy link
Collaborator

/test ci/centos/mini-e2e/k8s-1.30

@ceph-csi-bot
Copy link
Collaborator

/test ci/centos/k8s-e2e-external-storage/1.31

@ceph-csi-bot
Copy link
Collaborator

/test ci/centos/mini-e2e-helm/k8s-1.31

@ceph-csi-bot
Copy link
Collaborator

/test ci/centos/mini-e2e/k8s-1.31

@ceph-csi-bot ceph-csi-bot removed the ok-to-test Label to trigger E2E tests label Aug 27, 2024
@nixpanic nixpanic requested a review from a team August 27, 2024 11:49
@mergify mergify bot merged commit add317d into release-v3.12 Aug 27, 2024
42 checks passed
@mergify mergify bot deleted the mergify/bp/release-v3.12/pr-4798 branch August 27, 2024 11:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/deployment Helm chart, kubernetes templates and configuration Issues/PRs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants