Ken Rider

It worked the first time then sometime later in a separate start of the kubeman executable it didn’t. It’s done that several times. Every time it didn’t work in kubeman,...

I've since gotten the same message from other recipes with the same message in the debug console.

It's still broken and it looks like I have the newest versions of VS Code and the extension installed. A `kubectl config get-contexts` shows 5 contexts. However, 2 of the...

I deleted the 2 contexts that didn't work but still get the same error.

There is an additional error message now. (See below.) I'm not sure why it would be trying to connect to localhost:8080 as it's not referenced anywhere in ~/.kube/config. "Failed to...

First, it’s not just a WSL problem. If I open VS Code from PowerShell and the Windows desktop, I get the same behavior. I made a short video of starting...

That worked. My settings.json now has the vs-kubernetes.kubeconfig and vs-kubernetes.knownKubeconfigs. I had to add both the WSL and the Windows default kubeconfig. However, I do get the same error message...

My (related) settings are the same as I left them back in November. ```json "vs-kubernetes": { "vs-kubernetes.kubeconfig": "/home/ken/.kube/config", "vs-kubernetes.knownKubeconfigs": [ "/home/ken/.kube/config", "c:\\Users\\KenRider\\.kube\\config" ], ``` When I open VS Code in...

I was hoping to do this without introducing another tool, but I'll look at Robusta this weekend.

Found this [ServiceMonitor not found in monitoring.coreos.com/v1](https://stackoverflow.com/questions/51095556/servicemonitor-not-found-in-monitoring-coreos-com-v1). After applying the referenced manifest and ignoring the errors, the OpenCost install worked. ```bash ❯ kubectl apply -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/main/bundle.yaml customresourcedefinition.apiextensions.k8s.io/podmonitors.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/probes.monitoring.coreos.com created...