[release-0.2] Fix: e2e tests

[Danil-Grigorev]

What this PR does / why we need it:
Cherry-pick for #260, #203, #204

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 #

Special notes for your reviewer:

Checklist:

• squashed commits into logical changes
• includes documentation
• adds unit tests
• adds or updates e2e tests

[Danil-Grigorev]

@richardcase @furkatgofurov7 Updated, PTAL again

[furkatgofurov7]

lgtm

[furkatgofurov7]

@Danil-Grigorev just to confirm, have we run e2e tests with these changes?

[Danil-Grigorev]

There are some issues with e2e tests on release-0.2 branch, unrelated to any recently merged change. Docker provider fails to update ProviderID field on the machine. Needs to be looked into, just didn’t find time yet

[furkatgofurov7]

maybe #203 needs to be backported?

[richardcase]

maybe #203 needs to be backported?

Yes i think part or all of it my need backporting.....especially this part

  serverConfig:
    disableComponents:
      kubernetesComponents:
      - cloudController

[Danil-Grigorev]

Tests are passing locally with the change

[furkatgofurov7]

@Danil-Grigorev strange, I noticed space issue in the logs in GHA, maybe we can push #204 also on top of current changes and retest?

[richardcase]

@Danil-Grigorev strange, I noticed space issue in the logs in GHA, maybe we can push #204 also on top of current changes and retest?

We could also move to self hosted runners for the e2e. I started to do this but we need to update the VM image.

[Danil-Grigorev]

Currently tests are already running longer then before. I think this all fixes e2e completely for now (24GB were freed from the logs), PTAL @furkatgofurov7 @richardcase

[furkatgofurov7]

Thanks for working on this @Danil-Grigorev!

/approve