This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

This repository currently has no open or pending branches.

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

after the repo migration, can we please get travis CI enabled? thanks.

Hi,

I've been playing around writing individual master and node components as resources itself in [1]. Right now I have enough defaults to get each process running at least. If the rewrite described in #5 is a similar approach, I'd love to help out.

[1] https://github.com/aespinosa/cookbook-kube

now that kubernetes is ga, we should go to the v1 api

Cookbook version

1.0.0

Chef-client version

N/A

Platform Details

Vagrant

Scenario:

I am trying to use the cookbook in a Chef Solo provisioner in Vagrant. But the kuberneters::node recipe is faulty since it calls the kube_node resource without a master_ip.

I can see in the history that the recipes have been removed:
7e0e761

But the released documentation still mentions them:
https://supermarket.chef.io/cookbooks/kubernetes

Steps to Reproduce:

Vagrant looks something like this:

  config.vm.define "k8s-master" do |master|
    master.vm.provision "chef_solo" do |chef|
      chef.add_recipe "kubernetes::master"
    end
  end

  2.times do |n|
    config.vm.define "k8s-worker-#{n}" do |worker|
      worker.vm.provision "chef_solo" do |chef|
        chef.add_recipe "kubernetes::node"
      end
    end
  end

Expected Result:

I can follow the docs.

Actual Result:

I get an error about a missing, required master_ip property when calling kube_node.

As a user, I'd like to not only have Chef ensure my Kubernetes entities exist, but also that they are up to date.

k8s is not the best name for the overall intent of this cookbook and implies that people will understand the shortname

Cookbook version

N/A - Latest

Chef-client version

>= 12.14

Platform Details

EL/Debian Based Distros

Scenario:

I would like to support Weave-Net and not be forced into using Flannel.

Steps to Reproduce:

Use the established resources.

Expected Result:

Swap Flannel for Weave-Net (or other available networking services)

Actual Result:

Flannel is the only option.

Merge in the kube resources for setting up kubernetes itself

As a user, I'd like the node recipe to setup a kubernetes node that is able to talk to a kubernetes master other than localhost.