Skip to content
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.

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

add documentation about deny-wildcard annotation #433

Merged
merged 2 commits into from
Sep 23, 2021
Merged

Conversation

alegrey91
Copy link
Contributor

fixes #219.

@alegrey91 alegrey91 added the documentation Improvements or additions to documentation label Sep 23, 2021
@alegrey91 alegrey91 added this to the v0.1.1 milestone Sep 23, 2021
Copy link
Member

@prometherion prometherion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just needs to be rebased over the latest master.

@prometherion prometherion merged commit 7db263b into master Sep 23, 2021
@prometherion prometherion deleted the issue/219-2 branch September 23, 2021 16:34
@aminmr
Copy link

aminmr commented Sep 8, 2024

I have a specific domain for my customers, such as freeexample.com, which is available for general use. However, for certain special users, I need to restrict access to creating an ingress with this domain. Do you have any ideas on how to achieve this?
@prometherion

@prometherion
Copy link
Member

@aminmr I would suggest you use the Slack workspace channel to ask for more information about the Capsule features.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Make programmable deny of wildcard hostnames
3 participants