[Feature] Support TLS for inter-node and client-to-cluster connections
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- go, kubernetes, redis
- 领域
- backend, devops, infrastructure, security
调研方向
从内部提案文档 09-tls-support.md 开始，然后检查其中指出的 RedkeyCluster CRD、operator、Robin、Redis 配置、probes、Makefile 和示例 manifests。追踪配置、Secret 挂载、客户端连接和集群连接目前是如何组装的。完成的标准是：opt-in TLS 保持现有行为，覆盖列出的流量路径，支持轮换和 mTLS 要求，并通过证书工作流完成文档化。
由索引模型根据 Issue 内容生成。
描述
Feature description
Summary
Redkey currently does not support TLS encryption for Redis traffic. All
communication happens in plaintext, both between cluster nodes (cluster bus
/ gossip and replication) and from clients to the cluster. We would like to
propose adding optional TLS support so that all Redis connections can be
encrypted.
Problem / Motivation
Today, a RedkeyCluster exposes and uses unencrypted Redis connections:
- Client → Redis: application traffic travels in plaintext.
- Redis → Redis: the cluster bus (node-to-node gossip) and replication
streams are unencrypted. - Robin → Redis: management commands and metrics collection are unencrypted.
This is a blocker for:
- Compliance: regulatory frameworks such as PCI-DSS and SOC 2 require
encryption of data in transit. - Zero-trust networking: Kubernetes
NetworkPolicyonly protects at L4;
TLS adds encryption at the transport layer. - Multi-tenant clusters: without TLS, Redis traffic can be observed by other
workloads sharing the network.
Proposed Solution
Add an opt-in, disabled-by-default TLS configuration to the RedkeyCluster
CRD. When enabled, all Redis connections (client, cluster bus, replication, and
Robin management traffic) are encrypted.
High-level scope:
- CRD: new
spec.tlsblock referencing a Kubernetes TLSSecret
(tls.crt,tls.key,ca.crt), with an option to enable mutual TLS (mTLS)
between nodes. - Operator: when TLS is enabled, inject the relevant
redis.confsettings
(tls-port,tls-cert-file,tls-key-file,tls-ca-cert-file,
tls-replication yes,tls-cluster yes), mount the certificate Secret into
the Redis pods, and update liveness/readiness probes to useredis-cli --tls. - Robin: support TLS when connecting to Redis (go-redis
tls.Config) and
when invokingredis-clisubcommands (--tls --cert --key --cacert). - Certificate management: the operator consumes an existing Secret and does
not generate certificates. Certificate lifecycle is managed externally
(cert-manager recommended, with support for manual OpenSSL generation or an
external PKI such as HashiCorp Vault).
Example CRD usage
apiVersion: redkey.inditex.dev/v1beta1
kind: RedkeyCluster
metadata:
name: redkeycluster-sample
spec:
primaries: 3
image: redis:7.4.2
tls:
enabled: true
secretName: redkey-tls
mutualTLS: true
Requirements
- TLS is opt-in and disabled by default; existing clusters keep
working unchanged. - Encrypt client → cluster connections.
- Encrypt node → node connections (cluster bus and replication).
- Encrypt Robin → Redis management and metrics traffic.
- Optional mutual TLS (mTLS) between cluster nodes.
- Certificates are provided via an external Kubernetes
Secret; the
operator does not generate them. - Documented certificate workflow (cert-manager, OpenSSL, external PKI).
- Support for certificate rotation without data loss.
Out of Scope
- Automatic certificate generation by the operator.
- Certificate authority (CA) lifecycle management.
Additional Context
A detailed technical design (CRD changes, operator and Robin changes, certificate
generation options, Makefile integration, sample manifests, rotation, and
compatibility) is available in the internal proposal document
09-tls-support.md.
Use case or motivation
No response
Would you like to work on this?
Yes, I'd like to open a PR
- 主要语言
- Go
- 星标
- 20
- 派生
- 2
- 平均合并
- 1 天 18 小时
- 30 天内合并 PR
- 11
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
InditexTech/redkey-operator 的其他 Issue
-
[Feature] Set RevisionHistoryLimit on the generated Robin Deployment to bound retained ReplicaSets未关闭enhancement
难度 2/5 1-3 小时 新手友好度 75/100
InditexTech/redkey-operator#87 ·
维护者通常 2 天内回复
-
[Bug] Rolling N+1 upgrade stalls forever on persistent clusters (deletePVC: false) after a second consecutive upgrade可能已有人在做 @albertompe 于 1 天前认领。 未关闭bug
InditexTech/redkey-operator#102 · 已指派 1 人 ·
维护者通常 2 天内回复
-
[Feature] Inject the operator version at build time via -ldflags instead of a hardcoded constant未关闭enhancement
难度 3/5 1-2 天 新手友好度 70/100
InditexTech/redkey-operator#88 ·
维护者通常 2 天内回复
-
enhancement
难度 3/5 1-2 天 新手友好度 65/100
InditexTech/redkey-operator#86 ·
维护者通常 2 天内回复
-
[Feature] Apply hardened securityContext and default resources to the generated Robin Deployment未关闭enhancement
难度 4/5 3-5 天 新手友好度 45/100
InditexTech/redkey-operator#85 ·
维护者通常 2 天内回复
查看 InditexTech/redkey-operator 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 77/100
维护者通常 1 天内回复
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:session-state issue-rating: 🦞 diamond lobster no-stale P2
难度 2/5 1-3 小时 新手友好度 74/100
openclaw/wacli#503 · 1 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 81/100
apache/rocketmq-dashboard#6895 ·
维护者通常 3 天内回复
-
agent-butler-finding chore
难度 1/5 1 小时以内 新手友好度 88/100
jordansmall/spindrift#5466 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 92/100
open-telemetry/opentelemetry-go-compile-instrumentation#1507 ·
维护者通常 3 天内回复