RETIRED, Fuel CCP - Installer sub-project
Go to file
Maciej Kwiek 1abf5ac1c4 Bump solar-minimal image version
Change-Id: I4178d7a490345924c1532c87c7e940e2edd103b2
2016-06-01 09:45:51 +02:00
deploy Verbose task errors logging in deploy.sh 2016-05-20 16:01:44 +02:00
resources Merge "Verbose task errors logging in deploy.sh" 2016-06-01 07:39:46 +00:00
utils Bump solar-minimal image version 2016-06-01 09:45:51 +02:00
.gitignore Add scripts for jenkins tests 2016-05-06 09:24:14 +02:00
.gitreview Initial tox.ini with bashate test and .gitreview 2016-05-10 12:16:25 +00:00
README.md Fix duplicate 2016-05-09 09:50:14 +02:00
config.yaml.sample Possibility to set all values of global_config in yaml file 2016-05-05 22:48:38 +02:00
kube-config Added several quality of life improvements 2016-04-28 16:05:17 +02:00
mcpinstall.py Fixed add_nodes behaviour 2016-05-20 11:12:48 +00:00
requirements.txt k8s nodes use public IP based on k8s/global_config resource 2016-04-13 16:49:43 +02:00
tox.ini Added pep8 check in tox.ini 2016-05-10 13:26:17 +00:00

README.md

This repository contains resources for configuring kubernetes with calico networking plugin using Solar.

Express Vagrant setup:

  1. git clone -b stable https://github.com/pigmej/mcpinstall.git && cd mcpinstall
  2. ./deploy/kube-up.sh
  3. vagrant ssh solar
  4. kubectl get pods

You can adjust any setting value from utils/vagrant/vagrant-settings.yaml_defaults by setting it in utils/vagrant/vagrant-settings.yaml. For example on Linux you should consider setting sync_type to nfs by adding sync_type: nfs to your vagrant-settings.yaml.

Fedora slave nodes:

If you don't want to use Ubuntu for slaves, you can use Fedora. After step 2 in above steps, please do as follow:

  1. Download box file for the Vagrant provider you are using from here
  2. Import it to Vagrant vagrant box add fc23 <downloaded-box-name> --provider <provider> --force
  3. Change slaves_image value to fc23 in vagrant-settings.yaml file.
  4. Proceed from step 3 from "Express Vagrant setup" section.

Configuration:

In config.yaml you can set:

  • login data for kubernetes master
  • IP address for master
  • default login data for kubernetes slave nodes
  • node-specific config (IP address is required, but you can override default access data)
  • global_config resource inputs including:
    • cluster dns ip and domain
    • cluster ip range
    • default k8s version
    • default calico version

LCM example: Kubernetes version change:

  1. log in to solar master node (vagrant ssh solar)
  2. solar resource update kube-config k8s_version=v1.2.1
  3. solar changes stage
  4. solar changes process
  5. solar orch run-once -w 600
  6. After a while, kubernetes will restart in desired version