Home • Explore • Blog • CI
☰



kubernetes
1st chunk of `content/en/blog/_posts/2015-07-00-Weekly-Kubernetes-Community-Hangout_23.md`
cedcc189f10903366e331c21a0eb922eda9d04e786f0cfdb0000000100000872
---
title: " Weekly Kubernetes Community Hangout Notes - July 17 2015 "
date: 2015-07-23
slug: weekly-kubernetes-community-hangout_23
url: /blog/2015/07/Weekly-Kubernetes-Community-Hangout_23
---




Every week the Kubernetes contributing community meet virtually over Google Hangouts. We want anyone who's interested to know what's discussed in this forum.

Here are the notes from today's meeting:



- Eric Paris: replacing salt with ansible (if we want)

  - In contrib, there is a provisioning tool written in ansible
  - The goal in the rewrite was to eliminate as much of the cloud provider stuff as possible
  - The salt setup does a bunch of setup in scripts and then the environment is setup with salt

    - This means that things like generating certs is done differently on GCE/AWS/Vagrant
  - For ansible, everything must be done within ansible
  - Background on ansible

    - Does not have clients
    - Provisioner ssh into the machine and runs scripts on the machine
    - You define what you want your cluster to look like, run the script, and it sets up everything at once
    - If you make one change in a config file, ansible re-runs everything (which isn’t always desirable)
    - Uses a jinja2 template
  - Create machines with minimal software, then use ansible to get that machine into a runnable state

    - Sets up all of the add-ons
  - Eliminates the provisioner shell scripts
  - Full cluster setup currently takes about 6 minutes

    - CentOS with some packages
    - Redeploy to the cluster takes 25 seconds
  - Questions for Eric

    - Where does the provider-specific configuration go?

      - The only network setup that the ansible config does is flannel; you can turn it off
    - What about init vs. systemd?

      - Should be able to support in the code w/o any trouble (not yet implemented)
  - Discussion

    - Why not push the setup work into containers or kubernetes config?

      - To bootstrap a cluster drop a kubelet and a manifest
    - Running a kubelet and configuring the network should be the only things required. We can cut a machine image that is preconfigured minus the data package (certs, etc)
Title: Kubernetes Community Hangout Notes - July 17, 2015: Ansible vs. Salt
Summary
These are notes from the Kubernetes community hangout on July 17, 2015. The discussion focused on replacing Salt with Ansible for provisioning. Ansible offers advantages like provider-agnostic configuration, single-step cluster setup, and elimination of provisioner shell scripts. The discussion covered topics like provider-specific configuration, init systems, and the possibility of pushing setup work into containers or Kubernetes configurations.