Skip to content

Gateway not auto-assigned to Default Gateway Group on registration — expositions never delivered to proxy #19

@s009desh

Description

@s009desh

When a proxy pod starts and registers with the control plane using a default gateway token, it is never automatically assigned to the Default Gateway Group. As a result, any exposition created on gateway group 1 has no active gateways, and the MCP endpoint returns Service not found indefinitely.

Steps to reproduce:

  • Deploy reshapr-control-plane and reshapr-proxy via Helm (fresh install)
  • Configure proxy with a valid default gateway token (reshapr-{token})
  • Import an OpenAPI spec via reshapr import
  • Call the MCP endpoint

Expected behavior:
When a proxy registers using a default gateway token, it should be automatically assigned to the Default Gateway Group so expositions are delivered to it.

Actual behavior:

Proxy registers successfully and subscribes to the exposition changes stream
Fetched 0 expositions during registration — gateway is in no group

Exposition is created on gateway group 1 but control plane finds no active gateways:

⚠️ No active exposition found for the Exposition XXX. Maybe there's no running Gateway at the moment?

MCP endpoint returns Service not found

Logs (control plane):

Registering gateway with name: 'fp-dev-reshapr-proxy-5c58f5d6b6-54sjc'
Gateway with ID fp-dev-reshapr-proxy-5c58f5d6b6-54sjc not found, creating a new one
...
Creating a new exposition for config plan '...' on gateway group '1'
Publishing exposition creation for exposition '...'

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions