Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
Implementa objetos Service
Implementar objetos Service en clústeres con Cloud Service Mesh es casi la misma que la implementación de objetos Service en clústeres sin Cloud Service Mesh. Necesitas realizar algunos cambios en tus manifiestos de Kubernetes:
Asigna un nombre a los puertos de los objetos Service. Aunque GKE te permite definir puertos de Service sin nombre, Cloud Service Mesh requiere que proporciones un nombre para un puerto que coincida con el protocolo del puerto.
Etiqueta tus objetos Deployment. Esto te permite usar las funciones de administración de tráfico de Cloud Service Mesh, como la división del tráfico entre versiones del mismo servicio.
En el siguiente ejemplo, los objetos Deployment y Service ilustran estos requisitos:
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-04 (UTC)"],[],[],null,["# Deploying Services\n==================\n\nDeploying Services to clusters with Cloud Service Mesh is almost the\nsame as deploying Services to clusters without Cloud Service Mesh. You do need to\nmake some changes to your Kubernetes manifests:\n\n- Create\n [Kubernetes Services](/kubernetes-engine/docs/concepts/network-overview#services)\n for all containers. All\n [Deployments](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/)\n should have a\n Kubernetes Service attached.\n\n- Name your Service ports. Although GKE allows you to\n define unnamed Service ports, Cloud Service Mesh requires that you provide a\n [name for a port](/service-mesh/v1.19/docs/naming-service-ports) that matches the port's\n protocol.\n\n- Label your Deployments. This allows you to use Cloud Service Mesh traffic\n management features such as splitting traffic between versions of the same\n service.\n\nThe following example Deployment and Service illustrate these requirements: \n\n apiVersion: apps/v1\n kind: Deployment\n metadata:\n name: helloserver\n spec:\n replicas: 1\n selector:\n matchLabels:\n app: helloserver\n template:\n metadata:\n labels:\n app: helloserver\n spec:\n containers:\n - image: gcr.io/google-samples/istio/helloserver:v0.0.1\n imagePullPolicy: Always\n name: main\n restartPolicy: Always\n terminationGracePeriodSeconds: 5\n\n apiVersion: v1\n kind: Service\n metadata:\n name: hellosvc\n spec:\n ports:\n - name: http\n port: 80\n targetPort: 8080\n selector:\n app: helloserver\n type: LoadBalancer\n\nAfter deploying your Services on a cluster with Cloud Service Mesh, be sure to\n[inject sidecar proxies](/service-mesh/v1.19/docs/anthos-service-mesh-proxy-injection).\n\nWhat's next\n-----------\n\n- [Preparing an application for Cloud Service Mesh](/service-mesh/v1.19/docs/prepare-app-for-anthos-service-mesh)\n\n- [Deploy the Online Boutique sample application](/service-mesh/v1.19/docs/onlineboutique-install-kpt)"]]