Skip to content

Latest commit

 

History

History
43 lines (34 loc) · 3.1 KB

rackspace.md

File metadata and controls

43 lines (34 loc) · 3.1 KB
Raw

Rackspace

In general, the dev-build-and-up.sh workflow for Rackspace is the similar to GCE. The specific implementation is different due to the use of CoreOS, Rackspace Cloud Files and network design.

These scripts should be used to deploy development environments for Kubernetes. If your account leverages RackConnect or non-standard networking, these scripts will most likely not work without modification.

NOTE: The rackspace scripts do NOT rely on saltstack.

The current cluster design is inspired by:

Prerequisites

  1. You need to have both nova and swiftly installed. It's recommended to use a python virtualenv to install these packages into.
  2. Make sure you have the appropriate environment variables set to interact with the OpenStack APIs. See Rackspace Documentation for more details.

Provider: Rackspace

  • To use Rackspace as the provider, set the KUBERNETES_PROVIDER ENV variable: export KUBERNETES_PROVIDER=rackspace and run the bash hack/dev-build-and-up.sh script.

Build

  1. The kubernetes binaries will be built via the common build scripts in build/.
  2. If you've set the ENV KUBERNETES_PROVIDER=rackspace, the scripts will upload kubernetes-server-linux-amd64.tar.gz to Cloud Files.
  3. A cloud files container will be created via the swiftly CLI and a temp URL will be enabled on the object.
  4. The built kubernetes-server-linux-amd64.tar.gz will be uploaded to this container and the URL will be passed to master/minions nodes when booted.

Cluster

  1. There is a specific cluster/rackspace directory with the scripts for the following steps:
  2. A cloud network will be created and all instances will be attached to this network. We will connect the master API and minion kubelet service via this network.
  3. A SSH key will be created and uploaded if needed. This key must be used to ssh into the machines since we won't capture the password.
  4. A master and minions will be created via the nova CLI. A cloud-config.yaml is generated and provided as user-data with the entire configuration for the systems.
  5. We then boot as many minions as defined via $RAX_NUM_MINIONS.

Some notes:

  • The scripts expect eth2 to be the cloud network that the containers will communicate across.
  • A number of the items in config-default.sh are overridable via environment variables.
  • For older versions please either:

Network Design

  • eth0 - Public Interface used for servers/containers to reach the internet
  • eth1 - ServiceNet - Intra-cluster communication (k8s, etcd, etc) communicate via this interface. The cloud-config files use the special CoreOS identifier $private_ipv4 to configure the services.
  • eth2 - Cloud Network - Used for k8s pods to communicate with one another. The proxy service will pass traffic via this interface.