Holden Karau created YUNIKORN-380: ------------------------------------- Summary: Deploying YUNIKORN 0.9 RC2 on Minikube 1.3.1 results in port conflict Key: YUNIKORN-380 URL: https://issues.apache.org/jira/browse/YUNIKORN-380 Project: Apache YuniKorn Issue Type: Improvement Reporter: Holden Karau
Following the instructions in `README.md` against my currently installed minikube I got: {code:java} holden@hkdesktop:~/yunikron_scratch/apache-yunikorn-0.9.0-incubating-src$ kubectl logs yunikorn-admission-controller-88c5966d9-q672kholden@hkdesktop:~/yunikron_scratch/apache-yunikorn-0.9.0-incubating-src$ kubectl logs yunikorn-admission-controller-88c5966d9-q672k2020-08-23T22:56:23.349Z INFO log/logger.go:86 scheduler configuration, pretty print {"configs": "{\n \"clusterId\": \"my-kube-cluster\",\n \"clusterVersion\": \"0.1\",\n \"schedulerName\": \"yunikorn\",\n \"policyGroup\": \"queues\",\n \"schedulingIntervalSecond\": 1000000000,\n \"absoluteKubeConfigFilePath\": \"\",\n \"loggingLevel\": 0,\n \"logEncoding\": \"console\",\n \"logFilePath\": \"\",\n \"volumeBindTimeout\": 10000000000,\n \"testMode\": false,\n \"eventChannelCapacity\": 1048576,\n \"dispatchTimeout\": 300000000000,\n \"kubeQPS\": 1000,\n \"kubeBurst\": 1000,\n \"predicates\": \"\",\n \"operatorPlugins\": \"general\"\n}"}2020-08-23T22:56:23.349Z INFO webhook/webhook.go:83 the admission controller started {"port": 8443, "listeningOn": ["/mutate", "/validate-conf"]}2020-08-23T22:56:23.349Z FATAL webhook/webhook.go:79 failed to start admission controller {"error": "listen tcp :8443: bind: address already in use"}main.main.func1 /Users/wyang/workspace/apache/yunikorn/incubator-yunikorn-k8shim/pkg/plugin/admissioncontrollers/webhook/webhook.go:79 {code} -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org