containerized-data-importer/cluster-sync/external
akalenyu 8b92395ddf
Change the way we fetch latest release from GitHub (#2256)
CI is failing, it looks like gh releases/latest now redirects (302 HTTP).
Also seems like the go to is to use the gh API for this

Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com>
2022-05-03 16:52:04 +02:00
..
resources update kubevirtci with builtin rook/ceph (#1703) 2021-03-17 20:14:50 +01:00
provider.sh Change the way we fetch latest release from GitHub (#2256) 2022-05-03 16:52:04 +02:00
README.md Refactored provider infra structure (#831) 2019-06-13 14:29:42 -04:00

External Kubernetes Provider

This provider works with an existing Kubernetes cluster. You'll want to configure your own Container Image Registry, we tie into the existing Make/Build workflow, but modify things such that:

  1. We build container images and push to the specified registry (instead of registry:5000)
  2. We generate the manifests with the provided DOCKER_PREFIX (uses default port)
  3. Uses your configured kubectl and deploys your build to the existing cluster

Building images and pushing to your registry

export DOCKER_PREFIX=index.docker.io/barney_rubble
export DOCKER_TAG=latest # defaults to `latest`
export KUBEVIRT_PROVIDER=external

make docker push

Build and push images, create manifests and deploy CDI

We use the same workflow as the ephemeral dev environment, but skip make cluster-up:

export DOCKER_PREFIX=index.docker.io/barney_rubble
export DOCKER_TAG=latest # defaults to `latest`
export KUBEVIRT_PROVIDER=external

make cluster-sync

A note about kubernetes local-up-cluster.sh

The external provider isn't quite appropriate for use with the local-up-cluster.sh script used in the Kubernetes source repo. We'll need to add an additional local provider for this to handle some of the specifics.