🌱 Generate vm-operator YAML instead of downloading it from GCS

[sbueringer]

Signed-off-by: Stefan Büringer [email protected]

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

[sbueringer]

/hold

let's see if this actually works

[sbueringer]

Not sure why we are going so far up that we have to go back into the CAPV repo dir, but I copied this from vc-sim.

One reason could be that this config file can even be used from 4 levels deep in another repo (?)

[fabriziopandini]

I think this is because paths are relative to the test file.
if this is true, probably we are going up too much, but this seems a generalized smell all around this file

[sbueringer]

Yup, agree :)

[sbueringer]

/hold cancel

[sbueringer]

/assign @fabriziopandini @chrischdi

I would cherry-pick this after this PR merges to all relevant branches and then cleanup the files in the bucket.

[chrischdi]

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: f837229db6c88ac8bd1102fe60bb9bc45677a4e6

[sbueringer]

/ok-to-test

[sbueringer]

/hold

so Fabrizio can take a look if he wants

[fabriziopandini]

/lgtm
/approve

I would suggest to unhold only after the release
Also, are you planning to cleanup the published manifests as soon as they are not necessary anymore?

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chrischdi, fabriziopandini

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 [chrischdi,fabriziopandini]

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

[sbueringer]

/lgtm /approve

I would suggest to unhold only after the release

Sounds good

Also, are you planning to cleanup the published manifests as soon as they are not necessary anymore?

Yup :) #2931 (comment)

[sbueringer]

/hold cancel

[sbueringer]

Looks like we only need it in release-1.10. release-1.9 doesn't seem to have the vm-operator yet

Will wait with merging the cherry-pick until after the release tomorrow

[sbueringer]

/cherry-pick release-1.10

[k8s-infra-cherrypick-robot]

@sbueringer: new pull request created: #2943

In response to this:

/cherry-pick release-1.10

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.