Skip to content

docs: warn about the ingress objects renaming consequences #182

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
MoisesGSalas merged 1 commit into from
May 14, 2026
Merged

docs: warn about the ingress objects renaming consequences #182

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
9 changes: 9 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,15 @@ See the fragment files in the [changelog.d/ directory](./changelog.d).
`-tls` was also removed from additional ingresses defined via
`DRYDOCK_INGRESS_EXTRA_HOSTS`.

> [!WARNING]
>
> This rename will cause errors with the Ingress NGINX validation webhook
> due to two different ingress objects registering the same routes.
>
> The old ingress objects must be deleted before applying the new
> changes. Either perform a manual delete or set `DRYDOCK_INGRESS` to false
> to delete all ingress objects in the next apply.

<a id='changelog-21.1.0'></a>
## 21.1.0 — 2026-04-17

Expand Down