dxvk-native VS istio

DXVK 2.0 has upstreamed the dxvk-native code, meaning the game runs using native Linux libraries but uses DX11 with DXVK. This is mostly done because the ancient OpenGL linux-native renderer was rather bad.

what works best is games supporting dxvk-native: https://github.com/Joshua-Ashton/dxvk-native

There is DXVK native which doesn't require wine.

https://github.com/Joshua-Ashton/dxvk-native

There are also Dxvk native for porting game to Linux. Which is used by valve to port it's game to Linux.(replacing togl)

I disagree, but I get the frustration. It's just that I've been playing CS:GO for almost a decade, and while I think the game is neglected by Valve in general, it's way a worse scenario on Linux. For instance, Vulkan support (via dxvk-native) was added back in December last year, and it's not been updated ever since, so you get way worse stuttering when compared to OpenGL (which is actually a DirectX 9 to OpenGL translation layer, called toGL, which has its own set of bugs and issues); Plus, you can't change screen resolution when using Vulkan. I get some occasional little stutters on Windows as well, but the whole CS:GO experience is honestly just way worse on Linux, unfortunately.

DXVK-Native and the game Perimeter. Perimeter is the one game I know of that's opensource and that uses DXVK-Native. I got it to run, but there was no support for any audio, making this pretty unexciting. This is still being worked on upstream, so maybe a DXVK-native port later and a port of perimeter will happen then...

You never mentioned that requirement, but here you go: https://github.com/Joshua-Ashton/dxvk-native

DirectX isn't an option on linux/mac anyway, it's just launch or safe mode. (Note to any SCS developers if they're lurking around here... please implement the DX pipeline into the linux build so we can use DXVK-Native, it's much faster than OGL!)

AWS EKS provides a managed Kubernetes service, simplifying cluster management and deployment. Istio, an open-source service mesh, enables traffic management, security, and observability across microservices.

Istio is a popular open-source service mesh framework that provides a comprehensive solution for managing, securing, and observing microservices-based applications running on Kubernetes.

Leverage a service mesh like Istio or Linkerd to manage communication between microservices within the Kubernetes cluster. These service meshes can be configured to intercept JMX traffic and enforce access control policies. Benefits:

Open Source and Cloud Computing: A Match Made in Heaven The cloud is accelerating OSS adoption. Cloud-native technologies like Kubernetes [https://kubernetes.io/] and Istio [https://istio.io/], both open-source projects, are revolutionizing how applications are built and deployed across cloud platforms.

Consider the case of Bookinfo, a sample application provided by Istio, rewritten using CloudWeGo's Kitex for superior performance and extensibility.

It is a dedicated infrastructure layer that manages service-to-service communication, providing features like load balancing, encryption, authentication, and monitoring. Istio deploys sidecar proxies alongside each microservice instance. These proxies handle communication, providing features like load balancing, service discovery, encryption, monitoring and authentication.

5Y old post that sounds like they've done similar here: Caddy Issue Istio Issue but doesn't cover much of the implementation

In a production environment there will be a load balancer setup with an Ingress Controller, Service Mesh or some type of Custom Router. This allows all traffic to be sent to the single load balancer IP address and then route the traffic to a service based on the Domain name or subpath. We are using a NGINX ingress controller but service meshes like Istio have been becoming the most popular solution to use as they offer more segmentation, security and granular control.

Flagger is a progressive delivery tool that enables a Kubernetes operator to automate the promotion or rollback of deployments based on metrics analysis. It supports a variety of metrics including Prometheus, Datadog, and New Relic to name a few. It also works well with Istio service mesh, and can implement progressive traffic splitting between primary and canary releases.