c12s-kubespray/roles/dnsmasq/templates/dnsmasq-svc.yml.j2

---
apiVersion: v1
kind: Service
metadata:
  labels:
    kubernetes.io/cluster-service: 'true'
    k8s-app: dnsmasq
  name: dnsmasq
  namespace: kube-system
spec:
  ports:
    - port: 53
      name: dns-tcp
      targetPort: 53
      protocol: TCP
    - port: 53
      name: dns
      targetPort: 53
      protocol: UDP
  type: ClusterIP
  clusterIP: {{dnsmasq_dns_server}}
  selector:
    k8s-app: dnsmasq
Use dnsmasq inside pods 2016-03-18 14:07:33 +00:00			`---`
			`apiVersion: v1`
			`kind: Service`
			`metadata:`
			`labels:`
			`kubernetes.io/cluster-service: 'true'`
			`k8s-app: dnsmasq`
			`name: dnsmasq`
Stop templating kube-system namespace and creating it (#2545) Kubernetes makes this namespace automatically, so there is no need for kubespray to manage it. 2018-03-30 11:29:13 +00:00			`namespace: kube-system`
Use dnsmasq inside pods 2016-03-18 14:07:33 +00:00			`spec:`
			`ports:`
			`- port: 53`
			`name: dns-tcp`
			`targetPort: 53`
			`protocol: TCP`
			`- port: 53`
			`name: dns`
			`targetPort: 53`
			`protocol: UDP`
			`type: ClusterIP`
Rename dns_server, add var for selinux. (#1572) * Rename dns_server to dnsmasq_dns_server so that it includes role prefix as the var name is generic and conflicts when integrating with existing ansible automation. * Enable selinux state to be configurable with new var preinstall_selinux_state 2017-10-11 19:40:21 +00:00			`clusterIP: {{dnsmasq_dns_server}}`
Use dnsmasq inside pods 2016-03-18 14:07:33 +00:00			`selector:`
			`k8s-app: dnsmasq`