apiVersion: v1
kind: Service
metadata:
  name: redis-cache
  labels:
    role: cache
spec:
  type: NodePort
  ports:
  - port: 6379
    targetPort: 6379
  selector:
    role: cache

TIL NodePort && targetPort

After completing my kubernetes setup, I realise that there is some caveats and stuff to know beforehand :

• Kubernetes is not admin friendly, it's meant to be user friendly more or less
• If you don't know anything about BGP/OSPF, you will have a hard time implementing a "simple" overlay network and will have to use flannel, calico or whatever shit they put on their documentation. On my end, quagga and bgpd ftw.
• Kubernetes is multimaster "by design" but none of the daemons are multimaster compliant, so you will have to setup some DNS infrastructure if you don't already have one
• This is a good product, you might overlook it and prefer to use Mesos or its wrapper DC/OS, imho : it would be a mistake to dismiss kubernetes VS mesos on the simple fact that it's harder to setup.

it took me a good week to properly understand and setup, I think this is the minimum learning curve for anybody who want to properly understand what is done and could be done.

POURQUOI le SDN est il obligatoire pour ce genre de shit ?

via stephane

Un excellent descriptif des différentes solutions networking pour k8s

ça peut être bien puissant avec un haproxy devant et un kubernetes / etcd derrière

ça, je garde sous le coude :)