vCluster - Create fully functional virtual Kubernetes clusters - Each vcluster runs inside a namespace of the underlying k8s cluster. It's cheaper than creating separate full-blown clusters and it offers better multi-tenancy and isolation than regular namespaces.
The Gateway API is in v1 and is supposed to be able to completely replace the usage of Ingress and give more possibilities, power, expressiveness and security to users.
Ingress is frozen. New features are being added to the Gateway API. - source
Gateway API is the successor to the Ingress API. However, it does not include the Ingress kind. As a result, a one-time conversion from your existing Ingress resources to Gateway API resources is necessary.
Refer to the ingress migration guide for details on migrating Ingress resources to Gateway API resources. - source
Is your feature request related to a problem?
The Gateway API is in v1 and is supposed to be able to completely replace the usage of Ingress and give more possibilities, power, expressiveness and security to users.
Ingress:
Gateway API:
HTTP flow
Users (Personas)
Which solution do you suggest?
Have for vcluster...
Which alternative solutions exist?
NA
Additional context