Skip to content

Conversation

@raptorsun
Copy link
Contributor

@raptorsun raptorsun commented Oct 15, 2025

Description

Type of change

  • Refactor
  • New feature
  • Bug fix
  • CVE fix
  • Optimization
  • Documentation Update
  • Configuration Update
  • Bump-up dependent library

Related Tickets & Documents

Checklist before requesting a review

  • I have performed a self-review of my code.
  • PR has passed all pre-merge test jobs.
  • If it is a core feature, I have added thorough tests.

Testing

  • Please provide detailed steps to perform tests related to this code change.
  • How were the fix/results from this change verified? Please provide relevant screenshots or results.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 15, 2025
@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 15, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 15, 2025

@raptorsun: This pull request references OLS-2101 which is a valid jira issue.

In response to this:

Description

Type of change

  • Refactor
  • New feature
  • Bug fix
  • CVE fix
  • Optimization
  • Documentation Update
  • Configuration Update
  • Bump-up dependent library

Related Tickets & Documents

Checklist before requesting a review

  • I have performed a self-review of my code.
  • PR has passed all pre-merge test jobs.
  • If it is a core feature, I have added thorough tests.

Testing

  • Please provide detailed steps to perform tests related to this code change.
  • How were the fix/results from this change verified? Please provide relevant screenshots or results.

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
Copy link

openshift-ci bot commented Oct 15, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign raptorsun for approval. For more information see the Code Review Process.

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

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

@raptorsun raptorsun changed the title [WIP] OLS-2101: switch to LSC app backend using magic configmap OLS-2101: switch to LSC app backend using magic configmap Oct 17, 2025
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 17, 2025
@raptorsun
Copy link
Contributor Author

/test bundle-e2e-4-19

@raptorsun raptorsun force-pushed the ols-2101 branch 2 times, most recently from c9090c7 to aad9c13 Compare October 21, 2025 12:56
appServerReconcileFunc, err := r.getAppServerReconcileFunction(ctx)
if err != nil {
r.logger.Error(err, "Failed to get app server reconcile function")
r.updateStatusCondition(ctx, olsconfig, typeCRReconciled, false, "Failed to get app server reconcile function", err)
Copy link
Contributor

Choose a reason for hiding this comment

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

do not update status here. Its done later in the code

Copy link
Contributor Author

Choose a reason for hiding this comment

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

right, removing

// todo: implement LSC deployment generation
//
//nolint:unused // Ignore unused lint error before implementation of reconciliation functions
func (r *OLSConfigReconciler) generateLSCDeployment(ctx context.Context, cr *olsv1alpha1.OLSConfig) (*appsv1.Deployment, error) { //lint:ignore U1000 Ignore unused lint error before implementation of reconciliation functions
Copy link
Contributor

Choose a reason for hiding this comment

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

Should this be in deployment file rather than here to make it symmetric to the current one?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

let's put the LSC backend related code in a dedicated file and when we remove the old code in future, we just need to remove the old deployment file and the switch code in the main controller loop.

@raptorsun raptorsun force-pushed the ols-2101 branch 2 times, most recently from b8e175b to b779177 Compare October 27, 2025 15:52
@raptorsun
Copy link
Contributor Author

/test bundle-e2e-4-19

1 similar comment
@raptorsun
Copy link
Contributor Author

/test bundle-e2e-4-19

@openshift-ci
Copy link

openshift-ci bot commented Oct 29, 2025

@raptorsun: all tests passed!

Full PR test history. Your PR dashboard.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants