<p>I am new to Kubernetes. I am planning to build/deploy an application to EKS. This will likely be deployed on azure and gcp as well.</p>
<p>I want to separate data plane and control plane in my application deployed in EKS.</p>
<p>Is there anyway EKS/kubernetes allows to accomplish this?</p>
<p>Or should we go for two EKS with one for data plane and another for control plane?</p>
<p>Here is the problem(copied from the answer below)</p>
<blockquote>
<p>I have an application, built using the microservice architecture
(meaning you will have it split into components that will communicate
with eachother).</p>
<p>I want to deploy this application on a public cloud (EKS, GCP, AWS).</p>
<p>I want a separation of the APPLICATION control plane (decision making
components like authentication APIs, internal service routing) from
the APPLICATION data plane (the serving of your application data to
the clients through the egress).</p>
</blockquote>

infinite_loop
<p>I great open-source observability control plane for you apps is Odigos.  The installation is super easy and within a few minutes you can get traces, metrics and logs.  You get auto-instrumentation for all languages (including GO) as well as a manager of your opentelemetry collectors.
Check it out: <a href="https://github.com/keyval-dev/odigos" rel="nofollow noreferrer">https://github.com/keyval-dev/odigos</a></p>
