External access

Agility needs access to the following public endpoints in order to work

HTTP Proxy configuration

If the network where AGILITY is running requires an HTTP proxy setup to access Internet, follow these instructions:

Deploy the AGILITY Services chart

1. Create an override values file

   cd agility-charts vi agility-services-values-overrides.yaml

   Update agility-operator.env.manager.httpProxy options

   agility-operator: env: manager: httpProxy: httpProxy: <<http://example.com:3128>> httpsProxy: <<http://example.com:3128>> noProxy: <10.0.0.0/8,172.16.0.0/12,192.168.0.0/16>

   • httpProxy: HTTP Proxy setting, with URL format. Regular expression: ^https?:\\/\\/.+$.

   • httpsProxy: HTTPS Proxy setting, with URL format. Regular expression: ^https?:\\/\\/.+$.

   • noProxy: No Proxy setting, comma separated list of network addresses and/or domain names.

   noProxy should at least include the Kubernetes Services network address.

   For example, if the Kubernetes Services network address is 10.43.0.0/16. Then, the values should looks like:

   agility-operator: env: manager: httpProxy: httpProxy: <http://example.com:3128> httpsProxy: <http://example.com:3128> noProxy: 10.43.0.0/16

Deploy the AGILITY application chart

1. Create an override values file (options available in the AGILITY chart):

   Update cv.httpProxy options

   • httpProxy: HTTP Proxy setting, with URL format. Regular expression: ^https?:\\/\\/.+$.

   • httpsProxy: HTTPS Proxy setting, with URL format. Regular expression: ^https?:\\/\\/.+$.

   • noProxy: No Proxy setting, comma separated list of network addresses and/or domain names.

Disable remote monitoring (central-monitoring.b-yond.com) and data report (AWS bucket)

AGILITY sends anonymous usage data collection to B-Yond. This can be disabled following these instructions:

Deploy the AGILITY application chart

1. Create an override values file (options available in the AGILITY chart):

   Update cv.agilityOpenTelemetry.settings.remote.enabled and cv.settings.sharePcapInformation options

Enable customer monitoring

AGILITY can send metrics to a compliant Open Telemetry collector.

1. Create an override values file (options available in the AGILITY chart):

   Update cv.agilityOpenTelemetry.settings.customer options

   Complete based on the following options:

   • enabled: <boolean> -required-

     • Enables a customer to route Agility data to a compliant Open Telemetry collector. Default value: false

   • endpoint: <string> -required-

     • URL Endpoint where to send OpenTelemetry data. If useHttps is true, ensure to match the following pattern: ^https?:\\/\\/.+$. For example: https://example.com. If useHttps is false, ensure to match the following pattern: ^.*:[0-9]+$. For example: example.com:4317

   • tlsInsecure: <boolean>

     • Do not validate TLS certificate

   • tlsSecret: <Object>

     • The secret containing the Certificates and Key to encrypt OpenTelemetry traffic will need to contain the TLS certificate, TLS key and TLS certificate authority with the data keys set to tls.crt, tls.key and http://tls.ca , respectively. It will then be mounted as a volume projection to the '/tmp/oteltls' directory. For more information on Kubernetes secret projections, please see <Secrets >. NOTE: If tlsInsecure is true, this value will be ignored.

   • useHttps: <boolean>

     • Use HTTPS protocol instead of gRPC protocol. Default value: true