kubernetes-ingress-controller
kubernetes-ingress-controller copied to clipboard
ngrok
The official ngrok Ingress Controller for Kubernetes
## What Add Issue and Pull Request Templates ## Why Will help us better triage issues by providing community members and ourselves templates for creating issues. We can still fall...
as a part of the notes.txt that runs after the helm installation, we should output some useful information about next steps the user could take to see some useful functionality...
Currently we have some github actions that will release new `latest` docker images on each push to main and it will publish a new release of our helm chart on...
While we have our e2e suite to test overall functionality, we should also setup lower level tests. * Plain go unit tests where they provide value * Kubebuilder tests frameworks...
Resolves #36 Adds helm `unittest` plugin to project with snapshots so we can validate helm generates what we want it to
Fixes #34 Will fail CI if Kubebuilder generated files aren't up to date. I moved the other tests to depend on this one so that if the kubebuilder generated files...
We get lots of events of updates to status and finalizers that we don't need to see twice. We could filter some out with a predicate https://stuartleeks.com/posts/kubebuilder-event-filters-part-1-delete/
Kubebuilder supports auto generating some files like rbac permissions based on annotations in the [code](https://github.com/ngrok/ngrok-ingress-controller/blob/main/internal/controllers/ingress_controller.go#L30-L35). We should have CI run these generation commands and fail CI if there are any...
untangling some local work into separate branches. Stashing off some readme updates and the outline for the tech spec
We should audit and support the common helm values other controllers support.