我有一个实验流水线,使用: Jenkins,minikube,以及用于窗口的码头。docker和Jenkins都是在windows启动时启动的,然后我开始使用
小型起跑
在这个过程中,我得到了命令bat "kubectl apply -f deployment.yaml"。
Unable to connect to the server: dial tcp [::1]:8080: connectex: No connection could be made because the target machine actively refused it.但是,当我在power shell中运行相同的命令时,它将正确运行。在power shell中,运行命令kubectl config get -也会得到
CURRENT NAME CLUSTER AUTHINFO NAMESPACE
docker-desktop docker-desktop docker-desktop
docker-for-desktop docker-desktop docker-desktop
* minikube minikube minikube当我运行kubectl config view,来自power 的时,我得到
apiVersion: v1 clusters:
- cluster:
certificate-authority-data: DATA+OMITTED
server: https://kubernetes.docker.internal:6443 name: docker-desktop
- cluster:
certificate-authority: C:\Users\shady1\.minikube\ca.crt
**server: https://127.0.0.1:32768** name: minikube contexts:
- context:
cluster: docker-desktop
user: docker-desktop name: docker-desktop
- context:
cluster: docker-desktop
user: docker-desktop name: docker-for-desktop
- context:
cluster: minikube
user: minikube name: minikube current-context: minikube kind: Config preferences: {} users:
- name: docker-desktop user:
client-certificate-data: REDACTED
client-key-data: REDACTED
- name: minikube user:
client-certificate: C:\Users\shady1\.minikube\profiles\minikube\client.crt
client-key: C:\Users\shady1\.minikube\profiles\minikube\client.key当我运行kubectl config view,Jenkins管道的时,我得到
apiVersion: v1
clusters: null
contexts: null
current-context: ""
kind: Config
preferences: {}
users: null有什么提示吗?
发布于 2020-09-19 13:30:46
添加环境变量KUBECONFIG=C:\Users\shady1.kube\config解决了这个问题
https://stackoverflow.com/questions/63968246
复制相似问题