Signed-off-by: Greg Schohn <[email protected]>

There's a testObservability chart that will deploy jaeger, prometheus, and grafana - testing values are within the helmValues/localTesting/testObservability.yaml file.

Signed-off-by: Greg Schohn <[email protected]>

… to be deployed hierarchically via helm packages

Signed-off-by: Greg Schohn <[email protected]>

…to work as expected.

Jaeger & Prometheus have been deployed, but I don't have a collector and haven't confirmed that they're behaving as expected.
I still need to 1) setup kafka, flip the proxy to write to kafka; 2) setup the replayer 3) setup otel-collectors; 4) setup RFS.

Signed-off-by: Greg Schohn <[email protected]>

… package.

Signed-off-by: Greg Schohn <[email protected]>

Signed-off-by: Greg Schohn <[email protected]>

Signed-off-by: Greg Schohn <[email protected]>

…HEAD

Signed-off-by: Tanner Lewis <[email protected]>

Signed-off-by: Tanner Lewis <[email protected]>

Signed-off-by: Tanner Lewis <[email protected]>

Signed-off-by: Tanner Lewis <[email protected]>

Signed-off-by: Tanner Lewis <[email protected]>

Signed-off-by: Tanner Lewis <[email protected]>

Signed-off-by: Tanner Lewis <[email protected]>

…ared library WIP

Signed-off-by: Tanner Lewis <[email protected]>

Signed-off-by: Tanner Lewis <[email protected]>

Signed-off-by: Greg Schohn <[email protected]>

Signed-off-by: Tanner Lewis <[email protected]>

…nsearch-migrations into KubernetesExperimentation

…refactoring

Signed-off-by: Tanner Lewis <[email protected]>

Signed-off-by: Tanner Lewis <[email protected]>

Signed-off-by: Tanner Lewis <[email protected]>

Signed-off-by: Greg Schohn <[email protected]>

…o this too. This commit also creates general purpose helper scripts.

Helper scripts for the chart to handle threading command line params through ConfigMaps and into the command line.  This takes parameters from the values file and put them into ConfigMaps, always creating an immutable one for a default and possibly another for the user to override the setting at runtime.  That runtime configmap is created with no value.

The pod itself pulls the configmap values in as env variables, preferring the overridden one if it was present.  It then strings all of those into the command line invocation.
Notice that there are 3 types of values for parameters - ones with arity 0, arity 1, and arity > 2.  For arity 0, the keyname will be 'present', for arity 1, the keyname=value, and for greater arities, the data should be passed as a yaml list via the keyname 'list'.  For lists, we'll use yq and xargs to parse the contents of the yaml list to turn that into the command line - so those two utilities need to be present in the image that we're running in to take advantage of that feature.

Signed-off-by: Greg Schohn <[email protected]>

…talling the capture proxy by itself.

Signed-off-by: Greg Schohn <[email protected]>

…ates.

Example syntax: `helm template charts/valueGenerator --set-file "proxy=helmValues/localTesting/captureProxy.yaml"  --set-file "source=helmValues/localTesting/sourceElasticsearchCluster.yaml" --set-file "target=helmValues/localTesting/targetOpenSearchCluster.yaml"   | grep -v "^---$" | helm install mcc charts/aggregates/mockCustomerClusters -f - --dry-run`

Signed-off-by: Greg Schohn <[email protected]>

…verall).

Signed-off-by: Greg Schohn <[email protected]>

…ponent/captureProxy or aggregates/mockCustomerClusters.

To install the aggregate package, run the values through a pre-template first, e.g.:
```
helm template charts/valueGenerator --set-file "proxy=helmValues/localTesting/captureProxy.yaml"  --set-file "source=helmValues/localTesting/sourceElasticsearchCluster.yaml" --set-file "target=helmValues/localTesting/targetOpenSearchCluster.yaml"   | grep -v "^---$" | helm install ma charts/aggregates/mockCustomerClusters -f -
```

Signed-off-by: Greg Schohn <[email protected]>

… that they'll follow the same conventions as the other files in this directory.

The expectation is that these support independent installs for those charts OR will be used in an aggregate install but only after applying the valueGenerator template.

Signed-off-by: Greg Schohn <[email protected]>

… working toward bringing the console and proxy into the main MA chart.

Notice that the proxy is still available as a standalone chart or through the mockCustomerClusters

Signed-off-by: Greg Schohn <[email protected]>

…variables across pods.

Signed-off-by: Greg Schohn <[email protected]>

Signed-off-by: Greg Schohn <[email protected]>

This helps canonicalize parameter passing from configs.

Signed-off-by: Greg Schohn <[email protected]>

…pods.

All containers will use an initContainer to setup their arguments from configMaps.  That will require restarting the pod to pickup new configs, but I want require full-recycling anyway (as the applications re easier to write and manage).
BulkLoad won't come up because it requires some runtime parameters.
Console uses a sidecar to update /etc/migration_services.yaml w/ the help of a new container/image that runs some python code to monitor the configs and write to a shared file.
Replayer requires more work to support it - positional argument parsing support needs to be added; shared configs; and aliases for parameter names (--otelCollectorEndpoint may be the same or might be different for different services...
We should namespace the configMaps w/ the service name - and global ones will be just that... that might complicate the sidecar logic, but we'll see.

Signed-off-by: Greg Schohn <[email protected]>

…agement for resources.

Signed-off-by: Greg Schohn <[email protected]>