Skip to content

Issues: openshift/kubernetes

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.

Sign up for GitHub

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

Clear current search query, filters, and sorts
5 Open 1,235 Closed
5 Open 1,235 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
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

[release-4.18] OCPBUGS-56384: Propagate error when creating CustomResourceStorage instead of panicking 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. backports/validated-commits Indicates that all commits come to merged upstream PRs. 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. vendor-update Touching vendor dir or related files
#2303 opened May 16, 2025 by openshift-cherrypick-robot Loading…
@sdodson @bertinatto
@kasturinarra @zhouying7780 @xingxingxia @duanwei33 @wangke19 @gangwgr
11
[release-4.19] OCPBUGS-56082: UPSTREAM: 130047: adjusting loopback certificate validity in kube-apiserver backports/validated-commits Indicates that all commits come to merged upstream PRs. 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. vendor-update Touching vendor dir or related files
#2297 opened May 13, 2025 by openshift-cherrypick-robot Loading…
@vrutkovs @wangke19
16
[release-4.18] OCPBUGS-54724: Fix implementation of ContainsCIDR to allow non-equal addresses approved Indicates a PR has been approved by an approver from all required OWNERS files. backports/validated-commits Indicates that all commits come to merged upstream PRs. 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. vendor-update Touching vendor dir or related files
#2267 opened Apr 8, 2025 by openshift-cherrypick-robot Loading…
@bertinatto @JoelSpeed
6
NO-JIRA: UPSTREAM: Add several request/response headers in audit log entries acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. 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/stale Denotes an issue or PR has remained open with no activity and has become stale. vendor-update Touching vendor dir or related files
#2121 opened Oct 22, 2024 by vrutkovs Loading…
@Elbehery
74
NO-JIRA: detect unused annotation rules approved Indicates a PR has been approved by an approver from all required OWNERS files. backports/validated-commits Indicates that all commits come to merged upstream PRs. 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. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
#2117 opened Oct 18, 2024 by danwinship Loading…
@bertinatto @atiratree
28
ProTip! Type g i on any issue or pull request to go back to the issue listing page.