The tech-log tenant needs objects inside platform namespaces: its database and role, ingress to Postgres and AIStor, blackbox probes, alert rules, a dashboard and two observability NetworkPolicies. They were only ever applied with kubectl and no repository holds them, so a deleted object cannot be recreated and a platform re-apply can drop tech-log access without anyone noticing. Declare them in services/tenants/techlog, copied from each object's last-applied configuration. The dashboard follows the repository's dashboard pattern (JSON file + configMapGenerator, same name, same labels). The hyeonworks-prod Namespace moves here as the tenant boundary and gets PSA enforce=baseline, warn/audit=restricted. Rejected: enforce=restricted now. A server dry-run shows all three tech-log pods would violate it; baseline has zero violations. Risk: the render matches the live objects exactly except the added PSA labels. The pg_hba rules and the Secret stay out of this root (Cluster owner and Git policy). Verification (desktop): - render-tenants-and-policies.sh passes. - kubectl diff of the render shows only the Namespace PSA labels. - kubectl label --dry-run=server enforce=baseline: no warnings.
24 lines
626 B
YAML
24 lines
626 B
YAML
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
|
|
# tech-log(hyeonworks.com) 테넌트의 플랫폼 쪽 객체. 앱 쪽 매니페스트는 tech-log repo가 소유한다.
|
|
resources:
|
|
- namespace.yaml
|
|
- platform-data.yaml
|
|
- object-storage.yaml
|
|
- observability-probes.yaml
|
|
- observability-rules.yaml
|
|
- observability-network-policies.yaml
|
|
|
|
generatorOptions:
|
|
disableNameSuffixHash: true
|
|
labels:
|
|
app.kubernetes.io/part-of: techlog
|
|
grafana_dashboard: "1"
|
|
|
|
configMapGenerator:
|
|
- name: grafana-dashboard-techlog
|
|
namespace: observability
|
|
files:
|
|
- dashboards/techlog-operations.json
|