A Juju charm deploying and managing external access to HTTP/HTTPS services in a Kubernetes cluster via a Gateway and an HTTPRoute resource. This requires the Kubernetes cluster in question to have a Gateway API controller already deployed into it.
Project and community
Gateway API is an open-source project that welcomes community contributions, suggestions, fixes and constructive feedback.
- Read our Code of Conduct
- Join the Discourse forum
- Discuss on the Matrix chat service
- Contribute and report bugs to the Gateway API integrator operator
- Check the release notes
Contributing to this documentation
Documentation is an important part of this project, and we take the same open-source approach to the documentation as the code. As such, we welcome community contributions, suggestions and constructive feedback on our documentation. Our documentation is hosted on the Charmhub forum to enable easy collaboration. Please use the “Help us improve this documentation” links on each documentation page to either directly change something you see that’s wrong, or ask a question, or make a suggestion about a potential change via the comments section.
If there’s a particular area of documentation that you’d like to see that’s missing, please file a bug.
In this documentation
| Tutorial Hands-on introductions to Gateway API integrator |
|
| Explanation Concepts - discussion and clarification of key topics |
Reference Technical information - specifications, commands, architecture |
Navigation
| Level | Path | Navlink |
|---|---|---|
| 1 | explanation | Explanation |
| 2 | explanation-workflow | The charm’s workflow |
| 1 | reference | Reference |
| 2 | reference-actions | Actions |
| 1 | tutorial | Tutorial |
| 2 | tutorial-getting-started | Tutorial: Deploy the Gateway API integrator charm |