Minikube

问题 I am running minikube on OSX(10.11.6). The MiniKube version is v0.32.0 . I tried minikube start and minikube start --vm-driver=virtualbox but nothing happened. minikube logs returns following ending lines: "default" not found' (will not retry!) Jan 01 10:23:28 minikube kubelet[2753]: E0101 10:23:28.041218 2753 kubelet.go:2236] node "minikube" not found Jan 01 10:23:28 minikube kubelet[2753]: E0101 10:23:28.141908 2753 kubelet.go:2236] node "minikube" not found Jan 01 10:23:28 minikube kubelet

问题 I have started to learn Minikube using some of this tutorial and a bit of this one. My plan is to use the "none" driver to use Docker rather than the standard Virtual Box. My purpose is to learn some infra/operations techniques that are more flexible than Docker Swarm. There are a few docker run switches that Swarm does not support, so I am looking at alternatives. When setting this up, I had a couple of false starts, as I did not specify the --vm-driver=none initially, and I had to do a sudo

问题 I have kubernetes + minicube installed (MacOs 10.12.6) installed. But while trying to start the minicube i get constant errors: $: minikube start Starting local Kubernetes v1.10.0 cluster... Starting VM... Getting VM IP address... Moving files into cluster... Setting up certs... Connecting to cluster... Setting up kubeconfig... Starting cluster components... E0601 15:24:50.571967 67567 start.go:281] Error restarting cluster: running cmd: sudo kubeadm alpha phase certs all --config /var/lib

问题 I want to completely purge Minikube so that I could start over as if I installed it for the first time to avoid some configuration clashes. Mailnly to have initial IP 192.168.99.100, unfortunatelly it increases on next minikube start to 192.168.99.101, etc. I've run to delete Minikube: minikube delete rm -rf ~/.minikube rm -rf ~/.kube I'm running minikube version: v0.31.0 on Ubuntu 18.04 with driver VirtualBox 5.2.18 回答1: Minikube is used on different platforms, so it might be helpful to add

问题 I followed Istio's official documentation to setup Istio for sample bookinfo app with minikube. but I'm getting Unable to connect to the server: net/http: TLS handshake timeout error. these are the steps that I have followed(I have kubectl & minikube installed). minikube start curl -L https://git.io/getLatestIstio | sh - cd istio-1.0.3 export PATH=$PWD/bin:$PATH kubectl apply -f install/kubernetes/helm/istio/templates/crds.yaml kubectl apply -f install/kubernetes/istio-demo-auth.yaml kubectl

问题 I'm having trouble connecting to the kubernetes python client even though I'm following the examples here in the api. Basically this line can't connect to the kubernetes client: config.load_kube_config() What I'm doing: I have a Dockerfile file like this that I'm building my image with. This is just a simple python/flask app. FROM python:2 RUN mkdir -p /usr/src/app WORKDIR /usr/src/app COPY requirements.txt /usr/src/app/ RUN pip install --no-cache-dir -r requirements.txt COPY . /usr/src/app

问题 i have a REST application integrated with kubernetes for testing REST queries. Now when i execute a POST query on my client side the status of the job which is automatically created remains PENDING indefinitely. The same happens with the POD which is also created automatically When i looked deeper into the events in dashboard, it attaches the volume but is unable to mount the volume and gives this error : Unable to mount volumes for pod "ingestion-88dhg_default(4a8dd589-e3d3-4424-bc11

问题 I am following with the answer here step 6th. To make my own local minikube cluster of single master and 2 nodes . master names minikube . $ kubeadm version kubeadm version: &version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.3", GitCommit:"721bfa751924da8d1680787490c54b9179b1fed0", GitTreeState:"clean", BuildDate:"2019-02-01T20:05:53Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"} $ kubelet --version Kubernetes v1.13.3 login to the minikube console by minikube ssh Then

问题 Issue: My flask API is unable to connect to my Postgres instance. I've verified that the database and api are both working as expected on their own, the deployments and services are running within kubernetes. It must be the connection itself. The connection is defined inside of the Flask config file so perhaps I'm specifying it incorrectly? I'm at a loss of next steps to take. Error This is the error I see when I check the logs of the pod specific to the API which is trying to reach out to

问题 I'm using a vanilla minikube environment. I'm not specifying any service account-related instructions in my bare-bones simple Pod .yaml file. Inside a deployed Pod, /var/run/secrets/kubernetes.io/serviceaccount/token is empty. What are the possible causes for this? 回答1: As mentioned in the docs In version 1.6+, you can opt out of automounting API credentials for a service account by setting automountServiceAccountToken: false on the service account: apiVersion: v1 kind: ServiceAccount