Le produit décrit dans cette documentation, Anthos Clusters on AWS (génération précédente), est désormais en mode de maintenance. Toutes les nouvelles installations doivent utiliser le produit de génération actuelle, Anthos Clusters on AWS.
Restez organisé à l'aide des collections
Enregistrez et classez les contenus selon vos préférences.
Cet article explique comment installer Cloud Service Mesh, qui est préinstallé avec une passerelle d'entrée.
Avec Cloud Service Mesh, vous pouvez configurer une ressource d'entrée Kubernetes pour vos déploiements si vous avez besoin d'un contrôleur d'entrée.
Cet article fournit un exemple qui vous montre comment configurer un exemple de déploiement et une ressource d'entrée.
L'installation de Cloud Service Mesh se compose de deux parties principales:
Si vous avez uniquement besoin d'utiliser un objet Ingress à l'aide d'un contrôleur Ingress, vous n'avez pas besoin d'injecter un proxy side-car dans vos pods de charge de travail. En revanche, si vous souhaitez bénéficier des avantages en matière de sécurité offerts par Cloud Service Mesh et utiliser les fonctionnalités de routage du trafic, vous devez injecter les proxys side-car.
Avant de commencer
Avant de commencer à utiliser GKE sur AWS, veillez à effectuer les tâches suivantes :
Le champ ADDRESS doit comporter un nom de domaine ELB. Si le champ ADDRESS reste en attente (pending), confirmez les libellés de VPC et de sous-réseau.
Vous pouvez vérifier l'URL de la passerelle d'entrée en composant l'hôte et le port.
Pour obtenir l'URL de votre passerelle, exécutez les commandes suivantes :
exportINGRESS_URL=$(envHTTPS_PROXY=http://localhost:8118\
kubectlgetingresshello-app-ojsonpath='{.status.loadBalancer.ingress[0].hostname}')echo"Your hello-app Ingress URL is: http://"$INGRESS_URL
La dernière commande imprime le point de terminaison de votre entrée.
Si vous avez créé une entrée publique, vous pouvez afficher la page Web par défaut hello-app dans curl en accédant à http://$INGRESS_URL/.
curl$INGRESS_URL/
Nettoyer
Vous supprimez les composants hello-app avec la commande kubectl delete.
Sauf indication contraire, le contenu de cette page est régi par une licence Creative Commons Attribution 4.0, et les échantillons de code sont régis par une licence Apache 2.0. Pour en savoir plus, consultez les Règles du site Google Developers. Java est une marque déposée d'Oracle et/ou de ses sociétés affiliées.
Dernière mise à jour le 2025/09/04 (UTC).
[[["Facile à comprendre","easyToUnderstand","thumb-up"],["J'ai pu résoudre mon problème","solvedMyProblem","thumb-up"],["Autre","otherUp","thumb-up"]],[["Difficile à comprendre","hardToUnderstand","thumb-down"],["Informations ou exemple de code incorrects","incorrectInformationOrSampleCode","thumb-down"],["Il n'y a pas l'information/les exemples dont j'ai besoin","missingTheInformationSamplesINeed","thumb-down"],["Problème de traduction","translationIssue","thumb-down"],["Autre","otherDown","thumb-down"]],["Dernière mise à jour le 2025/09/04 (UTC)."],[],[],null,["This topic shows you how to install Cloud Service Mesh, which comes preinstalled\nwith an [Ingress Gateway](https://istio.io/latest/docs/tasks/traffic-management/ingress/ingress-control/).\nWith Cloud Service Mesh, you can configure a\n[Kubernetes Ingress resource](https://kubernetes.io/docs/concepts/services-networking/ingress/)\nfor your Deployments if you need an\n[Ingress controller](https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/).\nThis topic provides an example that shows you how to configure a sample\nDeployment and Ingress resource.\n\nThe installation of Cloud Service Mesh consists of two main parts:\n\n1. Installing a specific version of the Cloud Service Mesh [customer-managed control plane](/service-mesh/docs/glossary#control_plane) and Ingress Gateway.\n2. Labeling your namespaces with a [revision label](/service-mesh/docs/revisions-overview) and redeploying your workloads to inject a [sidecar proxy](/service-mesh/docs/proxy-injection).\n\nIf you only need to use an Ingress object using an Ingress controller, you don't\nhave to inject a sidecar proxy into your workload Pods. But if you want the\n[security benefits](/service-mesh/docs/overview#security_benefits) that\nCloud Service Mesh provides, and if you want to make use of the\n[traffic routing](/service-mesh/docs/overview#traffic_management) capabilities,\nyou need to inject the sidecar proxies.\n\nBefore you begin\n\n\nBefore you start using GKE on AWS, make sure you have performed the following tasks:\n\n- Complete the [Prerequisites](/kubernetes-engine/multi-cloud/docs/aws/previous-generation/how-to/prerequisites).\n\n\u003c!-- --\u003e\n\n- Install a [management service](/kubernetes-engine/multi-cloud/docs/aws/previous-generation/how-to/installing-management).\n- Create a [user cluster](/kubernetes-engine/multi-cloud/docs/aws/previous-generation/how-to/creating-user-cluster).\n- Register your cluster with Connect by following the steps in [Connecting to your cluster with Cloud console](/kubernetes-engine/multi-cloud/docs/aws/previous-generation/how-to/connecting-to-a-cluster).\n- Configure your cluster to [Use workload identity with Google Cloud](/kubernetes-engine/multi-cloud/docs/aws/previous-generation/how-to/workload-identity-gcp).\n- If your user clusters have restricted outbound access to the internet,\n allow access to the following container repository domains:\n\n - `docker.io`\n - `quay.io`\n- From your `anthos-aws` directory, use\n `anthos-gke` to switch context to your user cluster.\n\n ```sh\n cd anthos-aws\n env HTTPS_PROXY=http://localhost:8118 \\\n anthos-gke aws clusters get-credentials CLUSTER_NAME\n ```\n Replace \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e with your user cluster name.\n\n \u003cbr /\u003e\n\nInstalling Anthos Service Mesh\n\nFollow the steps in\n[Install Cloud Service Mesh](/service-mesh/docs/unified-install/install).\n\nCreating an example Deployment\n\nIn this section, you install a sample application and create an Ingress endpoint\nfor it.\n\n1. Create a Deployment of `hello-app` and a ClusterIP for the deployment.\n Copy the following YAML into a file named `hello-app.yaml`.\n\n apiVersion: apps/v1\n kind: Deployment\n metadata:\n labels:\n app: hello-app\n name: hello-app\n spec:\n selector:\n matchLabels:\n app: hello-app\n replicas: 3\n template:\n metadata:\n labels:\n app: hello-app\n spec:\n containers:\n - name: hello\n image: \"gcr.io/google-samples/hello-app:2.0\"\n ---\n apiVersion: v1\n kind: Service\n metadata:\n labels:\n app: hello-app\n name: hello-app\n spec:\n type: ClusterIP\n selector:\n app: hello-app\n ports:\n - protocol: TCP\n port: 8080\n targetPort: 8080\n\n2. Apply the YAML to your cluster with `kubectl apply`.\n\n env HTTPS_PROXY=http://localhost:8118 \\\n kubectl apply -f hello-app.yaml\n\n3. Create a Kubernetes Ingress for the sample application. Copy the following\n YAML into a file named `hello-app-ingress.yaml`\n\n apiVersion: networking.k8s.io/v1beta1\n kind: Ingress\n metadata:\n annotations:\n kubernetes.io/ingress.class: istio\n labels:\n app: hello-app\n name: hello-app\n spec:\n rules:\n - host:\n http:\n paths:\n - backend:\n serviceName: hello-app\n servicePort: 8080\n\n4. Create the Ingress by applying the configuration with `kubectl apply`.\n\n env HTTPS_PROXY=http://localhost:8118 \\\n kubectl apply -f hello-app-ingress.yaml\n\n5. Check the status of your gateway with `kubectl get svc`.\n\n env HTTPS_PROXY=http://localhost:8118 \\\n kubectl get ingress hello-app\n\n The `ADDRESS` field should have an ELB domain name. If the `ADDRESS`\n remains `pending`, confirm your VPC and Subnet labeling.\n6. You can check the Ingress gateway URL by composing the host and port.\n To get your gateway URL, perform the following commands:\n\n export INGRESS_URL=$(env HTTPS_PROXY=http://localhost:8118 \\\n kubectl get ingress hello-app -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')\n echo \"Your hello-app Ingress URL is: http://\"$INGRESS_URL\n\n The last command prints the endpoint of your Ingress.\n7. If you created a public Ingress, you can view the `hello-app` default web page\n in `curl` by visiting `http://$INGRESS_URL/`.\n\n curl $INGRESS_URL/\n\nCleaning up\n\nYou remove the `hello-app` components with `kubectl delete`. \n\n env HTTPS_PROXY=http://localhost:8118 \\\n kubectl delete -f hello-app.yaml &&\\\n kubectl delete -f hello-app-ingress.yaml\n\nIf you would like to remove Cloud Service Mesh, see\n[Uninstalling Cloud Service Mesh](/service-mesh/docs/uninstall#uninstalling).\n\nWhat's next\n\nLearn more about:\n\n- [Injecting sidecar proxies](/service-mesh/docs/proxy-injection)\n\n- [Naming service ports](/service-mesh/docs/naming-service-ports)\n\n- [Enabling Cloud Service Mesh optional features](/service-mesh/docs/enable-optional-features)\n\n- [Integrating with third-party add-ons](/service-mesh/docs/third-party-integrations)\n\n- [Configuring the Ingress Gateway](https://istio.io/latest/docs/tasks/traffic-management/ingress/ingress-control/)\n\n- [Routing traffic](https://istio.io/docs/tasks/traffic-management/ingress/)"]]