Kubemark Master
Kubernetes Cluster
Every running Kubemark setup looks like the following:
When using the pre-existing provider, the developer is responsible for creating #1 and #2. Therefore, the kubemark scripts will not create any infrastructure or start a kubemark master like in other providers. Instead, the existing resources provided by the VM at $MASTER_IP will serve as the kubemark master.
The goal of the pre-existing provider is to use the kubemark tools with an existing kubermark master. It's meant to provide the developer with additional flexibility to customize the cluster infrastructure and still use the kubemark setup tools. The pre-existing provider is an advanced use case that requires the developer to have knowledge of setting up a kubemark master.
To use the pre-existing provider, the expectation is that there‘s a kubemark master that is rechable at $MASTER_IP. The machine that the kubemark master is on has to be ssh able from the host that’s executing the kubemark scripts. And the user on that machine has to be ‘kubernetes’.
Requirement checklist:
test/kubemark/cloud-provider-config.sh
CLOUD_PROVIDER="pre-existing" KUBEMARK_IMAGE_MAKE_TARGET="push" CONTAINER_REGISTRY=docker.io PROJECT="rthallisey" MASTER_IP="192.168.121.29:6443"