kubernetes-release | BOSH release for Kubernetes | Continous Integration library

You need to add the docker repo to yum config manager first.

https://docs.docker.com/engine/install/centos/

The answer is that

As you thought you are right in case of using VM and that be easy to test it out.

Instead of setting up Kubernetes on docker you can use Linux base container for development testing.

There is linux container available name as LXC container. Docker is kind of application container while in simple words LXC is like VM for local development testing. you can install the stuff into rather than docker setting up application inside image.

read some details about lxc : https://medium.com/@harsh.manvar111/lxc-vs-docker-lxc-101-bd49db95933a

you can also run it on windows and try it out at : https://linuxcontainers.org/

If you have read the documentation of Kubeflow there is also one option multipass

Multipass creates a Linux virtual machine on Windows, Mac or Linux systems. The VM contains a complete Ubuntu operating system which can then be used to deploy Kubernetes and Kubeflow.

Learn more about Multipass : https://multipass.run/#install

Try adding securityContext in your deployment

You have 2 solution

1. Escape the double quote "

There's probably a better way to do it, but I got it working by adding: -Dmaven.repo.local=/home/jenkins/.m2/repository, so:

/bin/sh: illegal option -

is because you have a space after the -c, which the arg parser interprets as /bin/sh "- " -- ironically(?) your golang snippet is correct, but the parts of your code you pasted and the crux of your question shows the wrong syntax

One can trivially reproduce this without involving busybox or whatever

Looks like this was something to do in the kubectl apply task in release pipeline. We have to go to right pane, scroll down, expand "advanced" and in version spec check the box "check for latest version". My pipeline built completed successfully. There was no issues in my deployment yaml.

Enabling this option ensures proper latest version of kubectl.exe is downloaded onto the VSTS agent

Installed kubectl on the server

You need kubectl on machine, from which you're going to access your cluster. If you installed it on the server and you ran kubectl proxy on the server - then you can access the proxy only from your server (depends on your network config).

If you do curl http://localhost:8001/api on the server - it will work.

So, you need to install kubectl on your machine, set up the k8s context for it and then run kubectl proxy - after that, all requests to proxy will be forwarded to your cluster.

In each request to k8s API server you need to be authenticated, when you run kubectl proxy - basically proxy will take care of authentication and SSL/TLS related stuff.

Read this for more info: Use an HTTP Proxy to Access the Kubernetes API and The Kubernetes API

Configure Access to Multiple Clusters - may also be useful

So basically you need to do the following:

Note: These should be done directly on your local machine, and not on the server or the terminal connecting to the server, but directly on your local machine:

Install the gcloud SDK: