question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

v1.16.1 (rev 936) broken

See original GitHub issue
mike@workstation:~$ sudo snap install microk8s --channel=edge --classic
[sudo] Passwort für mike: 
microk8s (edge) v1.16.1 aus Canonical✓ installiert
mike@workstation:~$ microk8s.enable dns ingress registry
Enabling DNS
Applying manifest
serviceaccount/coredns created
configmap/coredns created
deployment.apps/coredns created
service/kube-dns created
clusterrole.rbac.authorization.k8s.io/coredns created
clusterrolebinding.rbac.authorization.k8s.io/coredns created
Restarting kubelet
DNS is enabled
Enabling Ingress
error when retrieving current configuration of:
Resource: "/v1, Resource=namespaces", GroupVersionKind: "/v1, Kind=Namespace"
Name: "ingress", Namespace: ""
Object: &{map["apiVersion":"v1" "kind":"Namespace" "metadata":map["annotations":map["kubectl.kubernetes.io/last-applied-configuration":""] "name":"ingress"]]}
from server for: "/home/mike/snap/microk8s/936/tmp/temp.ingress.yaml": Get https://127.0.0.1:16443/api/v1/namespaces/ingress: dial tcp 127.0.0.1:16443: connect: connection refused
error when retrieving current configuration of:
Resource: "/v1, Resource=serviceaccounts", GroupVersionKind: "/v1, Kind=ServiceAccount"
Name: "nginx-ingress-microk8s-serviceaccount", Namespace: "ingress"
Object: &{map["apiVersion":"v1" "kind":"ServiceAccount" "metadata":map["annotations":map["kubectl.kubernetes.io/last-applied-configuration":""] "name":"nginx-ingress-microk8s-serviceaccount" "namespace":"ingress"]]}
from server for: "/home/mike/snap/microk8s/936/tmp/temp.ingress.yaml": Get https://127.0.0.1:16443/api/v1/namespaces/ingress/serviceaccounts/nginx-ingress-microk8s-serviceaccount: dial tcp 127.0.0.1:16443: connect: connection refused
error when retrieving current configuration of:
Resource: "rbac.authorization.k8s.io/v1, Resource=clusterroles", GroupVersionKind: "rbac.authorization.k8s.io/v1, Kind=ClusterRole"
Name: "nginx-ingress-microk8s-clusterrole", Namespace: ""
Object: &{map["apiVersion":"rbac.authorization.k8s.io/v1" "kind":"ClusterRole" "metadata":map["annotations":map["kubectl.kubernetes.io/last-applied-configuration":""] "name":"nginx-ingress-microk8s-clusterrole"] "rules":[map["apiGroups":[""] "resources":["nodes" "services"] "verbs":["get" "list" "watch"]] map["apiGroups":[""] "resources":["configmaps" "endpoints" "nodes" "pods" "secrets"] "verbs":["list" "watch"]] map["apiGroups":[""] "resources":["events"] "verbs":["create" "patch"]] map["apiGroups":["extensions" "networking.k8s.io"] "resources":["ingresses"] "verbs":["get" "list" "watch"]] map["apiGroups":["extensions" "networking.k8s.io"] "resources":["ingresses/status"] "verbs":["update"]]]]}
from server for: "/home/mike/snap/microk8s/936/tmp/temp.ingress.yaml": Get https://127.0.0.1:16443/apis/rbac.authorization.k8s.io/v1/clusterroles/nginx-ingress-microk8s-clusterrole: dial tcp 127.0.0.1:16443: connect: connection refused
error when retrieving current configuration of:
Resource: "rbac.authorization.k8s.io/v1, Resource=roles", GroupVersionKind: "rbac.authorization.k8s.io/v1, Kind=Role"
Name: "nginx-ingress-microk8s-role", Namespace: "ingress"
Object: &{map["apiVersion":"rbac.authorization.k8s.io/v1" "kind":"Role" "metadata":map["annotations":map["kubectl.kubernetes.io/last-applied-configuration":""] "name":"nginx-ingress-microk8s-role" "namespace":"ingress"] "rules":[map["apiGroups":[""] "resources":["configmaps" "endpoints" "pods" "secrets"] "verbs":["get"]] map["apiGroups":[""] "resourceNames":["ingress-controller-leader-nginx"] "resources":["configmaps"] "verbs":["create" "update"]]]]}
from server for: "/home/mike/snap/microk8s/936/tmp/temp.ingress.yaml": Get https://127.0.0.1:16443/apis/rbac.authorization.k8s.io/v1/namespaces/ingress/roles/nginx-ingress-microk8s-role: dial tcp 127.0.0.1:16443: connect: connection refused
error when retrieving current configuration of:
Resource: "rbac.authorization.k8s.io/v1, Resource=clusterrolebindings", GroupVersionKind: "rbac.authorization.k8s.io/v1, Kind=ClusterRoleBinding"
Name: "nginx-ingress-microk8s", Namespace: ""
Object: &{map["apiVersion":"rbac.authorization.k8s.io/v1" "kind":"ClusterRoleBinding" "metadata":map["annotations":map["kubectl.kubernetes.io/last-applied-configuration":""] "name":"nginx-ingress-microk8s"] "roleRef":map["apiGroup":"rbac.authorization.k8s.io" "kind":"ClusterRole" "name":"nginx-ingress-microk8s-clusterrole"] "subjects":[map["kind":"ServiceAccount" "name":"nginx-ingress-microk8s-serviceaccount" "namespace":"ingress"]]]}
from server for: "/home/mike/snap/microk8s/936/tmp/temp.ingress.yaml": Get https://127.0.0.1:16443/apis/rbac.authorization.k8s.io/v1/clusterrolebindings/nginx-ingress-microk8s: dial tcp 127.0.0.1:16443: connect: connection refused
error when retrieving current configuration of:
Resource: "rbac.authorization.k8s.io/v1, Resource=rolebindings", GroupVersionKind: "rbac.authorization.k8s.io/v1, Kind=RoleBinding"
Name: "nginx-ingress-microk8s", Namespace: "ingress"
Object: &{map["apiVersion":"rbac.authorization.k8s.io/v1" "kind":"RoleBinding" "metadata":map["annotations":map["kubectl.kubernetes.io/last-applied-configuration":""] "name":"nginx-ingress-microk8s" "namespace":"ingress"] "roleRef":map["apiGroup":"rbac.authorization.k8s.io" "kind":"Role" "name":"nginx-ingress-microk8s-role"] "subjects":[map["kind":"ServiceAccount" "name":"nginx-ingress-microk8s-serviceaccount"]]]}
from server for: "/home/mike/snap/microk8s/936/tmp/temp.ingress.yaml": Get https://127.0.0.1:16443/apis/rbac.authorization.k8s.io/v1/namespaces/ingress/rolebindings/nginx-ingress-microk8s: dial tcp 127.0.0.1:16443: connect: connection refused
error when retrieving current configuration of:
Resource: "/v1, Resource=configmaps", GroupVersionKind: "/v1, Kind=ConfigMap"
Name: "nginx-load-balancer-microk8s-conf", Namespace: "ingress"
Object: &{map["apiVersion":"v1" "kind":"ConfigMap" "metadata":map["annotations":map["kubectl.kubernetes.io/last-applied-configuration":""] "name":"nginx-load-balancer-microk8s-conf" "namespace":"ingress"]]}
from server for: "/home/mike/snap/microk8s/936/tmp/temp.ingress.yaml": Get https://127.0.0.1:16443/api/v1/namespaces/ingress/configmaps/nginx-load-balancer-microk8s-conf: dial tcp 127.0.0.1:16443: connect: connection refused
error when retrieving current configuration of:
Resource: "apps/v1, Resource=daemonsets", GroupVersionKind: "apps/v1, Kind=DaemonSet"
Name: "nginx-ingress-microk8s-controller", Namespace: "ingress"
Object: &{map["apiVersion":"apps/v1" "kind":"DaemonSet" "metadata":map["annotations":map["kubectl.kubernetes.io/last-applied-configuration":""] "labels":map["microk8s-application":"nginx-ingress-microk8s"] "name":"nginx-ingress-microk8s-controller" "namespace":"ingress"] "spec":map["selector":map["matchLabels":map["name":"nginx-ingress-microk8s"]] "template":map["metadata":map["labels":map["name":"nginx-ingress-microk8s"]] "spec":map["containers":[map["args":["/nginx-ingress-controller" "--configmap=$(POD_NAMESPACE)/nginx-load-balancer-microk8s-conf" "--publish-status-address=127.0.0.1"] "env":[map["name":"POD_NAME" "valueFrom":map["fieldRef":map["fieldPath":"metadata.name"]]] map["name":"POD_NAMESPACE" "valueFrom":map["fieldRef":map["fieldPath":"metadata.namespace"]]]] "image":"quay.io/kubernetes-ingress-controller/nginx-ingress-controller-amd64:0.25.1" "livenessProbe":map["httpGet":map["path":"/healthz" "port":'\u280e' "scheme":"HTTP"] "initialDelaySeconds":'\x1e' "timeoutSeconds":'\x05'] "name":"nginx-ingress-microk8s" "ports":[map["containerPort":'P'] map["containerPort":'\u01bb']]]] "dnsPolicy":"ClusterFirstWithHostNet" "hostNetwork":%!q(bool=true) "serviceAccountName":"nginx-ingress-microk8s-serviceaccount" "terminationGracePeriodSeconds":'<']]]]}
from server for: "/home/mike/snap/microk8s/936/tmp/temp.ingress.yaml": Get https://127.0.0.1:16443/apis/apps/v1/namespaces/ingress/daemonsets/nginx-ingress-microk8s-controller: dial tcp 127.0.0.1:16443: connect: connection refused
Failed to enable ingress

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:9 (5 by maintainers)

github_iconTop GitHub Comments

2reactions
octopus-primecommented, Oct 7, 2019

Running microk8s.enable separately for each add-on works. Thanks!

1reaction
ktsakalozoscommented, Oct 7, 2019

@rzr we recently added the microk8s.status --wait-ready in the microk8s.enable wrapper https://github.com/ubuntu/microk8s/blob/master/microk8s-resources/wrappers/microk8s-enable.wrapper#L38 . It might worth making the microk8s.enable ingress addon blocking (ie wait for services to come up). Any tips on how to reproduce this race condition?

Read more comments on GitHub >

github_iconTop Results From Across the Web

v1.16.1 (rev 936) broken · Issue #706 · canonical/microk8s
v1.16.1 (rev 936) broken #706 ... "name":"ingress"]]} from server for: "/home/mike/snap/microk8s/936/tmp/temp.ingress.yaml": Get ...
Read more >
Answers to Selected Exercises - Mathematical Sciences
(VI) e. (III) f. (II) ... tle in Australia or South Africa, while the entries in AC break ... 1 hour: .6; 2...
Read more >
The Peculiar 2016 Eruption of the Unique Recurrent Nova ...
As well as never being seen before, the bright cusp appears to break this smooth evolution. The 2016 eruption does not just appear...
Read more >
MDK5 Software Packs - Keil
Keil makes C compilers, macro assemblers, real-time kernels, debuggers, simulators, integrated environments, evaluation boards, and emulators for the ARM, ...
Read more >
Phosphate binders for preventing and treating chronic kidney ...
Phosphate binders are used to reduce positive phosphate balance and to lower serum phosphate levels for people with chronic kidney disease (CKD) ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found