-
Notifications
You must be signed in to change notification settings - Fork 214
Pull requests: openshift/machine-api-operator
Author
Label
Projects
Milestones
Reviews
Assignee
Sort
Pull requests list
SPLAT-2118: Update tests-extensions to pick up new vendor filtering
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.
#1351
opened Apr 1, 2025 by
vr4manta
Loading…
SPLAT-2051: implement e2e tests for vSphere multi network
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.
#1347
opened Mar 14, 2025 by
rvanderp3
Loading…
[release-4.17] OCPBUGS-53036,OCPBUGS-53037: Updates GCP credentials request
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/invalid-bug
Indicates that a referenced Jira bug is invalid for the branch this PR is targeting.
jira/severity-important
Referenced Jira bug's severity is important 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.
#1345
opened Mar 12, 2025 by
openshift-cherrypick-robot
Loading…
AUTH-482: Move required-scc annotation from deployment to pod
jira/valid-reference
Indicates that this PR references a valid Jira ticket of any type.
needs-ok-to-test
Indicates a PR that requires an org member to verify it is safe to test.
#1343
opened Mar 11, 2025 by
jacobsee
Loading…
[release-4.18] AUTH-482: set required-scc for openshift workloads
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
#1311
opened Dec 6, 2024 by
openshift-cherrypick-robot
Loading…
Bump client-go to use protobuf
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.
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
ProTip!
Type g p on any issue or pull request to go back to the pull request listing page.