Bouncer server proxy with Redis Sentinel Error #16
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What append :
The redirections don't work with Redis Sentinel
How to reproduce:
1°) Setup a Kubernetes cluster (with kind or whatever)
2°) Checkout the feat/issue-10/add-k8s-kustomize branch
3°) Deploy the developpement overlay with the command :
kubectl apply -k misc/k8s/overlay/dev
4°) Forward the port for the service bouncer-admin (8081) with kubectl port-forward or k9s
5°) Forward the port for the service boucner-proxy(8080) with kubectl port-forward or k9s
6°) Follow the bouncer doc "getting-started"
7°) Try to access the bouncer proxy after the redirection creation.
Error log from Bouncer
You also can use the command :
from
feat/issue-10/add-k8s-kustomize
branchLe problème provenait d'une mauvaise configuration de Bouncer vis à vis de l'utilisation du mode "sentinel" de Redis. Pour faire court, la bonne configuration était la suivante:
cf. la documentation de l'opérateur Redis: https://github.com/spotahome/redis-operator?tab=readme-ov-file#connection-to-the-created-redis-failovers
J'ai également profité de l'occasion pour mettre en place une procédure de démarrage plus complète de l'environnement de test Kubernetes, disponible à l'adresse suivante:
6f61073d1f/misc/k8s
Le correctif de la configuration est poussé sur la branche.