-
Notifications
You must be signed in to change notification settings - Fork 5
Description
Is your feature request related to a problem? Please describe.
Containers deployed on Akash have no way to know their own external hostnames and port mappings. This makes it impossible for applications to self-register or configure themselves properly without manual intervention. For example, when running database clusters, or monitoring, each node needs to know its own external endpoint to register with the cluster's configuration system.
Describe the solution you'd like
Add environment variables to all containers that provide:
The container's ingress hostname: AKASH_INGRESS_HOSTNAME
Any custom hostnames: AKASH_INGRESS_CUSTOM_HOSTNAME_{PORT}{INDEX}
External port mappings: AKASH_EXTERNAL_PORT{PORT}
This would allow containers to programmatically access their own network information and use it for self-configuration, registration with service discovery, or sharing connection details with other systems.
Describe alternatives you've considered
no good alternatives
Search
- I did search for other open and closed issues before opening this
Code of Conduct
- I agree to follow this project's Code of Conduct
Additional context
See draft PR akash-network/provider#259