Minikube

Here's the full error Unable to connect to the server: dial tcp [::1]:8080: connectex: No connection could be made because the target machine actively refused it. Here's my Kubectl config view apiVersion: v1 clusters: [] contexts: - context: cluster: "" user: "" name: dev current-context: dev kind: Config preferences: {} users: [] I'm running Minikube start . It's stuck on Starting VM... In Hyper-V Manager, I have minikube VM running. Check out " Minikube on Windows 10 with Hyper-V " by Jock Reed The command to run, from a Windows CMD console as Administrator, is: minikube start --vm-driver

1）创建服务 编辑gwp-svc.yaml apiVersion: v1 kind: Service metadata: name: gwp spec: ports: - port: 80 targetPort: 8080 selector: app: gwp 创建服务 kubectl create -f gwp-svc.yaml 查看服务 kubectl get svc 在运行的容器中远程执行命令，其中两个双斜杠（--）代表着kubectl命令项的结束，之后时pod内部需要执行的命令 kubectl exec gwp-fgjg6 -- curl -s http://10.98.20.174 同一个服务可以暴露多个端口，此时需要指定端口名称 编辑gwp-svc.yaml apiVersion: v1 kind: Service metadata: name: gwp spec: ports: - name: http port: 80 targetPort: 8080 - name: https port: 443 targetPort: 8443 selector: app: gwp 此外，targetPort还可以使用命名端口（就是pod中配置的containerPort对应的名称），最大的好处是即使更换端口号也无须更改服务spec。 2）服务发现 通过环境变量发现服务

So I've been playing around with Minkube. I've managed to deploy a simple python flask container: PS C:\Users\Will> kubectl run test-flask-deploy --image 192.168.1.201:5000/test_flask:1 deployment "test-flask-deploy" created I've also then managed to expose the deployment as a service: PS C:\Users\Will> kubectl expose deployment/test-flask-deploy -- type="NodePort" --port 8080 service "test-flask-deploy" exposed In the dashboard I can see that the service has a Cluster IP: 10.0.0.132. I access the dashboard on a 192.168.xxx.xxx address, so I'm hoping I can expose the service on that external

Basically I am trying to do is play around with pod lifecycle and check if we can do some cleanup/backup such as copy logs before the pod terminates. What I need : Copy logs/heapdumps from container to a hostPath/S3 before terminating What I tried: I used a preStop hook with a bash command to echo a message (just to see if it works !!). Used terminationGracePeriodSeconds with a delay to preStop and toggle them to see if the process works. Ex. keep terminationGracePeriodSeconds:30 sec (default) and set preStop command to sleep by 50 sec and the message should not be generated since the

I am running kubernetes on minikube, I am behind a proxy, so I had set the env variables(HTTP_PROXY & NO_PROXY) for docker in /etc/systemd/system/docker.service.d/http-proxy.conf. I was able to do docker pull but when I run the below example kubectl run hello-minikube --image=gcr.io/google_containers/echoserver:1.4 --port=8080 kubectl expose deployment hello-minikube --type=NodePort kubectl get pod pod never starts and I get the error desc = unable to pull sandbox image \"gcr.io/google_containers/pause-amd64:3.0\" docker pull gcr.io/google_containers/echoserver:1.4 works fine I was able to fix

Is it enabled by default? How could I set up an example audit log? I've tried: minikube start --extra-config=apiserver.Authorization.Mode=RBAC --extra-config=apiserver.Audit.LogOptions.Path=/var/log/apiserver/audit.log --extra-config=apiserver.Audit.LogOptions.MaxAge=30 --extra-config=apiserver.Audit.LogOptions.MaxSize=100 --extra-config=apiserver.Audit.LogOptions.MaxBackups=5 I'm also busy reading through (trying out all the options might take a while as minikube start ... is not a quick process): https://github.com/kubernetes/minikube/issues/1609 As far as I know and as per all available