Microk8s not starting behind corporate proxy
See original GitHub issueI installed microk8s on a Ubuntu 20.04 server via snap as of the official documentation. After the installation, the kubernetes cluster does not boot up properly, as the calico pods cannot be retrieved.
Nov 06 14:31:07 SRV100116 microk8s.daemon-containerd[1073]: time="2020-11-06T14:31:07.363358638+01:00" level=error msg="Failed to load cni configuration" error="cni config load failed: no network config found in /var/snap/microk8s/1769/args/cni-network: cni plugin not initialized: failed to load cni config"
Nov 06 14:31:12 SRV100116 microk8s.daemon-containerd[1073]: time="2020-11-06T14:31:12.364102216+01:00" level=error msg="Failed to load cni configuration" error="cni config load failed: no network config found in /var/snap/microk8s/1769/args/cni-network: cni plugin not initialized: failed to load cni config"
Nov 06 14:31:14 SRV100116 microk8s.daemon-containerd[1073]: time="2020-11-06T14:31:14.248621204+01:00" level=info msg="RunPodsandbox for &PodSandboxMetadata{Name:calico-node-q4ghx,Uid:1ba56ccd-5d72-4db5-ad12-5dcf0463a2af,Namespace:kube-system,Attempt:0,}"
Nov 06 14:31:15 SRV100116 microk8s.daemon-containerd[1073]: time="2020-11-06T14:31:15.120050803+01:00" level=error msg="RunPodSandbox for &PodSandboxMetadata{Name:calico-node-q4ghx,Uid:1ba56ccd-5d72-4db5-ad12-5dcf0463a2af,Namespace:kube-system,Attempt:0,} failed, error" error="failed to get sandbox image \"k8s.gcr.io/pause:3.1\": failed to pull image \"k8s.gcr.io/pause:3.1\": failed to pull and unpack image \"k8s.gcr.io/pause:3.1\": failed to copy: httpReaderSeeker: failed open: unexpected status code https://k8s.gcr.io/v2/pause/blobs/sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e: 503 Service Unavailable"
I have the suspicion that the corporate proxy server in the network is somehow blocking the download of the images. The proxy is doing deep package inspection and re-encrypting any SSL traffic. The root certificate of the proxy is correctly installed in /etc/ssl/certs/ca-certificates.crt
I am not sure, if I need to do some extra configuration, or if there is a bug that prevents microk8s from spawning. Any help is highly appreciated.
Issue Analytics
- State:
- Created 3 years ago
- Comments:8
Top Results From Across the Web
Microk8s not starting behind corporate proxy #1718 - GitHub
I installed microk8s on a Ubuntu 20.04 server via snap as of the official documentation. After the installation, the kubernetes cluster does not...
Read more >Installing behind a proxy - MicroK8s
Configuring the proxy environment variables. MicroK8s packages a number of utilities (eg curl, helm) that may need to fetch resources from the internet....
Read more >Installing behind a proxy - microk8s - Discuss Kubernetes
Configuring the proxy environment variables MicroK8s packages a number of utilities (eg curl, helm) that may need to fetch resources from ...
Read more >Running microk8s behind proxy - Developer Diary
My work workplace is an enterprise with all kinds of administrative controls. Access to the outside network is restricted and routed via a ......
Read more >microk8s behind authenticated proxy | by Prashant - Medium
Most likely you came here becuase you want to learn Kubernetes and trying to install microk8s on a system behind authenticated proxy server....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@mavencode01 I’m sorry, not
kubelet-env
butkubectl-env
. It’s also placed in SNAP_DATA -${SNAP_DATA}/args/kubectl-env
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.