Skip to content

Conversation

@Alcamech
Copy link

@Alcamech Alcamech commented Jan 23, 2026

What type of PR is this?

Documentation

What this PR does / why we need it?

Updates the local development.md documentation to:

  • Add step to delete the leader lease when scaling down the deployed MUO
  • Make the LOCAL mode ConfigMap step mandatory (not optional) for local development
  • Add UpgradeConfigSyncFailureOver4HrSRE to ignoredCriticals in the test ConfigMap (this al
    ert fires when the deployed MUO is scaled down)
  • Clarify that the operator must run as the MUO service account to bypass webhooks
  • Add OSDK_FORCE_RUN_MODE=local requirement for routes (both env vars are needed)
  • Fix inconsistent section header levels

Which Jira/Github issue(s) this PR fixes?

Fixes OCM-19812

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

openshift-ci-robot commented Jan 23, 2026

@Alcamech: This pull request references OCM-19812 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.22.0" version, but no target version was set.

Details

In response to this:

What type of PR is this?

Documentation

What this PR does / why we need it?

Updates the local development.md documentation to:

  • Add step to delete the leader lease when scaling down the deployed MUO
  • Make the LOCAL mode ConfigMap step mandatory (not optional) for local development
  • Add UpgradeConfigSyncFailureOver4HrSRE to ignoredCriticals in the test ConfigMap (this al
    ert fires when the deployed MUO is scaled down)
  • Clarify that the operator must run as the MUO service account to bypass webhooks
  • Add OSDK_FORCE_RUN_MODE=local requirement for routes (both env vars are needed)
  • Fix inconsistent section header levels

Which Jira/Github issue(s) this PR fixes?

Fixes OCM-19812

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 devppratik and ravitri January 23, 2026 19:54
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 23, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

The full list of commands accepted by this bot can be found 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
Copy link
Contributor

openshift-ci bot commented Jan 23, 2026

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

@Alcamech Alcamech mentioned this pull request Jan 26, 2026
2 tasks
@rawsyntax
Copy link
Member

LGTM

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