Блог

При попытке использовать расширение VS Code для моста Kubernetes, настроив задачи.json следующим образом:

     "version": "2.0.0",
    "tasks": [
        {
            "label": "bridge-to-kubernetes.service",
            "type": "bridge-to-kubernetes.service",
            "service": "frontend",
            "ports": [
                8080
            ],
            "targetCluster": "minikube",
            "targetNamespace": "ecomm-ns"
        }
    ]
}
 

И мой launch.json как

             "name": "Launch Package with Kubernetes",
            "type": "go",
            "request": "launch",
            "mode": "debug",
            "program": "${workspaceFolder}",
            "env": {
                "GOOGLE_APPLICATION_CREDENTIALS": "somepath/ecomm-key.json",
            },
            "preLaunchTask": "bridge-to-kubernetes.service"
        }
 

Я получаю следующий вывод:

 Target cluster: minikube
Current cluster: minikube
Target namespace: ecomm-ns
Current namespace: ecomm-ns
Target service name: frontend
Target service ports: 8080


Error: Failed to load current kubeconfig. Please confirm that your kubeconfig is valid.

The terminal process terminated with exit code: 1.
 

Kkubectl config view выдает правильный вывод

Просматривая журналы плагина bridge, я обнаружил следующее:

 2021-02-02T07:40:18.1876210Z | Library | WARNG | Failed to load kubeconfig at '/Users/scaucheteux/.kube/config': (Line: 10, Col: 5, Idx: 1804) - (Line: 10, Col: 6, Idx: 1805): Expected 'MappingStart', got 'SequenceStart' (at Line: 10, Col: 5, Idx: 1804).
 

Моя конфигурация kubeconfig выглядит нормально и корректно обрабатывается различными плагинами yaml и kubectl:

 apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: LS0tLS1CRUdJTiBDRVJ
    server: https://35.205.91.182
  name: gke_sca-ecommerce-291313_europe-west1-b_ecomm-demo
- cluster:
    certificate-authority: /Users/someuser/.minikube/ca.crt
    extensions:
    - extension :
        last-update: Mon, 01 Feb 2021 15:27:30 CET
        provider: minikube.sigs.k8s.io
        version: v1.17.1
      name: cluster_info
    server: https://127.0.0.1:55000
  name: minikube
contexts:
- context:
    cluster: gke_sca-ecommerce-291313_europe-west1-b_ecomm-demo
    namespace: ecomm-ns
    user: gke_sca-ecommerce-291313_europe-west1-b_ecomm-demo
  name: gke_sca-ecommerce-291313_europe-west1-b_ecomm-demo
- context:
    cluster: minikube
    extensions:
    - extension:
        last-update: Mon, 01 Feb 2021 15:27:30 CET
        provider: minikube.sigs.k8s.io
        version: v1.17.1
      name: context_info
    namespace: ecomm-ns
    user: minikube
  name: minikube
current-context: minikube
kind: Config
preferences: {}
users:
- name: gke_sca-ecommerce-291313_europe-west1-b_ecomm-demo
  user:
    auth-provider:
      config:
        access-token: ya29.A0A
        cmd-args: config config-helper --format=json
        cmd-path: /Users/someuser/Devs/gcloud/google-cloud-sdk/bin/gcloud
        expiry: "2021-02-01T18:23:02Z"
        expiry-key: '{.credential.token_expiry}'
        token-key: '{.credential.access_token}'
      name: gcp
- name: minikube
  user:
    client-certificate: /Users/someuser/.minikube/profiles/minikube/client.crt
    client-key: /Users/someuser/.minikube/profiles/minikube/client.key
 

Прочитайте где-нибудь еще удаление расширений исправляет это для minikube https://github.com/microsoft/mindaro/issues/111