Replies: 1 comment 2 replies
-
That's very interesting indeed! I think this is quite hard to achieve but it's interesting, and you would not have to use any middleware. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Thinking about every implementation I found until now and trying to think in a way to not add any overhead in the apps I look to these implementations:
Lazytainer
sablier
ContainerNursery
expected solution
For me the best solution will be:
This is what every service want to do.
The main problem is how is made, the best solution need to.
All this means:
The container have a public port for frontend that call the API in client-side and the server-side uses the sock to start the container and a the same container have a service to stop the container based on access, but how we know if have access without put a service behind the service? Based on traffic route used to redirect the traffic of a container by another
Step-by-step:
User acess the
whoami.example.com
and open the wait page, the client-side callsleep.example.com/api/wake/whoami.example.com
based on label configured.Service change the service again to original service after the container wake:
The main point is make the provider and implementation that change the reverse proxy without add no overhead. The only complexity is make sure the proxy is changed in the fancy way that not impact other services.
Beta Was this translation helpful? Give feedback.
All reactions