docs: add NetworkPolicy example manifests#2064
Open
yosofbadr wants to merge 2 commits into
Open
Conversation
cert-manager-prow
Bot
added
do-not-merge/work-in-progress
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
✅ Deploy Preview for cert-manager ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
Add concrete, ready-to-use Kubernetes NetworkPolicy manifests to the best-practice documentation. These examples cover: - Default deny-all baseline policy - DNS egress for all components - HTTPS/HTTP egress for API server and ACME endpoints - Webhook ingress from the Kubernetes API server - Webhook ingress from startupapicheck - Metrics port ingress for Prometheus scraping - HTTP01 acmesolver pod ingress on port 8089 The existing documentation describes network requirements and Helm chart values, but users on clusters with restrictive NetworkPolicy (e.g. Calico default-deny) have reported difficulty translating those requirements into working manifests. Ref: cert-manager/cert-manager#2334 Signed-off-by: Yosof Badr <23705518+YosofBadr@users.noreply.github.com>
yosofbadr
force-pushed
the
docs/network-policy
branch
from
27d5add to
2ecb8cb
Compare
cert-manager-prow
Bot
added
dco-signoff: yes
cert-manager-prow
Bot
removed
the
do-not-merge/work-in-progress
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
NetworkPolicymanifests to the best-practice pagecontent/docs/andcontent/v1.19-docs/Why
Issue cert-manager/cert-manager#2334 collected reports from users running restrictive NetworkPolicy configurations (Calico, Cilium, etc.) who struggled to translate cert-manager's documented network requirements into working manifests. The best-practice page already describes the required traffic flows and provides Helm chart values, but does not include standalone
NetworkPolicyresources that users can adapt.A project maintainer noted in cert-manager/website#1344 that example manifests would be welcome in follow-up PRs.
This PR complements cert-manager/website#2041, which adds cross-references from the HTTP01 guide to the best-practice page.
Test plan
Ref: cert-manager/cert-manager#2334