In general, the dev-build-and-up.sh workflow for Rackspace is the similar to Google Compute Engine. The specific implementation is different due to the use of CoreOS, Rackspace Cloud Files and the overall 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 and instead rely on cloud-init for configuration.
The current cluster design is inspired by:
swiftlyinstalled. It’s recommended to use a python virtualenv to install these packages into.
export KUBERNETES_PROVIDER=rackspaceand run the
export KUBERNETES_PROVIDER=rackspace; wget -q -O - https://get.k8s.io | bash
KUBERNETES_PROVIDER=rackspace, the scripts will upload
kubernetes-server-linux-amd64.tar.gzto Cloud Files.
swiftlyCLI and a temp URL will be enabled on the object.
kubernetes-server-linux-amd64.tar.gzwill be uploaded to this container and the URL will be passed to master/nodes when booted.
There is a specific
cluster/rackspace directory with the scripts for the following steps:
cloud-config.yamlis generated and provided as user-data with the entire configuration for the systems.
eth2to be the cloud network that the containers will communicate across.
config-default.share overridable via environment variables.
git checkout v0.9
git checkout v0.3
cloud-configfiles use the special CoreOS identifier
$private_ipv4to configure the services.
|IaaS Provider||Config. Mgmt||OS||Networking||Docs||Conforms||Support Level|
For support level information on all solutions, see the Table of solutions chart.Create Issue Edit This Page