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

Caddy plugin support #52

Closed
silverbackdan opened this issue Oct 27, 2020 · 5 comments
Closed

Caddy plugin support #52

silverbackdan opened this issue Oct 27, 2020 · 5 comments

Comments

@silverbackdan
Copy link

I'm sorry for the newbie issue here. I'm hoping to include Caddy ingress with a plugin for Vulcain which has been created. See: https://github.com/dunglas/vulcain/blob/master/docs/caddy.md

I'm sure there are many plugins for Caddy which is one of the great things about it - is there an easy way to use this ingress with additional plugins? If so, it'd be great to see some info in the documentation about it and I'd be using this right away. If not, is it a feature worth considering having the ability to add in or have docs about how one may do this (perhaps creating a new Docker image and basing it on the image here with a small example as a starting point?)

Thanks in advance.

@Embraser01
Copy link
Member

Hi 👋
For now, there isn't a easy way to add plugins in the controller. I don't think it will be added in the foreseeable future.

For you use case: I don't know Vulcain but I think it should be put behind the Caddy Ingress Controller as a Kubernetes Deployment & Service instead of integrating it in the Caddy Ingress process

@dunglas
Copy link

dunglas commented Dec 5, 2020

Regarding Vulcain, it must be at the edge because it triggers HTTP/2 Server Pushes. The Ingress looks like the right place for this module if you use Server Push. If you use preload hints, a standard deployment is ok.

@silverbackdan
Copy link
Author

silverbackdan commented Dec 6, 2020

Thank you both for your replies!

Am I right in thinking I can create a vulcain service and still get some speed benefits using preload headers then? Also did I read correctly that Chrome was deprecating push support as well? The ability to receive resolved requests simultaneously was going to be a big improvement for an application of mine, but if the browser won't support it, not much we can do. If I'm wrong regarding push support deprecation then figuring out how to get vulcain on the edge would be great, but I will get in touch you and LT about that when the time is right in my project.

@dunglas
Copy link

dunglas commented Dec 6, 2020

@silverbackdan yes and yes, see https://twitter.com/dunglas/status/1326552735404060672?s=21.

We're going to make some announcements about Vulcain soon, basically we'll recommend to use preload hints when targeting Chrome.

@silverbackdan
Copy link
Author

Thank you. In which case I had some helm templates which was implementing Vulcain as a service which I'll re-introduce. Fingers crossed for the early hints support. Closing the issue here as it's getting off topic for this repo.

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

3 participants