Separate Redis for Non Core Components

Redis is already part of the CX deployment and is currently used to cache data for the CX core system. However, several non-core components—such as the Controller, Campaign Manager, and Survey—also store data in the same Redis instance. To ensure optimal Redis performance and maintain clear data separation between core and non-core systems, it is highly recommended to deploy a separate Redis instance for the non-core components.

The redis intance used by CX core is part if ef-external namespace. To install redis for your components create separate namespace i.e. ef-controller using following command.
```
kubectl create namespace <NameofNameSpace>
```

You can change the default Redis password by updating the password field under the auth section in the cim-solution/kubernetes/external/bitnami/redis/values.yaml file.

auth:
  ## @param auth.enabled Enable password authentication
  ##
  enabled: true
  ## @param auth.password Redis&reg; password
  ## Defaults to a random 10-character alphanumeric string if not set
  ##
  password: "Expertflow123"  # Change this to match the requirements

Run the following command to deploy Redis. Make sure to replace the <NameSpaceName> with actual name.

helm upgrade --install=true --wait=true --timeout=10m0s --debug --namespace=<NameSpaceName> --values=external/bitnami/redis/values.yaml redis external/bitnami/redis/