Deploying Z APM Connect DG in a cluster
If you have a preexisting Red Hat®OpenShift®Container Platform cluster or Kubernetes cluster, Z APM Connect Distributed Gateway (Z APM Connect DG) can be deployed in these clusters to connect the Z APM Connect z/OS® components to AppDynamics.
Before you begin
If you are upgrading OpenShift deployments with a Distributed Gateway that is deployed before version 26.4.0, note that version 26.4.0 introduces an updated Red Hat OpenShift Container Platform (OCP) routes in the default configuration.
If you deploy Distributed Gateway using these new routes, you must update the z/OS components to connect to the updated OCP routes. Also, update the associated certificates and reissue them to match the new OCP route pattern.
About this task
Required configuration information for the OpenTelemetry solution
The following connection and OpenTelemetry (OTel) Collector information is required during installation and initial configuration:
- OTel connection information:
- The hostname and port number of the gRPC acceptor for your OTel Collector
- gRPC is the preferred communication protocol, but if required, HTTP(S) is supported as well
- The OTel Collector's public certificate if using TLS to secure the connection between the Z APM Connect Distributed Gateway
- If using TLS to secure the connection between Z APM Connect z/OS components and Z APM Connect distributed components, two-way authentication is enforced,
which requires the following:
- The appropriate CA certificate installed and trusted in RACF®
- A certificate with a client authentication extension installed in RACF, as well as its trust chain certificates
- A
JKSformat truststore on the distributed environment containing the appropriate CA certificate - A
JKSformat keystore on the distributed environment containing a certificate with a server authentication extension, as well as its trust chain certificates
- The hostname and port number of the gRPC acceptor for your OTel Collector
-
-
