Nocalhost is Cloud Native Dev Environment.

What happened: 如图点击 add cluster ，添加完成后，会提示 unable to connect。 我查看日志，发现是读取ca.pem文件路径不对（以前第一次使用比较久以前的版本是可以的，现在忘了具体是哪个版本了），于是我通过paste as text 添加，这一步我修改了我的默认配置中的ca文件目录为绝对路径如/users/nero/.kube/ca.pem，然后 连接成功了，但是k8s中的所有资源都不能正常加载。。。 如 我本身kubectl 可以正常使用：

我发现的问题：

1. add cluster 添加时，会存在ca.pem配置文件路径问题
2. 不知道啥原因，连接上k8s api server后，功能使用异常

Environment:

• Macos 11.4 (20F71)
• nhctl version v0.5.1
• kubectl version

Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.7", GitCommit:"1dd5338295409edcfff11505e7bb246f0d325d15", GitTreeState:"clean", BuildDate:"2021-01-13T13:23:52Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"darwin/amd64"} Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.10", GitCommit:"98d5dc5d36d34a7ee13368a7893dcb400ec4e566", GitTreeState:"clean", BuildDate:"2021-04-15T03:20:25Z", GoVersion:"go1.15.10", Compiler:"gc", Platform:"linux/amd64"}

我的开发工具是IntelliJ Idea，使用了nocalhost来调试远程k8s上的应用，点击了Remote Debug以后，控制台输出日志，显示一直处于Waiting pod to start...，Dev Config是参照文档中配置的，配置是 。 debug.sh配置是 。 控制台日志是 这是什么问题呢？

What would you like to be added: I wish Development env Support envFrom

Why is this needed: The environment variables we use online are all in configmap, That's too much. Manual migration to Env is too complicated for me.

What would you like to be added: add support for auth provider for azure ad

Why is this needed: our cluster auth is managed by azure ad, we try to connect cluster, it give error as below: Please check if your cluster or kubeconfig is valid, Error: : no Auth Provider found for name "azure"

What happened: My app workload type is statefulset. I use goland and nocalhost plugin to start remote dev. When I click the button "Run"（nocalhost run config)， the comand is like "nhctl exec test --deployment test-my-operator --controller-type statefulset --command /bin/zsh --command -c --command "go run cmd/my-operator/ma in.go" --kubeconfig ~/.nh/intellij-plugin/kubeConfigs/d9ca5ba8-5a30-4dec-a2c9-d8ba313f0218_config --namespace default "，and the return error is " deployments.apps "test-my-operator" not found"

What you expected to happen: No error returned.

How to reproduce it (as minimally and precisely as possible): App workload type is statefulset and start remote dev by click "Run"(run configured as nocalhost need)

Anything else we need to know?: The func ListPodsByDeployment only handle deployment resource.

Environment:

• OS (e.g: Macos 10.15.5 (19F96) or Windows 10): macOS 11.5.1
• nhctl version (use nchtl version command): 0.5.1(0.5.4 is also the same)
• helm version (use helm version command): none
• kubectl version (use kubectl version command):
• Others: nocalhost plugin version 0.5.1-211
• IDE: GoLand 2021-01

What happened: I create cluster from nocalhost web ui, then i add gcp kube config , it reported "KubeConfig parse error"

What you expected to happen: add gcp kubeconfig then add gcp cluster

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• OS (e.g: Macos 10.15.5 (19F96) or Windows 10):
• nhctl version (use nchtl version command):
• helm version (use helm version command):
• kubectl version (use kubectl version command):
• Others:

What happened:

I am using nocalhost to debug kube-proxy.

I used the Edit Manifest to look at the yaml of kube-proxy, and there are privileges:

......
            containers:
                - command:
                    - /usr/local/bin/kube-proxy
                    - --config=/var/lib/kube-proxy/config.conf
                    - --hostname-override=$(NODE_NAME)
                    - --feature-gates=TopologyAwareHints=true
                  env:
                    - name: NODE_NAME
                      valueFrom:
                        fieldRef:
                            apiVersion: v1
                            fieldPath: spec.nodeName
                  image: k8s.gcr.io/kube-proxy:v1.21.8
                  imagePullPolicy: IfNotPresent
                  name: kube-proxy
                  resources: {}
                  securityContext:
                    privileged: true        <--------------------------------- here!!!
......

However, the generated dev deployment, without privileged. I use the command kubectl -n kube-system get deployment.apps/daemon-set-generated-deploy-kube-proxy -oyaml to get dev deployment yaml:

(You cannot find privileged here)

apiVersion: apps/v1
kind: Deployment
metadata:
  annotations:
    deployment.kubernetes.io/revision: "1"
  creationTimestamp: "2022-01-11T12:07:06Z"
  generation: 1
  labels:
    nocalhost.dev.workload.ignored: "true"
  name: daemon-set-generated-deploy-kube-proxy
  namespace: kube-system
  resourceVersion: "28962130"
  selfLink: /apis/apps/v1/namespaces/kube-system/deployments/daemon-set-generated-deploy-kube-proxy
  uid: f61d9b0a-1e6a-4d7e-a885-186617a1d452
spec:
  progressDeadlineSeconds: 600
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      k8s-app: kube-proxy
  strategy:
    rollingUpdate:
      maxSurge: 25%
      maxUnavailable: 25%
    type: RollingUpdate
  template:
    metadata:
      creationTimestamp: null
      labels:
        k8s-app: kube-proxy
    spec:
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
            - matchExpressions:
              - key: node-role.kubernetes.io/edge
                operator: DoesNotExist
              - key: node-role.kubernetes.io/agent
                operator: DoesNotExist
      containers:
      - command:
        - /bin/sh
        - -c
        - tail -f /dev/null
        env:
        - name: NODE_NAME
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: spec.nodeName
        image: nocalhost-docker.pkg.coding.net/nocalhost/dev-images/golang:zsh
        imagePullPolicy: Always
        name: nocalhost-dev
        resources:
          limits:
            cpu: "2"
            memory: 4Gi
          requests:
            cpu: "1"
            memory: 2Gi
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /var/lib/kube-proxy
          name: kube-proxy
        - mountPath: /run/xtables.lock
          name: xtables-lock
        - mountPath: /lib/modules
          name: lib-modules
          readOnly: true
        - mountPath: /var/syncthing
          name: nocalhost-syncthing
          subPath: syncthing
        - mountPath: /var/syncthing/secret
          name: nocalhost-syncthing-secret
        - mountPath: /home/nocalhost-dev
          name: nocalhost-shared-volume
        workingDir: /home/nocalhost-dev
      - args:
        - rc-service sshd restart && unset STGUIADDRESS && cp /var/syncthing/secret/*
          /var/syncthing/ && /bin/entrypoint.sh && /bin/syncthing -home /var/syncthing
        command:
        - /bin/sh
        - -c
        image: nocalhost-docker.pkg.coding.net/nocalhost/public/nocalhost-sidecar:sshversion
        imagePullPolicy: Always
        name: nocalhost-sidecar
        resources:
          limits:
            cpu: "1"
            memory: 1Gi
          requests:
            cpu: 100m
            memory: 50Mi
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /var/syncthing
          name: nocalhost-syncthing
          subPath: syncthing
        - mountPath: /var/syncthing/secret
          name: nocalhost-syncthing-secret
        - mountPath: /home/nocalhost-dev
          name: nocalhost-shared-volume
        workingDir: /home/nocalhost-dev
      dnsPolicy: ClusterFirst
      hostNetwork: true
      nodeSelector:
        kubernetes.io/os: linux
      priorityClassName: system-node-critical
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext: {}
      serviceAccount: kube-proxy
      serviceAccountName: kube-proxy
      terminationGracePeriodSeconds: 30
      tolerations:
      - key: CriticalAddonsOnly
        operator: Exists
      - operator: Exists
      volumes:
      - configMap:
          defaultMode: 420
          name: kube-proxy
        name: kube-proxy
      - hostPath:
          path: /run/xtables.lock
          type: FileOrCreate
        name: xtables-lock
      - hostPath:
          path: /lib/modules
          type: ""
        name: lib-modules
      - emptyDir: {}
        name: nocalhost-syncthing
      - name: nocalhost-syncthing-secret
        secret:
          defaultMode: 448
          items:
          - key: config.xml
            mode: 448
            path: config.xml
          - key: cert.pem
            mode: 448
            path: cert.pem
          - key: key.pem
            mode: 448
            path: key.pem
          secretName: kube-proxy-daemonset-nocalhost-syncthing-secret
      - name: nocalhost-shared-volume
        persistentVolumeClaim:
          claimName: default.application-1641888119229698000
status:
  availableReplicas: 1
  conditions:
  - lastTransitionTime: "2022-01-11T12:07:10Z"
    lastUpdateTime: "2022-01-11T12:07:10Z"
    message: Deployment has minimum availability.
    reason: MinimumReplicasAvailable
    status: "True"
    type: Available
  - lastTransitionTime: "2022-01-11T12:07:06Z"
    lastUpdateTime: "2022-01-11T12:07:10Z"
    message: ReplicaSet "daemon-set-generated-deploy-kube-proxy-c5fb794bf" has successfully
      progressed.
    reason: NewReplicaSetAvailable
    status: "True"
    type: Progressing
  observedGeneration: 1
  readyReplicas: 1
  replicas: 1
  updatedReplicas: 1

This will make my dev container unprivileged and will not be able to create iptables rules!!!

By the way, I manually adding privileges to dev deployment will solve this problem.

What happened: See the picture:

Whether the windows defender let it go or not, it would always keep alerts.

Environment:

• OS (e.g: Macos 10.15.5 (19F96) or Windows 10): Windows 10
• nhctl version (use nchtl version command): maybe install by vscode?
• helm version (use helm version command): not yet
• kubectl version (use kubectl version command): cannot connect it.
• Others:

What happened: I use a k3s cluster and want to install nocalhost. It doesn't work with nocalhost-api CrashLoopBackOff.

The output of kubectl get pod -nnocalhost -owide:

NAME                             READY   STATUS             RESTARTS   AGE   IP           NODE              NOMINATED NODE   READINESS GATES
svclb-nocalhost-web-7nkvh        1/1     Running            0          73s   10.42.1.9    node-ccf0ed90     <none>           <none>
svclb-nocalhost-web-fqms9        1/1     Running            0          73s   10.42.0.16   master-d39b1dd5   <none>           <none>
svclb-nocalhost-web-77849        1/1     Running            0          73s   10.42.2.7    node-2ffe5da9     <none>           <none>
nocalhost-web-6f8f65d48f-xvzwt   1/1     Running            0          73s   10.42.2.8    node-2ffe5da9     <none>           <none>
nocalhost-api-7bdd895d99-tbthc   0/1     CrashLoopBackOff   3          73s   10.42.1.8    node-ccf0ed90     <none>           <none>

The log of nocalhost-api pod:

# kubectl logs -f -nnocalhost nocalhost-api-7bdd895d99-tbthc
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0xb7d260]

goroutine 1 [running]:
nocalhost/pkg/nocalhost-api/pkg/log.Errorf(...)
        /opt/src/pkg/nocalhost-api/pkg/log/logger.go:121
nocalhost/internal/nocalhost-api/model.openDB(0xc000594118, 0x4, 0xc000594130, 0x4, 0xc000476460, 0x16, 0xc0005940f0, 0x9, 0xc00034fd80)
        /opt/src/internal/nocalhost-api/model/init.go:53 +0x4c0
nocalhost/internal/nocalhost-api/model.Init(0x1959b60)
        /opt/src/internal/nocalhost-api/model/init.go:34 +0x14d
nocalhost/pkg/nocalhost-api/napp.New(0xc0003cc340, 0x17)
        /opt/src/pkg/nocalhost-api/napp/app.go:62 +0x4e
main.main()
        /opt/src/cmd/nocalhost-api/nocalhost-api.go:74 +0x319

What you expected to happen: nocalhost install successfully.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?: My k3s cluster is using containerd instand of docker.

Environment:

• OS (e.g: Macos 10.15.5 (19F96) or Windows 10): ubuntu 18.04.5 LTS
• nhctl version (use nchtl version command): v0.2.1 (defe9f2f33fda0bed2eb9791450eaa2f7badc7ed)
• helm version (use helm version command):

version.BuildInfo{Version:"v3.1.2", GitCommit:"d878d4d45863e42fd5cff6743294a11d28a9abce", GitTreeState:"clean", GoVersion:"go1.13.8"}

• kubectl version (use kubectl version command):

Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.1", GitCommit:"c4d752765b3bbac2237bf87cf0b1c2e307844666", GitTreeState:"clean", BuildDate:"2020-12-23T02:22:53Z", GoVersion:"go1.15.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.3-k3s.2", GitCommit:"e7e6a3c4e9a7d80b87793612730d10a863a25980", GitTreeState:"clean", BuildDate:"2019-11-18T18:31:23Z", GoVersion:"go1.13.4", Compiler:"gc", Platform:"linux/amd64"}

• Others:

# kubectl get node
NAME              STATUS   ROLES    AGE   VERSION
node-2ffe5da9     Ready    <none>   29h   v1.16.3-k3s.2
node-ccf0ed90     Ready    <none>   29h   v1.16.3-k3s.2
master-d39b1dd5   Ready    master   29h   v1.16.3-k3s.2

What this PR does / why we need it:

Special notes for your reviewer:

If applicable:

• [ ] this PR contains documentation
• [ ] this PR contains unit tests
• [ ] this PR has been tested for backwards compatibility

What would you like to be added: when i start dev mode，error happens：

[cmd] /Users/owen/.nh/bin/nhctl dev associate default.application --local-sync /Users/owen/woqu/qfushion/dock-template --controller-type Deployment --deployment dock --container dock --kubeconfig /Users/owen/.nh/intellij-plugin/kubeConfigs/ed9a7ff5-b0de-4357-8a4a-a90d1e4659fd_config --namespace qfusion [name: dock serviceType: deployment] Load nocalhost svc config from local fail, err: [Local config loaded, but no valid config found] [cmd] /Users/owen/.nh/bin/nhctl dev containers default.application --controller-type Deployment --kubeconfig /Users/owen/.nh/intellij-plugin/kubeConfigs/ed9a7ff5-b0de-4357-8a4a-a90d1e4659fd_config --namespace qfusion --deployment dock ["dock"] [cmd] /Users/owen/.nh/bin/nhctl dev associate default.application --local-sync /Users/owen/woqu/qfushion/dock-template --controller-type Deployment --deployment dock --container dock --kubeconfig /Users/owen/.nh/intellij-plugin/kubeConfigs/ed9a7ff5-b0de-4357-8a4a-a90d1e4659fd_config --namespace qfusion [name: dock serviceType: deployment] Load nocalhost svc config from local fail, err: [Local config loaded, but no valid config found] [cmd] /Users/owen/.nh/bin/nhctl dev containers default.application --controller-type Deployment --kubeconfig /Users/owen/.nh/intellij-plugin/kubeConfigs/ed9a7ff5-b0de-4357-8a4a-a90d1e4659fd_config --namespace qfusion --deployment dock ["dock"] [cmd] /Users/owen/.nh/bin/nhctl dev associate default.application --local-sync /Users/owen/woqu/qfushion/dock-template --controller-type Deployment --deployment dock --container dock --kubeconfig /Users/owen/.nh/intellij-plugin/kubeConfigs/ed9a7ff5-b0de-4357-8a4a-a90d1e4659fd_config --namespace qfusion [name: dock serviceType: deployment] Load nocalhost svc config from local fail, err: [Local config loaded, but no valid config found]

so，could we add more useful information for invalid config yaml file?

Why is this needed: i do not know what errors i writen in the config yaml file,

steps to reproduce: helm repo add nocalhost "https://nocalhost-helm.pkg.coding.net/nocalhost/nocalhost" helm repo update helm install nocalhost nocalhost/nocalhost -n nocalhost --create-namespace

What happened: Windows 11 上的 vscode, 安装插件nocalhost 插件， 已经开启了科学上网， 可以正常下载 nhctl. nhctl 启动失败， 可见在执行以下命令 execute command fail:C:\Users\Gabriel Wu\.nh\bin\nhctl.exe kubeconfig check -i -c k3d-k3d-cluster --kubeconfig -

我在正常终端中执行以上命令。 结果正常。 VSCode 中不正常， 无法加载kubeconfig 。难道因为我的路径中包含空格 ？ kubeconfig 后面一段C:\Users\"Gabriel Wu"\.kube\config哪去了 ？ PS C:\Users\Gabriel Wu\.nh\bin> .\nhctl.exe kubeconfig check -i -c k3d-k3d-cluster --kubeconfig C:\Users\"Gabriel Wu"\.kube\config [{"status":"SUCCESS","tips":"Current context can list with cluster-scope resources"}]

手动在 vscode 的kubeconfig 里编辑， 加上“” 号。 依然报错。

What you expected to happen: 正常加载 kubeconfig 配置

How to reproduce it (as minimally and precisely as possible): windows 11 上 vscode 安装 nocalhost v0.6.19 路径中包含空格 vscode 版本 1.74.0

Anything else we need to know?:

Environment:

• OS (e.g: Macos 10.15.5 (19F96) or Windows 10):
  Windows 11
• nhctl version (use nchtl version command): nocalhost v0.6.19

nhctl: Nocalhost CLI
    Version: v0.6.19
    Branch: HEAD
    Git commit: 6b60504abd065f45d0ffd941a5a30ceed8187e7e
    Built time: Fri Nov 25 15:05:59 2022
    Built OS/Arch: windows/amd64
    Built Go version: go1.16.7

• helm version (use helm version command):

PS D:\GitSpace\infra-code> helm version
version.BuildInfo{Version:"v3.9.4", GitCommit:"dbc6d8e20fe1d58d50e6ed30f09a04a77e4c68db", GitTreeState:"clean", GoVersion:"go1.17.13"}

• kubectl version (use kubectl version command):

PS D:\GitSpace\infra-code> kubectl version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.16", GitCommit:"b28e1f370a4a4c428ddbeababcaf0198f048fcac", GitTreeState:"clean", BuildDate:"2022-11-09T13:37:37Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.16+k3s1", GitCommit:"d04e48d63b28eba2ec83d579d09f6a313e1c187b", GitTreeState:"clean", BuildDate:"2022-11-18T17:51:22Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/amd64"}

• Others:

Bumps github.com/containerd/containerd from 1.5.10 to 1.5.16.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.