Skip to content

[release-4.18] USHIFT-6216: Remove flannel and kube-proxy from MicroShift downstream repo#5609

Merged
openshift-merge-bot[bot] merged 4 commits intoopenshift:release-4.18from
ggiguash:flannel-remove-downstream-418
Oct 14, 2025
Merged

[release-4.18] USHIFT-6216: Remove flannel and kube-proxy from MicroShift downstream repo#5609
openshift-merge-bot[bot] merged 4 commits intoopenshift:release-4.18from
ggiguash:flannel-remove-downstream-418

Conversation

@ggiguash
Copy link
Copy Markdown
Contributor

As a follow-up for microshift-io/microshift#76 PR, we can now remove the duplication from the downstream repo.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 14, 2025
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Oct 14, 2025

@ggiguash: This pull request references USHIFT-6216 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.z" version, but no target version was set.

Details

In response to this:

As a follow-up for microshift-io/microshift#76 PR, we can now remove the duplication from the downstream repo.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot requested review from pmtk and vanhalenar October 14, 2025 08:46
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 14, 2025
@ggiguash
Copy link
Copy Markdown
Contributor Author

/test e2e-aws-tests

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Oct 14, 2025

@ggiguash: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@ggiguash
Copy link
Copy Markdown
Contributor Author

/label backport-risk-assessed
/label jira/valid-bug
/verified by ci

@openshift-ci openshift-ci Bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Oct 14, 2025
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 14, 2025
@openshift-ci-robot
Copy link
Copy Markdown

@ggiguash: This PR has been marked as verified by ci.

Details

In response to this:

/label backport-risk-assessed
/label jira/valid-bug
/verified by ci

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@pmtk
Copy link
Copy Markdown
Member

pmtk commented Oct 14, 2025

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Oct 14, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Oct 14, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, pmtk

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot Bot merged commit 6cf5f36 into openshift:release-4.18 Oct 14, 2025
21 checks passed
@ggiguash ggiguash deleted the flannel-remove-downstream-418 branch October 20, 2025 06:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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. 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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants