Minikube

问题 I have a Spring Boot application that I'm trying to test in Minkube, which should connect to MongoDb Atlas. It connects to my database when running the application on my pc, it also connects after creating and running as a Docker image, running on a Ubuntu VM on my PC. It does not connect to Mongodb Atlas when running as a Kubernetes deployment on Minikube. There must be a configuration step im missing, but i just dont know what. I think my question is "Do i need to do anything special to

问题 Am using minikube to test out the deployment and was going through thislink And my manifest file for deployment is like apiVersion: extensions/v1beta1 kind: Deployment metadata: name: webapp spec: replicas: 1 template: metadata: labels: app: webapp spec: containers: - name: webapp imagePullPolicy: Never # <-- here we go! image: sams ports: - containerPort: 80 and after this when i tried to execute below commands got output user@usesr:~/Downloads$ kubectl create -f mydeployment.yaml --validate

问题 Does anyone know if there is a specific way to configure Kubernetes to allow resolution of SRV type URLs (to internet services) from within pods? Recently had a problem preventing me from connecting to MongoDB Atlas. Found the cause to be the use of SRV type URI for connection, was fixed after using legacy URI for connection (link to description). Is there some configuration required? 回答1: Some of the images like Alpine does not support the srv strings. Instead if you want to make it run

问题 I am using spark 2.4.4. Having trouble running spark-submit on my ubuntu machine with the following config and system environment: cpchung:small$ minikube start --kubernetes-version=1.17.0 😄 minikube v1.6.2 on Ubuntu 19.10 ✨ Selecting 'kvm2' driver from user configuration (alternates: [virtualbox none]) 💡 Tip: Use 'minikube start -p <name>' to create a new cluster, or 'minikube delete' to delete this one. 🏃 Using the running kvm2 "minikube" VM ... ⌛ Waiting for the host to be provisioned ...

问题 I am using spark 2.4.4. Having trouble running spark-submit on my ubuntu machine with the following config and system environment: cpchung:small$ minikube start --kubernetes-version=1.17.0 😄 minikube v1.6.2 on Ubuntu 19.10 ✨ Selecting 'kvm2' driver from user configuration (alternates: [virtualbox none]) 💡 Tip: Use 'minikube start -p <name>' to create a new cluster, or 'minikube delete' to delete this one. 🏃 Using the running kvm2 "minikube" VM ... ⌛ Waiting for the host to be provisioned ...

问题 I have a local minikube installation. I want to change the authentication mechanism for the api-server and restart and test it out. All the documentation I have read lacks this information. Has anybody got experience in it. Thanks in Advance. 回答1: Yes you can. The kubernetes API Server, Controller manager, and scheduler are all run as static manifests in minikube. So, in fact, in your example: Any change to the manifest will automatically lead to them being restarted instantly. In order to

问题 When I run my docker container using Docker Desktop for Windows I am able to connect to it using docker run -p 5051:5000 my_app http://0.0.0.0:5051 However when I open another terminal and do this minikube docker-env | Invoke-Expression and build and run the same container using the same run command as above I cannot connect to the running instance. Should I be running and testing the containers using Docker Desktop, then using minikube to store the images only (for Kubernetes)? Or can you

问题 Today randomly minikube seems to be taking very long to respond to command via kubectl . And occasionally even: kubectl get pods Unable to connect to the server: net/http: TLS handshake timeout How can I diagnose this? Some logs from minikube logs : ==> kube-scheduler <== I0527 14:16:55.809859 1 serving.go:319] Generated self-signed cert in-memory W0527 14:16:56.256478 1 authentication.go:387] failed to read in-cluster kubeconfig for delegated authentication: open /var/run/secrets/kubernetes

问题 Today randomly minikube seems to be taking very long to respond to command via kubectl . And occasionally even: kubectl get pods Unable to connect to the server: net/http: TLS handshake timeout How can I diagnose this? Some logs from minikube logs : ==> kube-scheduler <== I0527 14:16:55.809859 1 serving.go:319] Generated self-signed cert in-memory W0527 14:16:56.256478 1 authentication.go:387] failed to read in-cluster kubeconfig for delegated authentication: open /var/run/secrets/kubernetes

问题 I'm creating a HorizontalPodAutoscaler in Kubernetes and I need to configure the downscale stabilization window to be smaller than the default. The code used and error are below: apiVersion: autoscaling/v2beta2 kind: HorizontalPodAutoscaler metadata: name: busy-autoscaler spec: behavior: scaleDown: stabilizationWindowSeconds: 10 scaleTargetRef: apiVersion: apps/v1 kind: Deployment name: busy-worker minReplicas: 1 maxReplicas: 2 metrics: - type: Resource resource: name: cpu target: type: