Skip to content

Add initial Gloo Edge provider: VirtualService → HTTPRoute (basic translation) #102

@shivansh-source

Description

@shivansh-source

Problem
Ingress2gateway currently supports multiple providers but does not support migration from Gloo Edge resources.

Proposal
Introduce a new provider for Gloo Edge that:

Reads VirtualService resources
Converts basic routing configuration into the provider IR
Leverages existing emitters to generate Gateway API resources

to add :
Support:
domains → hostnames
prefix-based path matching
single upstream routing

future work:

advanced matchers
routing
plugins and filters

Goal
Establish the base provider structure and validate end-to-end translation from Gloo edge -> IR -> Gateway api.
I plan to start with a minimal implementation and then slowly add other features

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions