-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Deploy Kuma on Universal is broken #1997
Comments
Thanks for reporting. We didn't provide a CLI argument to configure this port but you can configure it using an environment variable when you need to run multiple kuma DPs on the same host, here is an example: export KUMA_READINESS_PORT=9903
export KUMA_APPLICATION_PROBE_PROXY_PORT=0
kuma-dp run In addition, there is another port which may conflict among multiple DPs and you may disable it on Universal DPs by exporting environment variable |
@jijiechen Can this be configured via DP manifest yaml so that this can be put in Version Contol? |
@jijiechen Also, what is the way to configure multiple services again single Dataplane? In univeral mode, single kuma-dp should be run on machine, isn't it? Thanks |
xref: #1960 |
These port unfortunately can't be configured via dataplane manifest. |
@jijiechen Yes, that's why asked how to run multiple services on same dataplane? E.g. they create separate dataplane for every service; just look at the example in quick start, Redis and Example app have separate dataplane. |
Conceptually a dataplane is a running instance of a service, so the relation |
export KUMA_READINESS_PORT=9903 It's not work |
The quickstart demo now works after rewritting it, and errors from this issues are now solved by: #2005 |
What happened?
Hi!
Quick Start example for Deploy Kuma on Universal is broken. Able to bring-up Redis service via kuma-dp but not the 2nd app because it wanna run admin on 9902 but it's already taken by redis service
"dataplane.readinessReporter.port": "9902",
. How to configure the"dataplane.readinessReporter.port"
explicitly via dataplane cli.Thanks
The text was updated successfully, but these errors were encountered: