Skip to content

Improve docs for fargate networking to avoid confusion #698

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

Merged
jetstack-bot merged 1 commit into from
Sep 14, 2021
Merged

Improve docs for fargate networking to avoid confusion #698

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
10 changes: 7 additions & 3 deletions content/en/docs/installation/compatibility.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,9 +74,13 @@ port; see the warning at the top of the page for details.

### AWS Fargate

It's worth noting that using AWS Fargate to run cert-manager will force you to
run using the host's network, and will force a port clash with the kubelet
running on port 10250, as seen in [#3237](https://github.com/jetstack/cert-manager/issues/3237).
It's worth noting that using AWS Fargate doesn't allow much network configuration and
will cause the webhook's port to clash with the kubelet running on port 10250, as seen
in [#3237](https://github.com/jetstack/cert-manager/issues/3237).

When deploying cert-manager on Fargate, you _must_ change the port on which
the webhook listens. See the warning at the top of this page for more details.

Because Fargate forces you to use its networking, you cannot manually set the networking
type and options such as `webhook.hostNetwork` on the helm chart will cause your
cert-manager deployment to fail in surprising ways.