Skip to content

[release-4.19] NETOBSERV-2296: add missing annotations on netobserv quickstart - #1094

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.19from
openshift-cherrypick-robot:cherry-pick-1080-to-release-4.19
Aug 10, 2026
Merged

[release-4.19] NETOBSERV-2296: add missing annotations on netobserv quickstart#1094
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.19from
openshift-cherrypick-robot:cherry-pick-1080-to-release-4.19

Conversation

@openshift-cherrypick-robot

Copy link
Copy Markdown

This is an automated cherry-pick of #1080

/assign jpinsonneau

@openshift-ci-robot

openshift-ci-robot commented Jan 14, 2026

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: NETOBSERV-2296

Details

In response to this:

This is an automated cherry-pick of #1080

/assign jpinsonneau

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.

@jpinsonneau

Copy link
Copy Markdown
Contributor

/refresh

@jpinsonneau

Copy link
Copy Markdown
Contributor

/retest

@christoph-jerolimov

Copy link
Copy Markdown
Member

/uncc
/cc @jhadvig

@openshift-ci
openshift-ci Bot requested review from jhadvig and removed request for christoph-jerolimov January 28, 2026 06:32
@openshift-bot

Copy link
Copy Markdown
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci Bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 28, 2026
@jpinsonneau

Copy link
Copy Markdown
Contributor

/lifecycle frozen

@openshift-ci

openshift-ci Bot commented May 11, 2026

Copy link
Copy Markdown
Contributor

@jpinsonneau: The lifecycle/frozen label cannot be applied to Pull Requests.

Details

In response to this:

/lifecycle frozen

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.

@jpinsonneau

Copy link
Copy Markdown
Contributor

/remove-lifecycle stale

@openshift-ci openshift-ci Bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 11, 2026
@jhadvig

jhadvig commented Aug 10, 2026

Copy link
Copy Markdown
Member

/label backport-risk-assessed
/lgtm
/approve

@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Aug 10, 2026
@jhadvig jhadvig added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Aug 10, 2026
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 10, 2026
@openshift-ci

openshift-ci Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jhadvig, openshift-cherrypick-robot

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 Aug 10, 2026
@jhadvig

jhadvig commented Aug 10, 2026

Copy link
Copy Markdown
Member

/verified by @jhadvig

@jhadvig jhadvig added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 10, 2026
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Aug 10, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

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

Details

In response to this:

/verified by @jhadvig

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 0eb1db3 and 2 for PR HEAD 9084bad in total

@jhadvig

jhadvig commented Aug 10, 2026

Copy link
Copy Markdown
Member

/override ci/prow/e2e-aws-console

@openshift-ci

openshift-ci Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

@jhadvig: Overrode contexts on behalf of jhadvig: ci/prow/e2e-aws-console

Details

In response to this:

/override ci/prow/e2e-aws-console

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.

@openshift-merge-bot
openshift-merge-bot Bot merged commit 49cae5e into openshift:release-4.19 Aug 10, 2026
12 checks passed
@jhadvig

jhadvig commented Aug 10, 2026

Copy link
Copy Markdown
Member

/override ci/prow/e2e-aws-console

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.

7 participants