Minikube

delete kubernetes cluster on docker-for-desktop OSX

由 眉间皱痕 提交于 2019-12-22 03:22:31
问题 What is the equivalent command for minikube delete in docker-for-desktop on OSX As I understand, minikube creates a VM to host its kubernetes cluster but I do not understand how docker-for-desktop is managing this on OSX. 回答1: Tear down Kubernetes in Docker for OS X is quite an easy task. Go to Preferences , open Reset tab, and click Reset Kubernetes cluster . All object that have been created with Kubectl before that will be deleted. You can also reset docker VM image ( Reset disk image )

Connect to local database from inside minikube cluster

由 徘徊边缘 提交于 2019-12-21 17:19:10
问题 I'm trying to access a MySQL database hosted inside a docker container on localhost from inside a minikube pod with little success. I tried the solution described Minikube expose MySQL running on localhost as service but to no effect. I have modelled my solution on the service we use on AWS but it does not appear to work with minikube. My service reads as follows apiVersion: v1 kind: Service metadata: name: mysql-db-svc namespace: external spec: type: ExternalName ExternalName: 172.17.0.2 ..

Jenkins service always pending on minikube

由 帅比萌擦擦* 提交于 2019-12-21 11:01:15
问题 I installed minikube on local. Dashboard is 192.168.99.100:30000 I installed Jenkins by helm: $ helm install stable/jenkins Then the service always pending: $ kubectl get services --namespace=default -w wandering-buffoon-jenkins NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE wandering-buffoon-jenkins 10.0.0.153 <pending> 8080:31326/TCP,50000:31090/TCP 26m Why? So can't use external-ip to access it. 回答1: I'm guessing that you didn't update the parameters to use NodePort instead of the default

Minikube not working in Windows 8

由 痞子三分冷 提交于 2019-12-21 09:18:29
问题 I'm new to Kubernetes. With the help of Kubernetes documentation , I installed minikube (v0.24.1) and kubectl in my Windows machine. VirtualBox(Version 5.1.18) is also installed in my machine. Before starting the minikube , i have executed set HTTP_PROXY=xx.xx.xx:8080 and set NO_PROXY=localhost,127.0.0.0/8,192.0.0.0/8 in Windows command prompt Started minikube by passing Proxy Details : C:\minikube>minikube start --memory 4096 --vm-driver=virtualbox --docker-env http_proxy=xx.xx.xx:8080 -

Expose port in minikube

由 ≡放荡痞女 提交于 2019-12-20 08:57:16
问题 In minikube, how to expose a service using nodeport ? For example, I start a kubernetes cluster using the following command and create and expose a port like this: $ minikube start $ kubectl run hello-minikube --image=gcr.io/google_containers/echoserver:1.4 --port=8080 $ kubectl expose deployment hello-minikube --type=NodePort $ curl $(minikube service hello-minikube --url) CLIENT VALUES: client_address=192.168.99.1 command=GET real path=/ .... Now how to access the exposed service from the

Kubernetes POD arguments are not passing to service, however Docker arguments are passing correctly

由 丶灬走出姿态 提交于 2019-12-20 05:40:32
问题 Problem Statement: I have a created a Docker image successfully from docker.io/joethecoder2/spring-boot-web . It has been tested with command line arguments, and those work correctly locally with Docker. I am trying to pass java arguments that are passed to Docker to a Kubernetes POD that is defined with a single image docker.io/joethecoder2/spring-boot-web The purpose of passing the arguments is to let the POD know what the IP address and port number are for the database service. Problem

Kubernetes入门篇

由 左心房为你撑大大i 提交于 2019-12-17 19:47:39
【推荐】2019 Java 开发者跳槽指南.pdf(吐血整理) >>> 前言 随着越来越多的公司使用Kubernetes作为它们运行应用的最佳平台，Kubernetes帮助企业标准化了无论是云端部署还是内部部署的应用交付方式；作为研发人员我们还是很有必要去了解其使用方式，了解其内部机制，接下来的一段时间准备通过阅读 <Kubernetes in Action> 来更多的了解Kubernetes。 Docker安装 1.删除旧版本 因为最早之前安装使用过docker，后面一段时间都没有用过，而Docker从17.03开始分为docker-ce(社区版)和docker-ee(企业版)，所以先要删除本地的旧版本； # 移除掉旧的版本 sudo yum remove docker \ docker-client \ docker-client-latest \ docker-common \ docker-latest \ docker-latest-logrotate \ docker-logrotate \ docker-selinux \ docker-engine-selinux \ docker-engine # 删除所有旧的数据 sudo rm -rf /var/lib/docker 2.安装依赖 docker依赖devicemapper存储类型，逻辑卷管理lvm2； sudo

External ip for kubernetes shows <nodes> in minikube

由 蹲街弑〆低调 提交于 2019-12-14 03:40:45
问题 I am fairly new to Kubernetes and I have recently exposed a service using miniKube using NodePort type. I want to test the running of my application but I dont see any external ip but the port only. Here is the output of my: $kubectl get service NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE kubernetes 10.0.0.1 <none> 443/TCP 1h kubernetes-bootcamp 10.0.0.253 <nodes> 8080:31180/TCP 20m $kubectl describe services/kubernetes-bootcamp Name: kubernetes-bootcamp Namespace: default Labels: run=kubernetes

kubectl adding extra env variable to pod

由 荒凉一梦 提交于 2019-12-13 07:40:49
问题 Ok here is the story: I am using minikube to host my application: 1 pod running redis (redis on ubuntu:14.04) 1 pod running my php application (php7-apache) I realised that if I setup my redis pod first then my php pod, my php pod will have these extra env variables: REDIS_SERVICE_PORT=6379 REDIS_PORT_6379_TCP_ADDR=10.0.0.229 REDIS_PORT_6379_TCP_PORT=6379 REDIS_PORT_6379_TCP=tcp://10.0.0.229:6379 REDIS_PORT=tcp://10.0.0.229:6379 REDIS_SERVICE_HOST=10.0.0.229 These variables override the port

Istio RouteRule based on headers user-agent doesn't work

由 风流意气都作罢 提交于 2019-12-13 04:45:33
问题 I have two services running on minikube, Foo and Bar . When I'm accessing the Foo service it makes a request to Bar service to retrieve some data. Bar service have 2 versions "1.0" and "2.0" . I have setup the default RouteRule configuration with istio to route all the requests to "1.0" : apiVersion: config.istio.io/v1alpha2 kind: RouteRule metadata: name: bar-default spec: destination: name: bar-server precedence: 1 route: - labels: version: "1.0" It works fine, and I can see that all the
订阅 Minikube