-
Notifications
You must be signed in to change notification settings - Fork 215
Pull requests: openshift/managed-cluster-config
Author
Label
Projects
Milestones
Reviews
Assignee
Sort
Pull requests list
allowing HCP settings to FedRAMP
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
lgtm
Indicates that a PR is ready to be merged.
#2384
opened Mar 17, 2025 by
theautoroboto
Loading…
3 tasks
[OSD 28223] Handle worker (node filesystem) alert using ocm-agent
#2380
opened Mar 13, 2025 by
a7vicky
Loading…
3 tasks
OSD-27692: New crontab to clean backplane remediation RBACs in case the remediation was not properly deleted
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.
#2368
opened Feb 27, 2025 by
Nikokolas3270
Loading…
1 of 3 tasks
ROX-27758: Allow ACS team read secured cluster namespace secrets
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.
#2358
opened Feb 10, 2025 by
kurlov
Loading…
3 tasks
[OSD-28131] OBO CSV Cleanup CronJob for Hypershift SC clusters
#2356
opened Feb 4, 2025 by
Nikokolas3270
Loading…
1 of 3 tasks
Init NOO SlectorSyncSet for MCs
do-not-merge/hold
Indicates that a PR should not merge because someone has issued a /hold command.
#2337
opened Jan 24, 2025 by
jimdaga
Loading…
[OCM-13425] Create draft work to adapt HCP STS policies to FedRAMP
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
#2317
opened Jan 10, 2025 by
BraeTroutman
•
Draft
3 tasks
[OCM-12870] define management cluster cronjob to perform olm dance
lgtm
Indicates that a PR is ready to be merged.
#2294
opened Dec 6, 2024 by
cdoan1
Loading…
3 tasks
Sync OWNERS_ALIASES with boilerplate
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
lgtm
Indicates that a PR is ready to be merged.
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
tide/merge-method-squash
Denotes a PR that should be squashed by tide when it merges.
#2290
opened Dec 4, 2024 by
abyrne55
Loading…
Make sure dns-default pods run on all nodes for 4.18+ clusters
do-not-merge/hold
Indicates that a PR should not merge because someone has issued a /hold command.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
#2286
opened Dec 3, 2024 by
mmazur
Loading…
1 of 3 tasks
ProTip!
Follow long discussions with comments:>50.