deps: bump RTE version to v0.19.0

[shajmakh]

Update dependency version to consume latest updates.

addresses: #978

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: shajmakh

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:

• OWNERS [shajmakh]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ffromani]

this will require evaluating the transition to the new APIs (e.g. move to config files rather than the bunch of options we are using) and regression testing

example of how it could look like: k8stopologyawareschedwg/resource-topology-exporter#256

[EDIT] we can stay with the old-style commandline option and defer the transition to the configfile, but we should make a plan/timeline for the transition to configfile.

[shajmakh]

/hold
for transitioning to configfiles style

[Tal-or]

this will require evaluating the transition to the new APIs (e.g. move to config files rather than the bunch of options we are using) and regression testing

example of how it could look like: k8stopologyawareschedwg/resource-topology-exporter#256

[EDIT] we can stay with the old-style commandline option and defer the transition to the configfile, but we should make a plan/timeline for the transition to configfile.

I recommend to the take the opportunity of supporting NROP on HCP, and:

1. bump dependent packages (deployer, RTE) to latest and greatest k8s and go versions.
2. rebase kni-scheduler to latest commit on sig-scheduler.
3. bump RTE, deployer and scheduler versions to latest and greatest on NROP.

[shajmakh]

this will require evaluating the transition to the new APIs (e.g. move to config files rather than the bunch of options we are using) and regression testing
example of how it could look like: k8stopologyawareschedwg/resource-topology-exporter#256
[EDIT] we can stay with the old-style commandline option and defer the transition to the configfile, but we should make a plan/timeline for the transition to configfile.

I recommend to the take the opportunity of supporting NROP on HCP, and:

1. bump dependent packages (deployer, RTE) to latest and greatest k8s and go versions.
2. rebase kni-scheduler to latest commit on sig-scheduler.
3. bump RTE, deployer and scheduler versions to latest and greatest on NROP.

Thanks for sharing, good idea indeed for the 4.18 branch. I'll note that to apply it when we branch.

[openshift-ci]

@shajmakh: 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/ci-install-e2e	11af241	link	true	/test ci-install-e2e
ci/prow/ci-e2e	11af241	link	true	/test ci-e2e
ci/prow/images	11af241	link	true	/test images
ci/prow/ci-index-numaresources-operator-bundle	11af241	link	true	/test ci-index-numaresources-operator-bundle
ci/prow/ci-e2e-install-hypershift	11af241	link	true	/test ci-e2e-install-hypershift
ci/prow/ci-index	11af241	link	true	/test ci-index

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.