Skip to content

Pull requests: openshift/cluster-etcd-operator

New pull request New
24 Open 1,450 Closed
24 Open 1,450 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
Assigned to nobody Loading
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Pull requests list

update cert injection annotations to beta needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test.
#1551 opened Feb 10, 2026 by lance5890 Loading…
4
OCPBUGS-67421: Update logrus to 1.9.3 to address CVE-2025-65637 jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#1550 opened Feb 5, 2026 by nindsimonv Loading…
10
OCPBUGS-67597: Update logrus to 1.9.3 to address CVE-2025-65637 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. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-moderate Referenced Jira bug's severity is moderate 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. verified Signifies that the PR passed pre-merge verification criteria
#1549 opened Feb 5, 2026 by nindsimonv Loading…
@dusk125
18
OCPBUGS-67770: Update logrus to 1.9.3 to address CVE-2025-65637 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. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-moderate Referenced Jira bug's severity is moderate 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. verified Signifies that the PR passed pre-merge verification criteria
#1548 opened Feb 5, 2026 by nindsimonv Loading…
@dusk125
14
OCPBUGS-67931: Update logrus to 1.9.3 to address CVE-2025-65637 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. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-moderate Referenced Jira bug's severity is moderate 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.
#1547 opened Feb 5, 2026 by nindsimonv Loading…
@dusk125
7
[release-4.18] OCPBUGS-76284: Add priority field to prevent early shutdown 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. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. 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. verified Signifies that the PR passed pre-merge verification criteria
#1545 opened Feb 5, 2026 by sanchezl Loading…
@hasbro17
17
CNTRLPLANE-2683: Add network policies to openshift-etcd pods 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.
#1544 opened Feb 5, 2026 by dusk125 Loading…
6
ETCD-557:Add e2e Network policy test cases jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#1543 opened Feb 5, 2026 by gangwgr Loading…
34
OCPBUGS-74151: Wait for revision stability before removing etcd members 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-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.
#1540 opened Feb 1, 2026 by hasbro17 Loading…
@tjungblu
33
CNTRLPLANE-2663: Add network policies 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. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.
#1538 opened Jan 30, 2026 by dusk125 Loading…
12
[release-4.21] OCPBUGS-74641: split grpc requests slow into read/write alerts jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#1537 opened Jan 29, 2026 by openshift-cherrypick-robot Loading…
@tjungblu
5
MON-4484: chore: add permissions on endpointslice to Prometheus Role and use serviceDiscoveryRole: EndpointSlice in ServiceMonitors jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#1536 opened Jan 28, 2026 by machine424 Loading…
7
DNM - Debugging CPMS failure do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.
#1530 opened Jan 19, 2026 by JoelSpeed • Draft
3
DNM - Testing do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.
#1529 opened Jan 16, 2026 by JoelSpeed • Draft
2
OCPBUGS-70050: Updating cluster-etcd-operator-container image to be consistent with ART for 4.22 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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. 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. verified Signifies that the PR passed pre-merge verification criteria
#1525 opened Dec 20, 2025 by openshift-bot Loading…
@hasbro17 @tjungblu
17
OCPBUGS-66334: remove version check from guard precheck approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/invalid-bug Indicates that a referenced Jira bug is invalid 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.
#1520 opened Dec 4, 2025 by tjungblu Loading…
@dusk125
7
OCPBUGS-64729: Update etcd alerts to match observed real world data acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. 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.
#1511 opened Nov 6, 2025 by dgoodwin Loading…
@hasbro17
24
change restore pod readinessProbe to 9980 approved Indicates a PR has been approved by an approver from all required OWNERS files. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.
#1509 opened Nov 4, 2025 by lance5890 Loading…
13
dedicated event etcd draft PoC for ShiftWeek 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. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
#1505 opened Oct 27, 2025 by tjungblu • Draft
6
NO-JIRA: add recommended etcd threshold for alerts 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. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
#1495 opened Oct 9, 2025 by tjungblu Loading…
12
[release-4.18] OCPBUGS-62698: add individual context to the health check 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. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
#1490 opened Oct 3, 2025 by openshift-cherrypick-robot Loading…
@tjungblu
12
[WIP] OCPEDGE-2176: two new disruptive fencing validation jobs for TNF 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. lgtm Indicates that a PR is ready to be merged. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#1486 opened Sep 17, 2025 by Neilhamza Loading…
@clobrano
41
NO-JIRA: util and docs for quota testing 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. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
#1470 opened Aug 18, 2025 by tjungblu • Draft
7
OCPBUGS-42810: actively move bootstrap member lead 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-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. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#1369 opened Nov 19, 2024 by tjungblu Loading…
@dusk125
69
ProTip! Mix and match filters to narrow down what you’re looking for.