-
Notifications
You must be signed in to change notification settings - Fork 404
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
POC: Hydra + Oathkeeper #3878
Merged
Merged
POC: Hydra + Oathkeeper #3878
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
jakkab
added
kind/feature
Categorizes issue or PR as related to a new feature.
area/security
Issues or PRs related to security
area/service-mesh
Issues or PRs related to service-mesh
labels
Apr 26, 2019
jakkab
force-pushed
the
hydra-oathkeeper-poc
branch
from
April 30, 2019 08:42
3bffd4f
to
99eec78
Compare
jakkab
requested review from
kazydek,
kfurgol,
klaudiagrz,
kubadz,
lszymik,
mmitoraj,
mszostok,
pbochynski,
piotrmiskiewicz,
piotrmsc,
PK85,
polskikiel,
sjanota,
strekm,
Tomasz-Smelcerz-SAP and
tomekpapiernik
as code owners
April 30, 2019 10:20
/test pre-master-kyma-integration |
strekm
approved these changes
May 6, 2019
piotrmsc
suggested changes
May 6, 2019
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.
First bunch of review
kfurgol
approved these changes
May 7, 2019
In the first iteration let's leave oathkeeper apiserver exposed like it is right now, we will think of using only one host in the future |
/test pre-master-kyma-gke-upgrade |
piotrmsc
approved these changes
May 7, 2019
tomekpapiernik
approved these changes
May 7, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/security
Issues or PRs related to security
area/service-mesh
Issues or PRs related to service-mesh
kind/feature
Categorizes issue or PR as related to a new feature.
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.
Description
Changes proposed in this pull request:
Related issue(s)
#3399