Skip to content

Instantly share code, notes, and snippets.

@boyvinall
Last active August 8, 2017 11:58
Show Gist options
  • Save boyvinall/2e18fe98ac620bfa1c3a57036d40b97e to your computer and use it in GitHub Desktop.
Save boyvinall/2e18fe98ac620bfa1c3a57036d40b97e to your computer and use it in GitHub Desktop.
apiVersion: v1
kind: ConfigMap
metadata:
name: coredns
namespace: kube-system
data:
Corefile: |
.:53 {
log stdout
health
# Replace cluster.local with your cluster domain
kubernetes cluster.local
proxy . /etc/resolv.conf
cache 30
}
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: coredns
namespace: kube-system
labels:
k8s-app: coredns
kubernetes.io/cluster-service: "true"
kubernetes.io/name: "CoreDNS"
spec:
replicas: 1
selector:
matchLabels:
k8s-app: coredns
template:
metadata:
labels:
k8s-app: coredns
annotations:
scheduler.alpha.kubernetes.io/critical-pod: ''
scheduler.alpha.kubernetes.io/tolerations: '[{"key":"CriticalAddonsOnly", "operator":"Exists"}]'
spec:
containers:
- name: coredns
image: rothgar/coredns:004
imagePullPolicy: Always
args: [ "-conf", "/etc/coredns/Corefile" ]
volumeMounts:
- name: config-volume
mountPath: /etc/coredns
ports:
- containerPort: 53
name: dns
protocol: UDP
- containerPort: 53
name: dns-tcp
protocol: TCP
livenessProbe:
httpGet:
path: /health
port: 8080
scheme: HTTP
initialDelaySeconds: 60
timeoutSeconds: 5
successThreshold: 1
failureThreshold: 5
dnsPolicy: Default
volumes:
- name: config-volume
configMap:
name: coredns
items:
- key: Corefile
path: Corefile
---
apiVersion: v1
kind: Service
metadata:
name: coredns
namespace: kube-system
labels:
k8s-app: coredns
kubernetes.io/cluster-service: "true"
kubernetes.io/name: "CoreDNS"
spec:
selector:
k8s-app: coredns
# Replace with your cluster DNS IP
clusterIP: 10.254.0.10
ports:
- name: dns
port: 53
protocol: UDP
- name: dns-tcp
port: 53
protocol: TCP
$ openstack coe cluster show kube
+---------------------+------------------------------------------------------------+
| Field | Value |
+---------------------+------------------------------------------------------------+
| status | CREATE_COMPLETE |
| cluster_template_id | ecffff66-ba7e-440d-8c76-65394b5a747e |
| node_addresses | [u'192.168.1.104', u'192.168.1.106'] |
| uuid | 9cf0aa94-eb1a-498e-81a3-5649b59a69ae |
| stack_id | 5dc9c557-12cc-4575-b0a6-8ce05a269bd3 |
| status_reason | Stack CREATE completed successfully |
| created_at | 2017-08-08T11:15:58+00:00 |
| updated_at | 2017-08-08T11:17:58+00:00 |
| coe_version | v1.5.3 |
| faults | |
| keypair | my-key |
| api_address | http://192.168.1.112:8080 |
| master_addresses | [u'192.168.1.112'] |
| create_timeout | 60 |
| node_count | 2 |
| discovery_url | https://discovery.etcd.io/d61a35e234b479c9557e8c8c67f037c0 |
| master_count | 1 |
| container_version | 1.12.6 |
| name | kube |
+---------------------+------------------------------------------------------------+
$ kubectl get events
LASTSEEN FIRSTSEEN COUNT NAME KIND SUBOBJECT TYPE REASON SOURCE MESSAGE
6m 6m 1 centos-1397332347-kh8db Pod Normal Scheduled default-scheduler Successfully assigned centos-1397332347-kh8db to ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf
6m 6m 2 centos-1397332347-kh8db Pod Warning MissingClusterDNS kubelet, ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. Falling back to DNSDefault policy.
6m 6m 1 centos-1397332347-kh8db Pod spec.containers{centos} Normal Pulling kubelet, ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf pulling image "centos"
6m 6m 1 centos-1397332347-kh8db Pod spec.containers{centos} Normal Pulled kubelet, ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf Successfully pulled image "centos"
6m 6m 1 centos-1397332347-kh8db Pod spec.containers{centos} Normal Created kubelet, ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf Created container with docker id 2dd666e6f600; Security:[seccomp=unconfined]
6m 6m 1 centos-1397332347-kh8db Pod spec.containers{centos} Normal Started kubelet, ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf Started container with docker id 2dd666e6f600
6m 6m 1 centos-1397332347 ReplicaSet Normal SuccessfulCreate replicaset-controller Created pod: centos-1397332347-kh8db
6m 6m 1 centos Deployment Normal ScalingReplicaSet deployment-controller Scaled up replica set centos-1397332347 to 1
35m 35m 1 ku-d3vcftqjgf-0-nuywsttffjdc-kube-minion-vyq22k53tjm7 Node Normal Starting kubelet, ku-d3vcftqjgf-0-nuywsttffjdc-kube-minion-vyq22k53tjm7 Starting kubelet.
35m 35m 1 ku-d3vcftqjgf-0-nuywsttffjdc-kube-minion-vyq22k53tjm7 Node Warning ImageGCFailed kubelet, ku-d3vcftqjgf-0-nuywsttffjdc-kube-minion-vyq22k53tjm7 unable to find data for container /
35m 35m 2 ku-d3vcftqjgf-0-nuywsttffjdc-kube-minion-vyq22k53tjm7 Node Normal NodeHasSufficientDisk kubelet, ku-d3vcftqjgf-0-nuywsttffjdc-kube-minion-vyq22k53tjm7 Node ku-d3vcftqjgf-0-nuywsttffjdc-kube-minion-vyq22k53tjm7 status is now: NodeHasSufficientDisk
35m 35m 2 ku-d3vcftqjgf-0-nuywsttffjdc-kube-minion-vyq22k53tjm7 Node Normal NodeHasSufficientMemory kubelet, ku-d3vcftqjgf-0-nuywsttffjdc-kube-minion-vyq22k53tjm7 Node ku-d3vcftqjgf-0-nuywsttffjdc-kube-minion-vyq22k53tjm7 status is now: NodeHasSufficientMemory
35m 35m 2 ku-d3vcftqjgf-0-nuywsttffjdc-kube-minion-vyq22k53tjm7 Node Normal NodeHasNoDiskPressure kubelet, ku-d3vcftqjgf-0-nuywsttffjdc-kube-minion-vyq22k53tjm7 Node ku-d3vcftqjgf-0-nuywsttffjdc-kube-minion-vyq22k53tjm7 status is now: NodeHasNoDiskPressure
35m 35m 1 ku-d3vcftqjgf-0-nuywsttffjdc-kube-minion-vyq22k53tjm7 Node Normal RegisteredNode controllermanager Node ku-d3vcftqjgf-0-nuywsttffjdc-kube-minion-vyq22k53tjm7 event: Registered Node ku-d3vcftqjgf-0-nuywsttffjdc-kube-minion-vyq22k53tjm7 in NodeController
35m 35m 2 ku-d3vcftqjgf-0-nuywsttffjdc-kube-minion-vyq22k53tjm7 Node Warning MissingClusterDNS kubelet, ku-d3vcftqjgf-0-nuywsttffjdc-kube-minion-vyq22k53tjm7 kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. pod: "kube-ui-v4-5v0cr_kube-system(32124cd8-7c2b-11e7-9796-fa163e10c27d)". Falling back to DNSDefault policy.
34m 35m 2 ku-d3vcftqjgf-0-nuywsttffjdc-kube-minion-vyq22k53tjm7 Node Warning MissingClusterDNS kubelet, ku-d3vcftqjgf-0-nuywsttffjdc-kube-minion-vyq22k53tjm7 kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. pod: "kube-proxy-ku-d3vcftqjgf-0-nuywsttffjdc-kube-minion-vyq22k53tjm7_kube-system(48401ec6465311224effc6721ddd6b8d)". Falling back to DNSDefault policy.
34m 34m 1 ku-d3vcftqjgf-0-nuywsttffjdc-kube-minion-vyq22k53tjm7 Node Normal Starting kube-proxy, ku-d3vcftqjgf-0-nuywsttffjdc-kube-minion-vyq22k53tjm7 Starting kube-proxy.
35m 35m 1 ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf Node Normal Starting kubelet, ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf Starting kubelet.
35m 35m 1 ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf Node Warning ImageGCFailed kubelet, ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf unable to find data for container /
35m 35m 2 ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf Node Normal NodeHasSufficientDisk kubelet, ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf Node ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf status is now: NodeHasSufficientDisk
35m 35m 2 ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf Node Normal NodeHasSufficientMemory kubelet, ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf Node ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf status is now: NodeHasSufficientMemory
35m 35m 2 ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf Node Normal NodeHasNoDiskPressure kubelet, ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf Node ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf status is now: NodeHasNoDiskPressure
35m 35m 1 ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf Node Normal RegisteredNode controllermanager Node ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf event: Registered Node ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf in NodeController
34m 35m 2 ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf Node Warning MissingClusterDNS kubelet, ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. pod: "kube-proxy-ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf_kube-system(48401ec6465311224effc6721ddd6b8d)". Falling back to DNSDefault policy.
$ kubectl run -ti centos --image=centos bash
If you don't see a command prompt, try pressing enter.
Error attaching, falling back to logs: error dialing backend: dial tcp: lookup ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf on 8.8.8.8:53: no such host
Error from server: Get https://ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf:10250/containerLogs/default/centos-1397332347-kh8db/centos: dial tcp: lookup ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf on 8.8.8.8:53: no such host
$ kubectl create -f kube-dns.yml
configmap "coredns" created
deployment "coredns" created
service "coredns" created
$ kubectl get -n kube-system po
NAME READY STATUS RESTARTS AGE
coredns-3788349839-n8lnj 0/1 Error 0 6s
kube-controller-manager-ku-ykilcseltk-0-ikfmjokra3pa-kube-master-rewunsibdknc 1/1 Running 0 40m
kube-proxy-ku-d3vcftqjgf-0-nuywsttffjdc-kube-minion-vyq22k53tjm7 1/1 Running 0 39m
kube-proxy-ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf 1/1 Running 0 39m
kube-proxy-ku-ykilcseltk-0-ikfmjokra3pa-kube-master-rewunsibdknc 1/1 Running 0 40m
kube-scheduler-ku-ykilcseltk-0-ikfmjokra3pa-kube-master-rewunsibdknc 1/1 Running 0 40m
kube-ui-v4-5v0cr 1/1 Running 0 39m
$ kubectl get -n kube-system po
NAME READY STATUS RESTARTS AGE
coredns-3788349839-n8lnj 0/1 Error 1 9s
kube-controller-manager-ku-ykilcseltk-0-ikfmjokra3pa-kube-master-rewunsibdknc 1/1 Running 0 40m
kube-proxy-ku-d3vcftqjgf-0-nuywsttffjdc-kube-minion-vyq22k53tjm7 1/1 Running 0 39m
kube-proxy-ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf 1/1 Running 0 39m
kube-proxy-ku-ykilcseltk-0-ikfmjokra3pa-kube-master-rewunsibdknc 1/1 Running 0 40m
kube-scheduler-ku-ykilcseltk-0-ikfmjokra3pa-kube-master-rewunsibdknc 1/1 Running 0 40m
kube-ui-v4-5v0cr 1/1 Running 0 39m
$ kubectl get -n kube-system po
NAME READY STATUS RESTARTS AGE
coredns-3788349839-n8lnj 0/1 CrashLoopBackOff 1 10s
kube-controller-manager-ku-ykilcseltk-0-ikfmjokra3pa-kube-master-rewunsibdknc 1/1 Running 0 40m
kube-proxy-ku-d3vcftqjgf-0-nuywsttffjdc-kube-minion-vyq22k53tjm7 1/1 Running 0 39m
kube-proxy-ku-d3vcftqjgf-1-pnjgh4fdsgbq-kube-minion-tbustm35hxhf 1/1 Running 0 39m
kube-proxy-ku-ykilcseltk-0-ikfmjokra3pa-kube-master-rewunsibdknc 1/1 Running 0 40m
kube-scheduler-ku-ykilcseltk-0-ikfmjokra3pa-kube-master-rewunsibdknc 1/1 Running 0 40m
kube-ui-v4-5v0cr 1/1 Running 0 39m
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment