This is a cache of https://docs.openshift.com/container-platform/4.7/service_mesh/v2x/ossm-deploy-production.html. It is a snapshot of the page at 2024-11-22T22:29:52.660+0000.
Deploying to production - <strong>service</strong> Mesh 2.x | <strong>service</strong> Mesh | OpenShift Container Platform 4.7
    OpenShift docs are moving and will soon only be available at docs.redhat.com, the home of all Red Hat product documentation. Explore the new docs experience today.
  1. Documentation
    2. history
×

Configuring service Mesh for production

When you are ready to move from a basic installation to production, you must configure your control plane, tracing, and security certificates to meet production requirements.

Prerequisites

  • Install and configure Red Hat OpenShift service Mesh.

  • Test your configuration in a staging environment.

Configuring your serviceMeshControlPlane resource for production

If you have installed a basic serviceMeshControlPlane resource to test service Mesh, you must configure it to production specification before you use Red Hat OpenShift service Mesh in production.

You cannot change the metadata.name field of an existing serviceMeshControlPlane resource. For production deployments, you must customize the default template.

Procedure

  1. Configure the distributed tracing platform for production.

    1. Edit the serviceMeshControlPlane resource to use the production deployment strategy, by setting spec.addons.jaeger.install.storage.type to Elasticsearch and specify additional configuration options under install. You can create and configure your Jaeger instance and set spec.addons.jaeger.name to the name of the Jaeger instance.

      Default Jaeger parameters including Elasticsearch
      apiVersion: maistra.io/v2
kind: serviceMeshControlPlane
metadata:
  name: basic
spec:
  version: v2.2
  tracing:
    sampling: 100
    type: Jaeger
  addons:
    jaeger:
      name: MyJaeger
      install:
        storage:
          type: Elasticsearch
        ingress:
          enabled: true
  runtime:
    components:
      tracing.jaeger.elasticsearch: # only supports resources and image name
        container:
          resources: {}

    2. Configure the sampling rate for production. For more information, see the Performance and scalability section.

  2. Ensure your security certificates are production ready by installing security certificates from an external certificate authority. For more information, see the Security section.

  3. Verify the results. Enter the following command to verify that the serviceMeshControlPlane resource updated properly. In this example, basic is the name of the serviceMeshControlPlane resource.

    $ oc get smcp basic -o yaml

Additional resources