Kubernetes Download No Docker

We can use the command shown below: k expose pod nginx --typeNodePort servicenginx exposed If we visit the Dashboard at this point and go to the Services section, we can see our nginx service entry.

What this is not This is not a tutorial or an article about what is Docker or what is Kubernetes.

Kubernetes Download No Docker

There is plenty of literature on those topics on the internet e.g: Docker intro from the official docs (always a good place to start): Kubernetes intro from the official docs: Another good one about Docker: A nice online course about Kubernetes from Edx: Introduction to Kubernetes Docker Desktop download No Docker Hub option If you dont have a Docker account already If you are not planning to publish container images If you prefer not to share your email address Get the macOS Installer.dmg directly here - Here for the Edge version - Docker Hub option If you use the standard Docker links, for example: They will kindly invite you to Sign In into Docker Hub, that will enable the download link, allow you to publish containers to Docker Hub, etc.

You can also do this step after the installation: Select Sign in Create Docker ID from the Docker Desktop menu to access your Docker Hub account.

Once logged in, you can access your Docker Hub repositories directly from the Docker Desktop menu.

Docker Desktop installation Double-click Docker.dmg to open the installer, then drag the Docker icon to the Applications folder.

Cmd Space and type Docker, you should be able to see the Docker app there, just hit Enter to open it 3.

Simply check on the Enable Kubernetes option and then hit the Apply Restart button as shown below: Create a Kubernetes cluster as easy as check one checkbox This will display a loading spinner while the Kubernetes cluster gets installed.

Please be patient since this could take a while depending on your network.

When the installation is done you should see the same screen: Note the two messages at the bottom of the window mentioning: Docker is running Kubernetes is running Congratulations You now have the following: A standalone Kubernetes server and client, as well as Docker CLI integration.

The Kubernetes server is a single-node cluster and is not configurable.

If you check you About Docker, you should see something similar to: Check our installation Let us try out a few things to ensure that we can make sense of what has got installed.

I am using kubectl from my gCloud SDK tools and Docker for Mac, when it launched the Kubernetes cluster has been able to set the cluster context for the kubectl utility for you.

Tip: In case you switch between different clusters, you can always get back using the following: kubectl config use-context docker-for-desktop Switched to context docker-for-desktop Let us get some information on the cluster.

Let us check out the nodes in the cluster: kubectl get nodes NAME STATUS ROLES AGE VERSION docker-desktop Ready master 21h v1.15.5 Installing the Kubernetes Dashboard The next step that we need to do here is to install the Kubernetes Dashboard.

It could take some time to change from ContainerCreating to Running, so be patient.

Once it is in running state, to access Dashboard from your local workstation you must create a secure channel to your Kubernetes cluster.

Kubectl Proxy kubectl proxy creates a proxy server between your machine and Kubernetes API server.

By default, it is only accessible locally (from the machine that started it).

Now access you can access Dashboard at::kubernetes-dashboard:proxy You will see the following screen: Login page for Kubernetes Dashboard To find a valid token here you have a useful one-liner kubectl -n kube-system describe secret (kubectl -n kube-system get secret awk deployment-controller-token-print 1) awk 1token:print 2 eyJhbGciOiJSUzI1NiIsImtpZCI6IiJ9.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlLXN5c3RlbSIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJkZXBsb3ltZW50LWNvbnRyb2xsZXItdG9rZW4tZnp3NzgiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC5uYW1lIjoiZGVwbG95bWVudC1jb250cm9sbGVyIiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZXJ2aWNlLWFjY291bnQudWlkIjoiOWJmOGE4ZDAtZDg1Ny00YzBlLThmNzktZDk3MDEyZDBjMjU5Iiwic3ViIjoic3lzdGVtOnNlcnZpY2VhY2NvdW50Omt1YmUtc3lzdGVtOmRlcGxveW1lbnQtY29udHJvbGxlciJ9.H6nQYQ1ltSHUTddNgUjpRHKe82hC-ipL0S08lK90rWE0hZir9fq1H9LhEyjSgt3QVIYCEiG8qiIqkQO0I2dvQNCbQHnLl6dmhlrn7astFdu2F621plNQaC6MHfL5YTsTfJEER2sx5qDuEgtZXobWQ8-64w2d6RfHEIFZIxmno8Oj7XccjfBv12p74qyleJYIOBSuglaHyOx8RaDROCkW0OR-9DHa4zlcU28YqW83J3ynxjwqPvuQzUc5xcycUk1nEfjWZORjH9A1DQdj5DNud7g1PaHHQZ50LBjIWKmwNLF7CSA-goCPfWFfcCgHANhFAfGYeU5sKWz9g Copy paste that token into the field and click Sign In to login, the dashboard will show as below: Lets Play Let us proceed now to running a simple Nginx container to see the whole thing in action: First things first, setup your command line for productivity: Kubectl autocomplete Bash source Zsh source 2.

Alias for kubectl Alias to type less (lazy is good) and it will also work with completion: alias kkubectl complete -F startkubectl k Now lets create our first namespace: k create namespace my-demo namespacemy-demo created To easy work within our new context lets make it the default: kubectl config set-context current namespacemy-demo TIP: create an alias with this, to be able to check contexts easily: alias knkubectl config set-context current namespace so now you can do kn my-demo or kn default We are going to use the run command as shown below: k run nginx --imagenginx --port80 --restartNever This creates a Pod ( ) and we can investigate into the Pod that gets created, which will run the container: k get pods NAME READY STATUS RESTARTS AGE nginx 01 ContainerCreating 0 4s You can see that the STATUS column value is ContainerCreating.

If we wait for a while, the Pod will eventually get created and it will ready as the command below shows: k get pods NAME READY STATUS RESTARTS AGE nginx 11 Running 0 14s Now, let us go back to the Dashboard and get to the Pods via the Pods link in the Workloads as shown below: Click on the Pod and you can get various details on it as given below: You can see that it has been given some default labels.

There are some interesting links that you will find on this page as shown below, via which you can directly EXEC into the pods or see the logs too.

View Logs and EXEC into pod buttons We could have got the Node and Pod details via a variety of kubectl describe nodepod commands and we can still do that.