Skip to content

OSDOCS-17826 [NETOBSERV] New Feature: Per-tenant configuration#104782

Merged
bergerhoffer merged 1 commit intoopenshift:no-1.11from
gwynnemonahan:OSDOCS-17826
Feb 17, 2026
Merged

OSDOCS-17826 [NETOBSERV] New Feature: Per-tenant configuration#104782
bergerhoffer merged 1 commit intoopenshift:no-1.11from
gwynnemonahan:OSDOCS-17826

Conversation

@gwynnemonahan
Copy link
Contributor

@gwynnemonahan gwynnemonahan commented Jan 14, 2026

OSDOCS-17826 [NETOBSERV] New Feature: Per-tenant configuration

Version(s):
Merge to only the no-1.11 branch - no cherrypicks are required.
I will open one PR against main to incorporate all of the <no-.11> content just before its GA.

Issue:
https://issues.redhat.com/browse/OSDOCS-17826

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

  • Per OCP Core, do not make DITA updates to automatically generated docs until further notice.
  • Except for API reference, Vale rules pass.

@openshift-ci openshift-ci bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jan 14, 2026
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Jan 14, 2026

@gwynnemonahan
Copy link
Contributor Author

/retest

1 similar comment
@gwynnemonahan
Copy link
Contributor Author

/retest

@openshift-ci openshift-ci bot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 15, 2026
@openshift-ci openshift-ci bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Jan 15, 2026
@gwynnemonahan
Copy link
Contributor Author

01/15/2026 PM:

no-1.11 rebased against main
PR rebased against no-1.11

@gwynnemonahan
Copy link
Contributor Author

Rebased 01/23/2026 AM

Copy link

@jotak jotak left a comment

Choose a reason for hiding this comment

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

Nice work!
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 12, 2026
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 12, 2026
@openshift-ci
Copy link

openshift-ci bot commented Feb 12, 2026

New changes are detected. LGTM label has been removed.

@gwynnemonahan
Copy link
Contributor Author

/label merge-review-needed

@openshift-ci openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Feb 12, 2026
@gwynnemonahan
Copy link
Contributor Author

Rebased against no-1.11 02/16/2026 AM

@gwynnemonahan
Copy link
Contributor Author

/retest

@bergerhoffer
Copy link
Contributor

/label merge-review-in-progress

@openshift-ci openshift-ci bot added the merge-review-in-progress Signifies that the merge review team is reviewing this PR label Feb 17, 2026
Copy link
Contributor

@bergerhoffer bergerhoffer left a comment

Choose a reason for hiding this comment

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

Nice job, just a few comments. I'm borderline on whether to request any of these fixes before merging, so I'll ping you on Slack and see what you want to do before merging.

@gwynnemonahan
Copy link
Contributor Author

Rebased against no-1.11 02/17/2026 AM.

@openshift-ci
Copy link

openshift-ci bot commented Feb 17, 2026

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

@bergerhoffer
Copy link
Contributor

LGTM now ty!

@bergerhoffer bergerhoffer merged commit e366714 into openshift:no-1.11 Feb 17, 2026
2 checks passed
@kalexand-rh
Copy link
Contributor

/cherrypick no-1.11

@openshift-cherrypick-robot

@kalexand-rh: I cannot cherry-pick the present PR on top of its base branch (no-1.11).

Details

In response to this:

/cherrypick no-1.11

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.

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

Labels

merge-review-in-progress Signifies that the merge review team is reviewing this PR merge-review-needed Signifies that the merge review team needs to review this PR qe-approved Signifies that QE has signed off on this PR size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants