-
Notifications
You must be signed in to change notification settings - Fork 591
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
chore: use networking.knative.dev/ingress-class
additionally to networking.knative.dev/ingress.class
#2485
Merged
Conversation
This file contains 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
pmalek
changed the title
chore: rename ingress.class to ingress-class
chore: rename kubernetes.io/ingress.class to kubernetes.io/ingress-class
May 12, 2022
pmalek
changed the title
chore: rename kubernetes.io/ingress.class to kubernetes.io/ingress-class
chore: rename May 12, 2022
kubernetes.io/ingress.class
to kubernetes.io/ingress-class
pmalek
force-pushed
the
ingress-class-rename
branch
from
May 12, 2022 07:30
0b5f935
to
18e0d15
Compare
pmalek
force-pushed
the
ingress-class-rename
branch
from
May 12, 2022 07:50
18e0d15
to
6ce9cfb
Compare
pmalek
force-pushed
the
ingress-class-rename
branch
from
May 12, 2022 08:51
6ce9cfb
to
e138b33
Compare
pmalek
force-pushed
the
ingress-class-rename
branch
from
May 12, 2022 08:52
e138b33
to
4fd3cab
Compare
pmalek
changed the title
chore: rename
chore: use May 12, 2022
kubernetes.io/ingress.class
to kubernetes.io/ingress-class
ingress.class
instead of ingress-class
with knative
pmalek
changed the title
chore: use
chore: use May 12, 2022
ingress.class
instead of ingress-class
with knativeingress-class
instead of ingress.class
with knative
pmalek
force-pushed
the
ingress-class-rename
branch
from
May 12, 2022 09:21
4fd3cab
to
4d4bd1f
Compare
pmalek
force-pushed
the
ingress-class-rename
branch
from
May 17, 2022 09:58
4d4bd1f
to
6a4ee90
Compare
pmalek
force-pushed
the
ingress-class-rename
branch
from
May 17, 2022 11:32
bec86c3
to
4d6ab5d
Compare
1 task
mflendrich
reviewed
May 17, 2022
Co-authored-by: Michał Flendrich <[email protected]>
mflendrich
previously approved these changes
May 17, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
mflendrich
approved these changes
May 17, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does / why we need it:
Use
networking.knative.dev/ingress-class
as well asnetworking.knative.dev/ingress-class
annotations (with the priority on the former - added in this PR) since knative has already added support fornetworking.knative.dev/ingress-class
in knative/networking#522Which issue this PR fixes :
fixes #2344
PR Readiness Checklist:
Complete these before marking the PR as
ready to review
:CHANGELOG.md
release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR