Windows 10: Windows idle process has kubernetes.docker.internal

I recently found there is a bunch of kubernetes.docker.internal in the system idle process. I don't use docker or kubernetes, does windows use it internally? Is there a way to remove it? I checked control panel and couldn't find either docker or kubernetes

:)

 

Using WSL2 with Docker Desktop to run a Kubernetes cluster

Up until a couple months ago I was able to use Docker Desktop and WSL2 to run Kubernetes WITHOUT having a Linux distro on my dev system. During the last 2 month period of time I did not do any development of services in K8s and did not even start Docker Desktop.

Now I am ready to start developing services that run in K8s which is hosted on Docker Desktop, with no Linux distro just as I did previously. But K8s does not start. No matter what kinds of remedies I try, K8s will not start.

I am wondering if something changed and now I need to use a Linux distro? Is this question within the scope of this forum?

Thanks.

 

System idle process spike

Although you may have a problem that is causing fps drops, "System Idle Process" isn't what's causing it.

When "CPU usage" for System Idle Process is high, that means that your CPU is not doing much useful work.

Idle, noun:

• not working or active; unemployed; doing nothing: idle workers.
  
• not spent or filled with activity: idle hours.
  

When System Idle Process shows as 30%, what's taking up the majority of the rest of the CPU cycles? That's probably the source of the problem.

 

Kubernetes - any way of making it work on Windows

Yes, we are moving towards Kubernetes at our office. We had moved to an on-prem hybrid Docker EE implementation, then we moved over to using AWS ECS......but shortly thereafter we decided that AWS EKS is really where we want to be.

Our plan is not to run Windows in our EKS clusters. We are converting the .net apps to .net core to run them on Linux and then run them on Kubernetes.

Kubernetes is a huge monster, as z3r010 noted. We use a bunch of bolt on tools too, like Istio, Rancher, and Helm to deploy the pods. We have written custom connectors and just about have our multicloud fully functional. OnPrem Kuberentes, AWS EKS and Azure Kubernetes.

I'll be working on hundreds of Kubernetes deployments in the next 6-12 months.


Today, you can enable it pretty easily in Docker Desktop to get used to it. You can also deploy a tool called minikube for playing with Kubernetes.