You need to implement a network ingress for a new game that meets the defined business and technical requirements. Mountkirk Games wants each regional game instance to be located in multiple Google Cloud regions. What should you do?
You need to implement a network ingress for a new game that meets the defined business and technical requirements. Mountkirk Games wants each regional game instance to be located in multiple Google Cloud regions. What should you do?
To meet the requirement of having regional game instances located in multiple Google Cloud regions, the best option is to configure Ingress for Anthos with a global load balancer and Google Kubernetes Engine. Ingress for Anthos is designed to manage multi-cluster configurations and supports multi-regional use cases with features such as health checking and traffic failover, ensuring that the used solution can handle traffic routing for a globally distributed architecture.
IMHO d) is the correct answer, not a) The game fulfills the business requirements as well as the technical requirements - so it is build upon an architecture that is multi regional. https://cloud.google.com/kubernetes-engine/docs/concepts/multi-cluster-ingress
I think anthos would work but i don’t think it is needed. Deploying anthos means they will maintain an on prem environment along with gcp. Anthos will give them the ability to manage both environments from a single pane of glass. I think b is correc. Kubemci provides global lb for multi gke clusters https://cloud.google.com/blog/products/gcp/how-to-deploy-geographically-distributed-services-on-kubernetes-engine-with-kubemci
From what i understand kubemci is now deprecated (although i have not found an official doc stating this). If this is the case then D is correct
Official doc saying kubemci deprecated in here: https://github.com/GoogleCloudPlatform/k8s-multicluster-ingress “This has now been deprecated in favor of Ingress for Anthos. Ingress for Anthos is the recommended way to deploy multi-cluster ingress.”
Interesting how they already, within this short period of time renamed 'Ingress for Anthos' to 'Multi Cluster Ingress'..
https://github.com/GoogleCloudPlatform/k8s-multicluster-ingress
Why is anthos needed. In the link shared above , a multi cluster ingress ( HTTPS LB ) is sufficient. We should go with C.
Anthos is overkill! - As per the case study, there is no mention of hybrid requirement.
Eventual migration. :-)
D for me. since it's a multiple regions game.Need multi-GKE or multi-MIG. To configure the ingress between multi-GKE. kubemci or Ahthos kubemci has now been deprecated in favor of Ingress for Anthos. Ingress for Anthos is the recommended way to deploy multi-cluster ingress. https://github.com/GoogleCloudPlatform/k8s-multicluster-ingress So. D
I had a test today. kubemci and Ingress for Anthos were deprecated . Ingress for Anthos was replaced with "Multi Cluster Ingress" in the actual test.
A is good to go. Anthos is an overkill here
Needs ingress over multiple clusters which requires Multi Cluster Ingress or Antos for Ingress as it was previously known.
For me is C. There is no necessity of Anthos or hybrid connectivity cluster. GKE and Global LB is enought
Well, here B is the deprecated right answer, but nowadays D is the current right answer.
why not the other options? A. Managed Instance Group with Compute Engine: While this can achieve regional deployments, it wouldn't offer containerization benefits like GKE. GKE provides features like autoscaling and health checks, which are well-suited for managing game workloads. B. Kubemci with Global Load Balancer: Kubemci is a tool for managing on-premise Kubernetes clusters, not directly applicable to Google Cloud's GKE. D. Ingress for Anthos: Anthos is a suite of tools for managing hybrid and multi-cloud deployments. While it can integrate with GKE and global load balancers, it's a more complex solution compared to simply using a global load balancer with GKE for this specific scenario.
C is sufficient.
Anthos enables migration of legacy games [last business/tech requirement]. Since the question requires consideration of these requirements, this is the difference maker for option D.
It is D. According to https://cloud.google.com/kubernetes-engine/docs/concepts/multi-cluster-ingress ... Multi Cluster Ingress's multi-cluster support satisfies many use cases including: Multi-regional, multi-cluster availability through health checking and traffic failover.
Adding an article explaining why D could be the solution https://itnext.io/ingress-for-anthos-multi-cluster-ingress-and-global-service-load-balancing-c56c57b97e82
B is the answer: B. Configure kubemci with a global load balancer and Google Kubernetes Engine (GKE). This approach provides a scalable, highly available, and manageable solution for routing traffic to regional game instances deployed across multiple Google Cloud regions. Kubemci is a multi-cluster Ingress controller that enables managing Ingress resources across multiple GKE clusters, making it ideal for handling regional game instances. A global load balancer distributes incoming traffic across multiple regions, ensuring that users are directed to the nearest and most responsive game instance.
it used to be the right answer, now the right answer should be D https://github.com/GoogleCloudPlatform/k8s-multicluster-ingress
D As per the below documentation, the best option found is D: https://cloud.google.com/kubernetes-engine/docs/concepts/multi-cluster-ingress
Anthos is required to fulfill the requirement of "Mountkirk Games wants each regional game instance to be located in multiple Google Cloud regions".
GKE + global rb = Ingless for Anthos.
There is no need for Anthos as Mountkrik has migrated all of its games to Google Cloud. Anthos should be used in a hybrid environment scenario.
Isn't kubemci the equivalent of a multi-cluster ingress?? What's the difference here between D and B?