spinframework / spinframework/spin-operator
Local Service Chaining and Intra-App routing not working with selective deployment
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 289
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
Trying to deploy a Spin application with two components, using local service chaining, the component calling another component fails with the following message:
Error with selective deployment: Component selected with '--component frontend' cannot use service chaining to unselected component: allowed_outbound_hosts = ["http://backend.spin.internal"]
Using the Intra-app method "http://self" also does not work, it returns 404 trying to route to another component.
It would be nice to see service chaining working across components with selective deployment.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the two-component deployment with selective component selection, then compare the local service chaining failure with the 404 from the intra-app "http://self" route. Done means a selected component can reach the other component through the documented service-chaining or intra-app routing behavior, without the reported error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100