add temporary testing setup self-hosted

[nandajavarma]

Description

This is a very early stage solution. Currently opened as PR to test another PR in self-hosted setup.

To setup an infrastructure, open a workspace from this PR. Make sure you have access to the core-dev cluster in the present workspace.

• Scenario: You want to test the latest changes in the replicated channel dev-nan which you published to by using the comment werft no-preview publish-to-kots in your PR. You have the license file of your channel locally saved as install/licenses/dev-nan.yaml in your workspace(note that the name of the license file should be same as the channel name, and you don't have to push this change). - If you are testing this PR of mine
  , this step is already done for you. The license file is a part of this PR.

Run the following command:

werft run github -s install/licenses/dev-nan.yaml -j .werft/k3s-installer-tests.yaml -a destroy=false -a channel=dev-nan

Wait for the werft job to finish. You can go to the werft page, you will find a phase called get-results which would have logged the URL in which your preview env is deployed to and the contents of kubeconfig file. You can find an example of this run: https://werft.gitpod-dev.com/job/gitpod-custom-nvn-tmp-test.6

Please copy and paste that to a file in the aforementioned workspace. Run the following commands:

export KUBECONFIG=/path/to/the/new/file
curl https://kots.io/install | bash
kubectl kots -n gitpod admin-console

You will see the running kots UI in port 8800. Password is gitpod.

P. S. your setup will be deleted after two hours of initiation. We are working on a cleaner cleanup policy here.

Related Issue(s)

Fixes #

How to test

Release Notes

Documentation

[roboquat]

@nandajavarma: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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.

[werft-gitpod-dev-com]

started the job as gitpod-build-nvn-tmp-test.3 because the annotations in the pull request description changed
(with .werft/ from main)

[werft-gitpod-dev-com]

started the job as gitpod-build-nvn-tmp-test.5 because the annotations in the pull request description changed
(with .werft/ from main)

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.