ecomm-integration-ballerina/kubernetes-cluster

Kubernetes cluster using Vagrant, VirtualBox and Kubeadm

kubernetes-cluster's Issues

Node status says not ready

Setup completed successfully, the deployment also get schedule but when checking for node status it says not ready 
--------------------
vagrant@k8s-head:~$ kubectl run hello-minikube --image=k8s.gcr.io/echoserver:1.4 --port=8080
kubectl run --generator=deployment/apps.v1 is DEPRECATED and will be removed in a future version. Use kubectl run --generator=run-pod/v1 or kubectl create instead.
deployment.apps/hello-minikube created
vagrant@k8s-head:~$ kubectl expose deployment hello-minikube --type=NodePort
service/hello-minikube exposed
vagrant@k8s-head:~$ kubectl get services
NAME             TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)          AGE
hello-minikube   NodePort    10.105.24.159   <none>        8080:30285/TCP   13s
kubernetes       ClusterIP   10.96.0.1       <none>        443/TCP          7m32s
vagrant@k8s-head:~$ kubectl get nodes
NAME         STATUS     ROLES    AGE     VERSION
k8s-head     NotReady   master   8m15s   v1.16.3
k8s-node-1   NotReady   <none>   5m47s   v1.16.3
k8s-node-2   NotReady   <none>   3m23s   v1.16.3

k8s-head: Failed to restart kubelet.service: Unit kubelet.service not found

$vagrant up
8s-head: Err:8 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 Packages
k8s-head: server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
k8s-head: Ign:9 https://packages.cloud.google.com/apt kubernetes-xenial/main all Packages
k8s-head: Ign:10 https://packages.cloud.google.com/apt kubernetes-xenial/main Translation-en_US
k8s-head: Ign:11 https://packages.cloud.google.com/apt kubernetes-xenial/main Translation-en
k8s-head: Reading package lists...
k8s-head: W: The repository 'http://apt.kubernetes.io kubernetes-xenial Release' does not have a Release file.
k8s-head: E: Failed to fetch https://packages.cloud.google.com/apt/dists/kubernetes-xenial/main/binary-amd64/Packages server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
k8s-head: E: Some index files failed to download. They have been ignored, or old ones used instead.
k8s-head: Reading package lists...
k8s-head: Building dependency tree...
k8s-head:
k8s-head: Reading state information...
k8s-head: E: Unable to locate package kubelet
k8s-head: E: Unable to locate package kubeadm
k8s-head: E: Unable to locate package kubectl
k8s-head: E: Unable to locate package kubelet
k8s-head: E: Unable to locate package kubeadm
k8s-head: E: Unable to locate package kubectl
k8s-head: E: No packages found
k8s-head: sed: can't read /etc/default/kubelet: No such file or directory
k8s-head: Failed to restart kubelet.service: Unit kubelet.service not found.
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

is the repo missing ./kubeadm_join_cmd.sh?

(Reading database ... 54568 files and directories currently installed.)
    k8s-node-2: Preparing to unpack .../sshpass_1.05-1_amd64.deb ...
    k8s-node-2: Unpacking sshpass (1.05-1) ...
    k8s-node-2: Processing triggers for man-db (2.7.5-1) ...
    k8s-node-2: Setting up sshpass (1.05-1) ...
    k8s-node-2: ssh: connect to host 192.168.205.10 port 22: No route to host
    k8s-node-2: sh: 0:
    k8s-node-2: Can't open ./kubeadm_join_cmd.sh
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

Fixed API 1.6 problem and other issues + cleanup

Hi,

First of all, I want to thank you for your project. I started working on it to play with the Kubernetes cluster. However, I needed to do some fixes to the code to run it on Kubernetes 1.7 (i.e. adapt to 1.6 API for an example). I also move the configuration script outside Vagrantfile to clean up the code. Moreover, I separate the servers configuration from Vagrantfile.
The code changed is here:
https://github.com/sasadangelo/k8s-cluster

I didn't create a pull request because I noticed there are three PR not merged in your queue and probably this means the project is abandoned. If you want I can create a PR if you think my fixes are ok. Feel free to contact me.

on windows

Succes on ubutnu !! but I am not able to create it on windows :(

Stderr: VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

Trying to deploy application to kubernetes

Hi I have a application im trying to automatically deploy onto the k8 instance you deploy using your script. I can get this deployed using vagrant I just cant get it to deploy the app. I have posted the change i made to your file but it executes the master and node and nothing else. Any ideas? how can I execute more command after master and node have been deployed?

        # we cannot use this because we can't install the docker version we want - https://github.com/hashicorp/vagrant/issues/4871
        #config.vm.provision "docker"
		config.vm.provision "shell", inline: $configureBox

        if opts[:type] == "master"
            config.vm.provision "shell", inline: $configureMaster
        elsif opts[:type] == "node"
            config.vm.provision "shell", inline: $configureNode
		else
			config.vm.provision "shell", inline: $deployMaster
		end
		
	end

end
end

Any help mych appreciated am new to vagrant just looking to automate as much as possible.

Whats the Sudo password

What is the sudo password?

How to access kubectl dashboard?

Sup mate,

thanks for the vagrant, it's really helpful to me.

this is what I tried:

• vagrant ssh k8s-head
• once inside, kubectl proxy
• added 8001 to 8001 port to proxy forwarding on k8s-head NAT
• tried wget 127.0.0.1 from host, it connects but get no html

ps: wget 127.0.0.1 8001 works from inside the machine, it gets the index.html.

Is there a more correct way to access the dashboard?

Thanks,
Luca

Should upgrate to new 1.16 APIS

You can migrate the existing APIS like apps/v1beta1 to apps/v1 and others stuffs

Otherwise these yaml won't work from 1.16 version of K8s.

please refer to:
https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/

Error concerning calico.yaml

When I try to deploy the environment, I get error:

k8s-head: unable to recognize "https://raw.githubusercontent.com/ecomm-integration-ballerina/kubernetes-cluster/master/calico/calico.yaml": no matches for kind "Deployment" in version "apps/v1beta1"
k8s-head: unable to recognize "https://raw.githubusercontent.com/ecomm-integration-ballerina/kubernetes-cluster/master/calico/calico.yaml": no matches for kind "DaemonSet" in version "extensions/v1beta1"

Does anyone else also encounter this issue ?