Netobserv clusterbot

[memodi]

NETOBSERV-872 First version prow config for network observability operator intended to be used with cluster bot.

[openshift-ci-robot]

@memodi: no rehearsable tests are affected by this change

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: memodi

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

The pull request process is described 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

[memodi]

/cc @jotak - could you PTAL and review? I am not sure if I have everything correct in this config.

[jotak]

typo here

[jotak]

From the CI errors it seems you need to run make jobs

[jotak]

have you been able to test the build or not?
I'm not sure how these configs/steps all play together, but if the build command is make build (as shown L14) and this dockerfile uses that build output, then the source should be something like ./bin/manager

In case it is useful, here's how the build definition was done previously: https://github.com/openshift/release/pull/35766/files#diff-df4f4f7896d9a6f03e1d041f559f8d1b076995b41b84ff5853eb619950b53da3L29-L32 (see file ci-operator/config/netobserv/network-observability-operator/netobserv-network-observability-operator-main.yaml)
As you can see we also had to override a couple of go ENV variables, but maybe this isn't useful here, as the base image used for building is different.

[memodi]

have you been able to test the build or not?

No, I have not yet, wanted to create this first draft of config and have it pass by you to resolve any evident issues as you noted.

I'm not sure how these configs/steps all play together

I can't say I know them well either, trying to go through the documentation and use references from other operator configs.

as the base image used for building is different.

do you mean 9.1 in Dockerfile vs 9 in this config?

added feedback in commit: 1284cbd

[openshift-ci]

@memodi: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/prow-config-filenames	7178ddf	link	true	/test prow-config-filenames
ci/prow/check-gh-automation	7178ddf	link	true	/test check-gh-automation
ci/prow/config	7178ddf	link	true	/test config
ci/prow/correctly-sharded-config	7178ddf	link	true	/test correctly-sharded-config
ci/prow/owners	7178ddf	link	true	/test owners

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/test-infra repository. I understand the commands that are listed here.

[memodi]

/hold
@jotak - looks like I need to start over again since the PR you linked removed support for Prow by initializing new-repo, I would have revert my earlier commits and start at make new-repo. In the mean could you add robots and GH app into repos under netobserv org.

[jotak]

our github repos already have the openshift bots enabled

[openshift-bot]

Issues in openshift/release go stale after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 15d 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-bot]

Stale issue in openshift/release rot after 15d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 15d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle rotten
/remove-lifecycle stale