Container Gateway REDIS/ValKey configuration issue

Products

• CA API Gateway

Issue/Introduction

trying to deploy an AWS Valkey capable container gateway.
To do so I have modified my helm chart deployment file inorder to :

Comment out the following

# com.l7tech.server.extension.sharedKeyValueStoreProvider=embeddedhazelcast
# com.l7tech.server.extension.sharedCounterProvider=ssgdb

 

Uncomment the following

# com.l7tech.server.extension.sharedKeyValueStoreProvider=redis
# com.l7tech.server.extension.sharedCounterProvider=redis
# com.l7tech.server.extension.sharedRateLimiterProvider=redis

 

As mentioned in Readme.md chart file.

Then Layer7 Container Gateway 11.1 documentation says:

Valkey Configuration

Valkey is a drop-in replacement for Redis and uses the same configuration parameters. To configure Valkey, reference the Supported YAML Configuration for Redis section for guidance on parameter settings, but replace the Redis-specific values in your YAML with the equivalent Valkey settings.

The primary change will be the connection endpoint for your Valkey instance. For example:

redis:

  default:
     keyPrefixGroupName: mygrpname
     testOnStart: true
     type: standalone
     commandTimeout: 6000
     connectTimeout: 12000
     standalone:
       host: valkey
       port: 6379
     ssl:

       enabled: false

What is unclear for me is how to provide to my helm deployment "my_values.yaml" this "sharedstate_client.yaml.file" ?

Without this "sharedstate_client.yaml.file" values, pods refuse to start.

Environment

11.1

Resolution

comment out existingConfigSecret like the below from the values.yaml if its already uncommented .

sharedStateClient:
    enabled: true
  # If you are using an existingConfigSecret for more than one shared state client that requires a tls cert, please use the customConfig section to mount
    #existingConfigSecret: shared-state-client-secret

 AWS Valkeys are in serverless mode. This Valkeys configuration only support TLS connection. thus the below configuration is the work around to solve the issue .

redis:

    enabled: true

    auth:

      enabled: false

    sentinel:

      enabled: false

    standalone:

      host: ***********************************.com

      port: 6379

    tls:

      enabled: true

      redisCrt: |+

        -----BEGIN CERTIFICATE-----

**************************************************************
**************************************************************

      ------END CERTIFICATE-----

      verifyPeer: false