forked from org1/infra
x
This commit is contained in:
@@ -7,7 +7,7 @@ This file records repository decisions and the guidance that follows from them.
|
||||
### DEC-001: Make the Kubernetes cluster the primary infrastructure
|
||||
|
||||
- **Decision:** New services should be deployed in the Kubernetes cluster, and services running on other instances should be migrated there.
|
||||
[kustomization.yaml](kustomization.yaml) is entry point for the Kubernetes cluster configuration.
|
||||
[kustomization.yaml](kustomization.yaml) is the entry point for the Kubernetes cluster configuration.
|
||||
|
||||
### DEC-002: Document manual operations in README.md
|
||||
|
||||
@@ -35,15 +35,15 @@ This file records repository decisions and the guidance that follows from them.
|
||||
|
||||
### DEC-008: Apply configuration through Git pushes only
|
||||
|
||||
- **Decision:** Configuration should be applied only through Git pushes. Do not apply configuration directly to infrastructure, even when access is available. An agent may apply configs directly tom infrastructure only when explicitly requested.
|
||||
- **Decision:** Configuration should be applied only through Git pushes. Do not apply configuration directly to infrastructure, even when access is available. An agent may apply configs directly to infrastructure only when explicitly requested.
|
||||
|
||||
## Draft
|
||||
|
||||
### DEC-009: Use Cilium for FQDN-based egress filtering
|
||||
|
||||
- **Context:** Standard Kubernetes NetworkPolicy rules use IPs, CIDRs, and workload selectors, while domain-based egress filtering is desirable for workloads such as Hermes. Cilium supports DNS-aware FQDN policies.
|
||||
- **Decision:** Evaluate adopting Cilium as the Kubernetes CNI and using its FQDN policies to restrict workload egress to explicitly approved domains.
|
||||
- **Consequences:** This requires a planned migration from K3s' current CNI and built-in network-policy enforcer, with compatibility, resource usage, policy behavior, and rollback tested before adoption. Existing broad egress allows must be removed or narrowed because network policies are additive.
|
||||
- **Decision:** Adopt Cilium as the Kubernetes CNI and use its FQDN policies to restrict workload egress to explicitly approved domains where domain-based filtering is required.
|
||||
- **Consequences:** This requires a planned migration from K3s' current CNI and built-in network-policy enforcer, with compatibility, resource usage, policy behavior, and rollback tested before rollout. Existing broad egress allows must be removed or narrowed because network policies are additive.
|
||||
|
||||
## Declined
|
||||
|
||||
@@ -56,5 +56,5 @@ Add each decision under its current status. Use a unique `DEC-NNN` identifier an
|
||||
### DEC-NNN: Short title
|
||||
|
||||
- **Context:** Why a decision is needed.
|
||||
- **Decision:** Rule which should be follwed by editors.
|
||||
- **Decision:** Rule that editors should follow.
|
||||
- **Consequences:** Important effects or tradeoffs.
|
||||
|
||||
Reference in New Issue
Block a user