open-source/qinglong
1
0
Fork 0
mirror of https://github.com/whyour/qinglong.git synced 2026-09-20 16:07:11 +08:00
Code Issues Packages Projects Releases Wiki Activity

feat(ql3): expose cluster secret binding management

Browse Source
This commit is contained in:
whyour
2026-08-13 15:41:59 +08:00
parent 7016903fba
commit 73eeaed4de
13 changed files with 1127 additions and 48 deletions
Download Patch File Download Diff File Expand all files Collapse all files
deploy/kubernetes/ql3-cluster/README.md
+6 -1
View File
@@ -451,7 +451,12 @@ become trusted by restarting every replica. Server TLS certificate rotation
requires a controlled Pod rollout because TLS material is loaded only at
process startup.
This deployment exposes only `propose`, `decide`, and low-sensitive `inspect`.
This deployment exposes only reviewed Package proposal/decision/inspection,
installation inventory, lifecycle review, publisher trust review, and
content-free Secret binding `plan|propose|decide|inspect`. Secret binding plans
derive generation and digests from PostgreSQL; the caller supplies only logical
requirements and fixed-version same-Project Secret references. The management
Pods never receive projected Secret values or package-executor database authority.
It has no Kubernetes API token or RBAC, no Registry credential, and no Package
executor/admin/runtime database identity. Process-local rate limiting is a
bounded anonymous-traffic shield, not a distributed quota. Authenticated