Skip to content

fix: add egress NetworkPolicy for CA extractor on OCP 4.22 #166

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
p-rog wants to merge 2 commits into
base: main
Choose a base branch
from
+50 −0
Open

fix: add egress NetworkPolicy for CA extractor on OCP 4.22 #166

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1abbcf0
fix: add egress NetworkPolicy for CA extractor on OCP 4.22
p-rog Jul 23, 2026
847445d
docs corrections about 4.22
p-rog Jul 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 38 additions & 0 deletions charts/ztvp-certificates/templates/ca-extractor-netpol.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
{{- if .Values.enabled }}
---
# Egress NetworkPolicy for the CA extractor Job/CronJob.
# Required on OCP 4.22+ where platform-managed default-deny-all
# NetworkPolicies block all egress from pods in openshift-config.
# On OCP 4.21 and earlier this policy is harmless (no default-deny exists).
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: {{ include "ztvp-certificates.fullname" . }}-ca-extractor-allow-egress
namespace: {{ .Values.global.namespace }}
annotations:
argocd.argoproj.io/sync-wave: "22"
labels:
{{- include "ztvp-certificates.labels" . | nindent 4 }}
spec:
podSelector:
matchLabels:
{{- include "ztvp-certificates.selectorLabels" . | nindent 6 }}
policyTypes:
- Egress
egress:
# Kubernetes API server — port-only rule because API endpoints
# are node IPs after DNAT and cannot be matched by podSelector
- ports:
- protocol: TCP
port: 6443
# CoreDNS — OCP uses port 5353 (not 53)
- ports:
- protocol: TCP
port: 5353
- protocol: UDP
port: 5353
to:
- namespaceSelector:
matchLabels:
kubernetes.io/metadata.name: openshift-dns
{{- end }}
12 changes: 12 additions & 0 deletions docs/DEVELOPMENT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,18 @@

This document describes recommended practices for developing and testing against this pattern.

## Supported OCP Versions

This pattern is tested and supported on the following OpenShift Container Platform versions:

| OCP Stream | Status | Notes |
|---|---|---|
| **< 4.20** | Usupported | |
| **4.20** | Supported | Tested and verified |
Comment thread
p-rog marked this conversation as resolved.
| **4.21** | Supported | Tested and verified |

Running the pattern on untested OCP versions may result in operator subscription failures or NetworkPolicy-related deployment issues.

## Testing Environments

While you may bring your own (BYO) OpenShift cluster, Red Hat associates and partners may utilize [Red Hat Demo Platform (RHDP)](https://catalog.demo.redhat.com) to provision OpenShift environments for use as targets for pattern development and testing.
Expand Down
Loading