Getting started with HTTPProxy basics, Contour's alternative API for Ingress
From official doc, the goal of the HTTPProxy Custom Resource Definition (CRD) is to expand upon the functionality of the Ingress API to allow for a richer user experience as well addressing the limitations of the latter’s use in multi tenant environments. Key HTTPProxy Benefits Safely supports multi-team Kubernetes clusters, with the ability to limit which Namespaces may configure virtual hosts and TLS credentials. Enables including of routing configuration for a path or domain from another HTTPProxy, possibly in another Namespace. Accepts multiple services within a single route and load balances traffic across them. Natively allows defining service weighting and load balancing strategy without annotations. Validation of HTTPProxy objects at creation time and status reporting for post-creation validity. So, without these complicated definitions of HTTPProxy, let’s just write some manifests and test it out for ourselves! ...