[k8s] No IP for Ingress with kubeadm bootstrapped clusters

Summary

I have bootstrapped a kubeadm single node cluster in my own machine, and tried to install Gitlab integration on it. However, Gitlab never received the IP addresses for Ingress and the Ingress controllers falls into crashloopback

Steps to reproduce

  1. Following the command here, install kubeadm.
  2. Give the below commands, note that I have tried both flannel and weavenet, no luck
sudo kubeadm init --pod-network-cidr=10.244.0.0/16

sudo sysctl net.bridge.bridge-nf-call-iptables=1

mkdir -p $HOME/.kube

sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config

sudo chown $(id -u):$(id -g) $HOME/.kube/config

kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/v0.10.0/Documentation/kube-flannel.yml


sudo kubectl taint nodes --all node-role.kubernetes.io/master-

# note that ca.crt is here /etc/kubernetes/pki/ca.crt

kubectl create namespace gitlab-managed-apps

kubectl create clusterrolebinding gitlab-deploy --clusterrole=cluster-admin --namespace=gitlab-managed-apps --serviceaccount=default:build-robot

kubectl create clusterrolebinding gitlab-deploy-internal --clusterrole=cluster-admin --namespace=gitlab-managed-apps --serviceaccount=gitlab-managed-apps:default
  1. Fill in the settings in kubernetes integration page.
  2. Install all the required plugins.
  3. Wait for hours and get no ip in Ingress, Ingress controller remain in crashloopback

Example Project

https://gitlab.com/michaellee8/k8s-nodejs-test-01

(If you are using an older version of GitLab, this will also determine whether the bug has been fixed in a more recent version)

What is the current bug behavior?

No IP in Ingress

What is the expected correct behavior?

Give the IP to register with dns

Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's very hard to read otherwise.)

Output of checks

(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)

Results of GitLab environment info

Expand for output related to GitLab environment info 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:env:info)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Edited by 🤖 GitLab Bot 🤖