Skip to content

Pull requests: openshift/csi-operator

New pull request New
16 Open 327 Closed
16 Open 327 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Reviews
Filter by reviews
No reviews Review required Approved review Changes requested
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Pull requests list

STOR-2263: Enable csi resize and inline volume support for smb csi driver jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#358 opened Feb 18, 2025 by Phaow Loading…
@mpatlasov @rhrmo
6
OCPBUGS-41827: update injector to use a secret rather than an environment variable jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#357 opened Feb 7, 2025 by sunzhaohua2 Loading…
5
[release-4.18] OCPBUGS-49843: Support HCP labels approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
#356 opened Feb 4, 2025 by muraee Loading…
@jsafrane @chao007
@duanwei33 @ropatil010 @Phaow @radeore
16
NO-JIRA: Fixed typo in README.md approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.
#348 opened Dec 16, 2024 by Hupra Loading…
@pierreprinetti
10
OSASINFRA-3652: openstack-cinder: Use new --with-topology flag do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#345 opened Dec 10, 2024 by stephenfin • Draft
4
OSASINFRA-3683: openstack-manila: Remove --nodeid parameter do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#344 opened Dec 9, 2024 by stephenfin • Draft
5
NO-JIRA: Move to 4.19 on go1.23 jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#333 opened Nov 28, 2024 by joepvd Loading…
8
NO-JIRA: build only needed cmd in container image approved Indicates a PR has been approved by an approver from all required OWNERS files. docs-approved Signifies that Docs has signed off on this PR jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR
#329 opened Nov 22, 2024 by sanchezl Loading…
@jsafrane
7
TlS 1.3 support do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#328 opened Nov 22, 2024 by sanchezl • Draft
5
CFE-1132: EFS Access Point Tags Update DAY2 jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#313 opened Nov 4, 2024 by anirudhAgniRedhat Loading…
26
NO-JIRA: Centralize injection of hosted-kubeconfig volume approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
#311 opened Oct 25, 2024 by stephenfin Loading…
@jsafrane
9
NO-JIRA: Remove inject-proxy annotations for aws-ebs, aws-efs node daemonsets approved Indicates a PR has been approved by an approver from all required OWNERS files. docs-approved Signifies that Docs has signed off on this PR jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR
#308 opened Oct 23, 2024 by stephenfin Loading…
@jsafrane
11
NO-JIRA: azure-disk, azure-file sync code de-duplication approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
#303 opened Oct 18, 2024 by stephenfin Loading…
@jsafrane
7
CFE-1131: AWS Tags DAY2 Update approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
#297 opened Oct 11, 2024 by anirudhAgniRedhat Loading…
@dobsonj
106
WIP: STOR-1140: Use kubeconfig specific for AWS-EBS CSI diriver controller approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#284 opened Sep 24, 2024 by mpatlasov Loading…
3
{WIP} Give node permissions secret and remove cloud-config approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#183 opened Feb 28, 2024 by gnufied Loading…
4
ProTip! Updated in the last three days: updated:>2025-02-15.