roi
Right now the discovery service server runs in a single pod. This is not optimal as if new pods are created while the discovery service pod in down, they will...
Interesting metrics could be: * Number of discovered nodeIDs * Number of InSync EnvoyConfigs * Number of RollbackFailed EnvoyConfigs * Number of Rollback EnvoyConfigs
Check snapshot consistency using "snap.Consistent()" function provided by the cache implementation of go-control-plane. Consider also validating consistency between clusters and listeners, as this is not done by snap.Consistent() because listeners...
A solution is needed to manage the renewal of the DiscoveryService related certificates: * The CA * The server certificate * The client certificates Currently all these certificates are just...
Similarly to #45 we need to add readiness/liveness to the discovery service Deployment. In this case is not sufficient with the endpoints provided by controller-runtime as we also need to...
VirtualHost service discovery is available in envoy and go-control-plane already has support for it. Add, if possible, support for it in Marin3r. /kind feature /priority important-longterm /assign
Switch back to a RollingUpdateDeploymentStrategy in the discovery service for future releases. Some interesting ideas in this [thread](https://github.com/3scale-ops/marin3r/pull/190#discussion_r1205350420). cc @slopezz related to #190
Add a check in the validating admission webhook for EnvoyConfig resources to avoid a new EnvoyConfig to be created for a node-id that is already being managed by an existent...
**Describe the bug** The authorino process panics when the `user` field in a k8s SAR authorization rule is not defined. **Help us Reproduce it** 1. Create the following Kuadrant AuthPolicy...