@dmgnr/kuber 2.1.0 → 2.2.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +14 -0
- package/dist/index.js +99 -98
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -28,6 +28,20 @@ a per-project namespace, reconciles managed Postgres and S3 claims, rolls
|
|
|
28
28
|
deployments back, streams logs, and exposes interactive `exec` sessions over a
|
|
29
29
|
WebSocket.
|
|
30
30
|
|
|
31
|
+
## Directory Trust
|
|
32
|
+
|
|
33
|
+
Before `kuber up`, run `kuber trust` from the configured project directory.
|
|
34
|
+
Trust is exactly the configured namespace plus a SHA-256 fingerprint of the
|
|
35
|
+
resolved current working directory. The local mode-0600 store lets `up` fail
|
|
36
|
+
before builds from an untrusted directory. The server stores only namespace and
|
|
37
|
+
fingerprint registrations in labelled ConfigMaps in its `kuber-system` control
|
|
38
|
+
plane namespace, then checks the pair when resource reconciliation begins.
|
|
39
|
+
|
|
40
|
+
This is an accidental-targeting safeguard, not a security boundary: a client
|
|
41
|
+
that intentionally forges a registered fingerprint can pass it. `kuber trust
|
|
42
|
+
status` shows local/server awareness without printing paths; `kuber trust revoke`
|
|
43
|
+
removes the current directory registration.
|
|
44
|
+
|
|
31
45
|
## Environment Assumptions
|
|
32
46
|
|
|
33
47
|
kuber targets a specific self-hosted cluster and workstation setup. It is not
|