Asking for help? Comment out what you need so we can get more information to help you!
Cluster information:
Kubernetes version: 1.26.1
Cloud being used: (put bare-metal if not on a public cloud)
Installation method: manual
Host OS: Redhat v8
CNI and version:
CRI and version: 1.27.0
I am inside a protected network and use a http/https proxy… When running the kubeadm init it is not able to find/connect to dl.k8s.io or release.k8s.io. It doesn’t seem to start the apiserver on 6443 so it just tries to connect until it errors out, and a kubectl errors on 8080 connecting. I’m new and I’m completely lost.
Please help
You will have to mirror the images for you to use, see the stability guarantee here:
There have been several blogs published on Kubernetes Blog | Kubernetes the subject if you’re looking for any further specific guidance.
thanks for the feedback, the problem I’ve narrowed it down to is when connecting out it is not sending valid host headers and the firewall/proxy is rejecting these requests. On RHEL 7, HTTP_PROXY=… works like a champ. Also to note CURL does not work unless you put the proxy in the curl command line.
e.g. curl -x :
So for some reason the connection out via kubeadm and curl using the env vars is sending bad or no host headers.
oh yeah and this also affected GIT an was resolved by adding the proxy info into the git conf
curiouser and curiouser.
I should mention I’m working on RHEL 8 using crio.