When specifying the REDIS_PASSWORD as a customEnv override via helm for the extauth and rate-limit deployment. The default REDIS_PASSWORD and overrides password value are both in the resultant deployment.
This is an optimization to reduce the time it takes to build/deploy YAStack.
Compilation of YAStack can be optimized by pre-compiling source code that does not depend on DPDK. This can help build the image faster since now only DPDK and dependent code will have to be compiled.
We already have the tooling and we can run envoy-control locally while connecting to an environment set up with docker-compose. However, current configuration files aren't utilizing more advanced features, like mTLS and RBAC. That hinders experimenting and testing with these functionalities. Also, creating a configuration for envoy-control and envoy connecting to is from the ground up every time I
This project repo contains a simple set codes and explanations which can enable someone to set up Envoy as a load balancer with the combination of headless service on Kubernetes cluster
This example demonstrates the example for acheiving 2way ssl on both ingress ( inward traffic) as well as egress ( outward network traffic ) using Envoy
Gloo Edge Version
1.11.x (latest stable)
Kubernetes Version
No response
Describe the bug
When specifying the
REDIS_PASSWORDas a customEnv override via helm for the extauth and rate-limit deployment. The defaultREDIS_PASSWORDand overrides password value are both in the resultant deployment.Steps to reproduce the bug