-
Infra Task
-
Resolution: Merged
-
Should have
-
None
-
None
-
Connections to redis pods are not secured by passwords, meaning any pod in the namespace (cluster) can read and write to other redis instance in cluster.
- [ ] Create redis connection secret in helm chart
- [ ] Password protect wordpress connection
- [ ] Password protect openresty connection
- [ ] Ensure connections from command line / helper scripts work as expected
Connections to redis pods are not secured by passwords, meaning any pod in the namespace (cluster) can read and write to other redis instance in cluster. [ ] Create redis connection secret in helm chart [ ] Password protect wordpress connection [ ] Password protect openresty connection [ ] Ensure connections from command line / helper scripts work as expected
Connections to redis pods are not secured by passwords, meaning any pod in the namespace (cluster) can read and write to other redis instance in cluster.
- [ ] Create redis connection secret in helm chart
- [ ] Password protect wordpress connection
- [ ] Password protect openresty connection
- [ ] Ensure connections from command line / helper scripts work as expected
As per https://github.com/pantheon-systems/wp-redis/blob/master/object-cache.php#L1071 I believe the authentication parameter for `$redis_server` is 'auth' but tbc
- blocks
-
-
- CLOSED
-