...

Text file src/k8s.io/kubernetes/test/kubemark/pre-existing/README.md

Documentation: k8s.io/kubernetes/test/kubemark/pre-existing

     1# Kubemark Pre-existing Provider Guide
     2
     3**Kubemark Master**
     4- A set of Kubernetes control plane components running in a VM
     5
     6**Kubernetes Cluster**
     7- A real Kubernetes Cluster that has master and nodes. The hollow-node pods
     8  are run in this cluster, but appear as nodes to the Kubemark Master
     9
    10## Introduction
    11
    12Every running Kubemark setup looks like the following:
    13 1) A running Kubernetes cluster pointed to by the local kubeconfig
    14 2) A separate VM where the kubemark master is running
    15 3) Some hollow-nodes that run on the Kubernetes Cluster from #1
    16 4) The hollow-nodes are configured to talk with the kubemark master at #2
    17
    18When using the pre-existing provider, the developer is responsible for creating
    19#1 and #2.  Therefore, the kubemark scripts will not create any infrastructure
    20or start a kubemark master like in other providers. Instead, the existing
    21resources provided by the VM at $MASTER_IP will serve as the kubemark master.
    22
    23## Use Case
    24
    25The goal of the pre-existing provider is to use the kubemark tools with an
    26existing kubemark master. It's meant to provide the developer with
    27additional flexibility to customize the cluster infrastructure and still use
    28the kubemark setup tools.  The pre-existing provider is an **advanced** use
    29case that requires the developer to have knowledge of setting up a kubemark
    30master.
    31
    32## Requirements
    33
    34To use the pre-existing provider, the expectation is that there's a kubemark
    35master that is reachable at $MASTER_IP. The machine that the kubemark master is
    36on has to be ssh able from the host that's executing the kubemark scripts. And
    37the user on that machine has to be 'kubernetes'.
    38
    39Requirement checklist:
    40- Set MASTER_IP to ip address to the kubemark master
    41- The host where you execute the kubemark scripts must be able to ssh to
    42  kubernetes@$MASTER_IP
    43
    44## Example Configuration
    45
    46_test/kubemark/cloud-provider-config.sh_
    47
    48```
    49CLOUD_PROVIDER="pre-existing"
    50KUBEMARK_IMAGE_MAKE_TARGET="push"
    51CONTAINER_REGISTRY=docker.io
    52PROJECT="rthallisey"
    53MASTER_IP="192.168.121.29:6443"
    54```

View as plain text