Skip to content

OPRUN-4610: Revert lifecycle server changes#1300

Merged
openshift-merge-bot[bot] merged 3 commits into
openshift:mainfrom
perdasilva:remove-lifecycle-server
May 20, 2026
Merged

OPRUN-4610: Revert lifecycle server changes#1300
openshift-merge-bot[bot] merged 3 commits into
openshift:mainfrom
perdasilva:remove-lifecycle-server

Conversation

@perdasilva
Copy link
Copy Markdown
Contributor

@perdasilva perdasilva commented May 19, 2026

Since we've decided on a different architecture for providing operator lifecycle metadata, this PR reverts the changes made to pave the way for the old architecture (lifecycle-controller + lifecycle-server).

Summary by CodeRabbit

Release Notes

  • Chores
    • Removed the lifecycle-server component and its HTTP API endpoints
    • Removed authentication/authorization middleware for lifecycle requests
    • Updated Docker image build configuration to exclude the removed component
    • Removed associated test coverage

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

@perdasilva: This pull request explicitly references no jira issue.

Details

In response to this:

Since we've decided on a different architecture for providing operator lifecycle metadata, this PR reverts the changes made to pave the way for the old architecture (lifecycle-controller + lifecycle-server).

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.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 19, 2026

Walkthrough

This PR removes the lifecycle-server CLI tool entirely: build rules and test targets are deleted from the Makefile, the CLI entrypoint is removed, direct dependencies used only by that tool are converted to indirect requirements in go.mod, and the binary is removed from the container image.

Changes

Lifecycle Server Component Removal

Layer / File(s) Summary
Build system cleanup
Makefile
Lifecycle-server is removed from the build system: LIFECYCLE_SERVER_CMD variable is deleted, the build/olm target recipe no longer invokes the lifecycle-server build, the $(LIFECYCLE_SERVER_CMD): FORCE build rule is deleted, and the unit/lifecycle-server test target is removed.
CLI entry point removal
cmd/lifecycle-server/main.go
The lifecycle-server CLI entrypoint is deleted, removing the Cobra root command initialization and registration logic.
Dependency graph adjustment
go.mod
Direct dependencies (library-go, golang.org/x/sync, k8s.io/apiserver, k8s.io/klog/v2) are moved to indirect requirements, reflecting the removal of the lifecycle-server tool that was their primary consumer.
Container image cleanup
operator-lifecycle-manager.Dockerfile
The COPY instruction that adds the lifecycle-server binary to the runtime image is removed.

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 12
✅ Passed checks (12 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed PR removes code and doesn't add new Ginkgo tests. Repository uses Go testing.T, not Ginkgo. Check is not applicable to this revert PR.
Test Structure And Quality ✅ Passed The custom check assesses Ginkgo test code quality. This PR deletes lifecycle-server test files but adds no new/modified test code. The check is not applicable.
Microshift Test Compatibility ✅ Passed This is a revert PR that removes code (lifecycle-server), not adds new tests. The custom check applies to NEW Ginkgo tests only. No new tests are added, so check is not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed This PR is a revert that removes lifecycle-server code and tests. No new Ginkgo e2e tests are added. The custom check only applies when new tests are added, so it is not applicable here.
Topology-Aware Scheduling Compatibility ✅ Passed This PR removes lifecycle-server code, not adding or modifying it. The check applies to new/modified deployment manifests, operator code, or controllers. This revert PR is not applicable.
Ote Binary Stdout Contract ✅ Passed PR removes lifecycle-server binary and all code entirely. No new process-level code with stdout violations introduced. Build and Docker configurations updated accordingly.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed This PR removes lifecycle-server code and unit tests (not e2e tests). No new Ginkgo e2e tests are being added, so the IPv6 and disconnected network compatibility check is not applicable.
Title check ✅ Passed The title clearly summarizes the main change: reverting lifecycle server changes. It directly reflects the substantial codebase modifications removing lifecycle-server components.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci Bot requested review from anik120 and rashmigottipati May 19, 2026 07:46
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 19, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: perdasilva

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-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 19, 2026
@perdasilva perdasilva force-pushed the remove-lifecycle-server branch from d899376 to f8e7bef Compare May 19, 2026 07:48
…ize-upstream"

This reverts commit 3da12b3, reversing
changes made to 9941db6.
@perdasilva perdasilva force-pushed the remove-lifecycle-server branch from f8e7bef to 4d96680 Compare May 19, 2026 07:52
@perdasilva perdasilva changed the title NO-ISSUE: Revert lifecycle server changes OPRUN-4610: Revert lifecycle server changes May 19, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented May 19, 2026

@perdasilva: This pull request references OPRUN-4610 which is a valid jira issue.

Details

In response to this:

Since we've decided on a different architecture for providing operator lifecycle metadata, this PR reverts the changes made to pave the way for the old architecture (lifecycle-controller + lifecycle-server).

Summary by CodeRabbit

Release Notes

  • Chores
  • Removed the lifecycle-server component and its HTTP API endpoints
  • Removed authentication/authorization middleware for lifecycle requests
  • Updated Docker image build configuration to exclude the removed component
  • Removed associated test coverage

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.

Copy link
Copy Markdown
Member

@fgiudici fgiudici left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 19, 2026
@perdasilva
Copy link
Copy Markdown
Contributor Author

/retest

@tmshort
Copy link
Copy Markdown
Contributor

tmshort commented May 19, 2026

/verified by tmshort

It removes the old implementation

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label May 19, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@tmshort: This PR has been marked as verified by tmshort.

Details

In response to this:

/verified by tmshort

It removes the old implementation

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-merge-bot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD f4b8ef2 and 2 for PR HEAD 4d96680 in total

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 20, 2026

@perdasilva: 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.

@openshift-merge-bot openshift-merge-bot Bot merged commit b379d0c into openshift:main May 20, 2026
17 checks passed
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. 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.

4 participants