cscott/apigateway-ocp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
c0176091292f6f37bf82520bc7e4b03398808994
apigateway-ocp/apigateway/charts/v7-traceability/README.md
Conan Scott 555c441ad1 Updated to 7.7.0.20250830-3-BN0276-ubi 
Updated ANM destinationCertCA for 7.7.0.20250830-3-BN0276-ubi
2025-11-20 15:56:45 +08:00

1.2 KiB
Raw Blame History

Helm chart

Prerequisites

Before the chart can be installed make sure to have the secrets installed/available.

i.e if you look at line 31(secrets) in the values.yaml file, you will notice we are referencing two files.

Required credentials can be applied by using the below format for the secret. Make sure all the values are base64 encoded before applying it in the cluster.

kubectl apply -f <creds-FILENAME.yaml>

apiVersion: v1
kind: Secret
metadata:
  name: traceability-creds
type: Opaque
stringData:
  APIMANAGER_AUTH_USERNAME: ""
  APIMANAGER_AUTH_PASSWORD: ""
  APIGATEWAY_AUTH_USERNAME: ""
  APIGATEWAY_AUTH_PASSWORD: ""

kubectl apply -f <keys-FILENAME.yaml>

apiVersion: v1
kind: Secret
metadata:
  name: traceability-keys
data:
  private_key: <PRIVATE_KEY_BASE64>
  public_key: <PUBLIC_KEY_BASE64>

Limitations

The traceability agent requires a 1 to 1 relationship of agent to events volume. Within your overrides it is important to specify a nodeSelector and/of affinity so the daemon set is deployed to exactly 1 node. By default the traceability agent will deploy to a node with a label named traceability-agent and value of "true".