jklein
77b978d669
Major, as every chart in this rollout is. Inbound 3000 only; outbound DNS plus 5432, 6379 and 443. Those three egress ports are the STANDARD ones and not the configured ones, which is this chart's real limitation and is written into values.yaml, the template header and NOTES.txt rather than left to be discovered: Outline's database, Redis and OIDC provider all arrive as connection URLs inside 1Password items that the chart never parses, so it cannot know where they listen and cannot validate a guess. A dependency on another port is blocked, and because all three probes hit /_health - which checks Postgres and Redis - the symptom is a pod that never becomes Ready rather than an error anyone reads. networkPolicy.egress.extraPorts is the escape hatch. That same property is what makes this chart the right place for the enforcement experiment in the next commit. Also reverts the cyberchef fixture from the first experiment: with the probe port restricted to an address that is not the node's, the install-test went GREEN, so the claim that it catches a blocked probe path does not hold as written. The next commit establishes whether policies are enforced in CI at all. Part of #5
12 lines
268 B
YAML
12 lines
268 B
YAML
apiVersion: v2
|
|
name: outline
|
|
description: A Helm chart to deploy Outline on Kubernetes
|
|
icon: https://raw.githubusercontent.com/outline/outline/main/public/images/icon-512.png
|
|
|
|
type: application
|
|
|
|
version: 8.0.0+up1.10.1
|
|
appVersion: 1.10.1
|
|
|
|
maintainers:
|
|
- name: jklein |