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

Helm chart for oathkeeper #186

Closed
piotrmsc opened this issue May 7, 2019 · 6 comments
Closed

Helm chart for oathkeeper #186

piotrmsc opened this issue May 7, 2019 · 6 comments

Comments

@piotrmsc
Copy link

piotrmsc commented May 7, 2019

Is your feature request related to a problem? Please describe.

I found out sample yaml file with oathkeeper here, however, it would be really nice to have helm chart (like you already created with hydra).
Describe the solution you'd like
Have the possibility to run just helm install ... with possible overrides and have oathkeeper up and running in the cluster.

Describe alternatives you've considered

Additional context
We are currently driving a POC in the kyma trying to integrate hydra + oathkeeper with our API gateway. As a part of that, we have created a first version of charts for oathkeeper.
If you find helm charts as a nice feature for easier oathkeepr adoption maybe we could contribute to that?

CC @aeneasr

@aeneasr
Copy link
Member

aeneasr commented May 7, 2019

Hey @piotrmsc ! There is an ongoing effort to implement helm charts for the whole ecosystem - we'd love to get your input (and help) on that!

ory/k8s#3

@piotrmsc
Copy link
Author

piotrmsc commented May 8, 2019

@aeneasr nice! once we will have it done in kyma I will plan to collaborate on that then ;-)

@aeneasr
Copy link
Member

aeneasr commented May 8, 2019

Awesome! Also, in case you haven't seen it - we're currently refactoring Oathkeeper and removing the need for a database as well as reducing deployment complexity (right now two pods api+proxy are required, this will go away in the future). More info #177 #185

@aeneasr
Copy link
Member

aeneasr commented May 8, 2019

I think we'll be done next week, maybe the week after�.

@piotrmsc
Copy link
Author

piotrmsc commented May 8, 2019

that's even better! ;) right now we had to expose apiserver and proxy via ingress separate hosts (or try to have it on a single host with "path based routing") but with the mentioned change it will much cleaner 👍

@aeneasr
Copy link
Member

aeneasr commented May 8, 2019

Great to hear that it will improve the way you deploy! We got a lot of feedback like that (including potentially slow queries with many rules when deploying multi-AZ) which is why we're changing the architecture!

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

No branches or pull requests

2 participants