Proposal : Docker Extension to solve Kubernetes Distribution differences

[anshrma]

Problem Statement : As a builder, developing against Kubernetes APIs (either K8s manifest or SDKs or CLIs) , differences between my local Kubernetes distribution (including K8s control plane and its dependencies) that is shipped with Docker Desktop Vs my production environment running on a managed kubernetes container service , like Amazon Elastic Kubernetes Service (EKS) or Amazon EKS Anywhere , creates friction in the development experience overall elevating my development timelines due to unproductive time lost to troubleshoot inconsistencies between the two environments.

Proposal : As a builder, developing against Kubernetes APIs (either K8s manifest or SDKs or CLIs), I enable Docker extension which gives me the same version of Kubernetes and its dependencies as deployed in managed kubernetes container service. When this extension is enabled, it should swap out Docker Desktop’s default upstream Kubernetes distribution with the one as used by a managed kubernetes container service , EKS or EKS-Anywhere.

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment