Restarting the Analytics client endpoint

Restart the pods that support the Analytics client endpoint in your API Connect deployment.

About this task

The client endpoint contains the external certificates that secure communications with the Analytics subsystem. The default names of the secrets for these certs are ingress-ca, analytics-ac-endpoint (server), and analytics-client-client (client).

When you refresh the certificates for the client endpoint, restart the NGINX configuration and the Analytics pods by completing the following steps.

Procedure

  1. Reload the NGINX configuration in the analytics-mtls-gw pod by running the following command: 
    kubectl -n namespace exec analytics-mtls-gw -- openresty -s reload
    where:
    • namespace is the namespace where Analytics is installed.
    • analytics-mtls-gw is the name of the analytics-mtls-gw pod.
  2. Restart the analytics-proxy pods by running the following command: 
    kubectl -n namespace delete po -l app.kubernetes.io/name=analytics-proxy,app.kubernetes.io/instance=CR_name
    where:
    • namespace is the namespace where Analytics is installed.
    • CR_name is the name of the CR used for installing the Management subsystem (default is management).
  3. Verify that the Analytics subsystem is working correctly by opening the Analytics user interface in both Portal and API Manager services.
    Note: Due to a known issue, when the ingress-ca is renewed, it is possible that Analytics in the Developer Portal might stop working. If this happens, complete the following steps to ensure that certificate changes take effect:
    1. Log in to the Cloud Manager user interface.
    2. In the navigation list, click Topology Topology.
    3. Edit the Analytics service.
    4. On the Analytics page, edit the Summary field to force a change; for example, by adding a space to the end of a sentence.
    5. Click Save.