Feature Proposal: Support for Certificate Manager

[kubevious]

Scope

We want to make usage of Certificate Manager easier and safer. This proposal is to implement native support of Certificate Manager to prevent and troubleshoot Certificate Manager issues right in Kubevious. That would involve tracking linked resources and guiding user to areas that need. Certificate Manager uses following path main ingress resource -> certificate -> certificaterequest -> order -> challenge -> challenge ingress during the certificate refresh. We want to implement a special view for Cert Manager, or integrated those resources with the Gateway View.

We also want to identify common conditions that lead to certificate refresh issues. What combination of Ingress / Issuer parameters and annotations caused issues with fetching certificates? Such checks can be implemented in Kubevious.

Current Stage

At this stage, we want to gather initial interest from the community to decide whether to move forward with this new capability.
❓- Did you have any issues with Certificate Manager?
❓- What caused those issues?
❓- How often did they happen?

❤️ - Please answer below in the comments, and 👍 thumbs up if the answer is yes to any of the questions above.

Progress

• ✅ Draft idea description
• 👉 Gather initial interest from the community. Thumbs up if you think you would use this feature in production.
• 🔳 Define high-level requirements
• 🔳 Form a working group and elect a DRI
• 🔳 Clarify implementation specifics
• 🔳 Fun part - coding
• 🔳 Released

Appendixes

Kubevious Gateway View

A glimpse of what Kubevious does for K8s Ingresses. We want to do the same (and more) for 3rd party API Gateways.