Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Unify CA certificate configuration for Trino, PostgreSQL and S3 storage

未关闭
#383 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript
领域
backend, security

调研方向

Start by tracing the three CA settings named in the issue: Trino, PostgreSQL, and S3 storage, including their Helm validation and Secret Operator volume configuration. Decide how shared CA configuration should coexist with system trust and public endpoints, then define how invalid certificates prevent startup. Done means the duplicated configuration is unified and all three stated problems are addressed.

由索引模型根据 Issue 内容生成。

描述

Cockpit has three independent CA certificate settings, all implemented the same way:

Trino
STACKABLE_COCKPIT_TRINO_TLS_CA_CERT
trino.tls.caCert / secretClass

PostgreSQL
DATABASE_TLS_CA_CERT
database.tls.caCert / secretClass

S3 storage
STACKABLE_COCKPIT_STORAGE_TLS_CA_CERT
storage.tls.caCert / secretClass

Problems

  • One CA replaces all trust: each setting replaces the system trust store. For S3 that's a real limitation: once a CA is set, connections to public endpoints such as AWS S3 fail, so an internal and a public object store can't be used side by side.
  • Duplicated code: reading the file, error handling, Helm validation and the Secret Operator volumes are written out three times.
  • Nothing stops the app from starting if a certificate is invalid
主要语言
TypeScript
星标
1
派生
0
平均合并
4 天 3 小时
30 天内合并 PR
16

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

stackabletech/cockpit 的其他 Issue

查看 stackabletech/cockpit 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。