Skip to content
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

Closed
wahmedswl opened this issue Oct 13, 2024 · 10 comments
Closed

Deploy Kuma on Universal is broken #1997

wahmedswl opened this issue Oct 13, 2024 · 10 comments
Labels
kind/bug A bug triage/accepted The issue was reviewed and is complete enough to start working on it

Comments

@wahmedswl
Copy link

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

@wahmedswl wahmedswl added kind/bug A bug triage/pending This issue will be looked at on the next triage meeting labels Oct 13, 2024
@jijiechen
Copy link
Member

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 KUMA_APPLICATION_PROBE_PROXY_PORT as 0. This feature is mainly used by Kubernetes users.

@wahmedswl
Copy link
Author

@jijiechen Can this be configured via DP manifest yaml so that this can be put in Version Contol?

@wahmedswl
Copy link
Author

wahmedswl commented Oct 14, 2024

@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

@lukidzi
Copy link
Contributor

lukidzi commented Oct 21, 2024

Triage: we need to rework our quickstart on Universal, but we should add at least some improvement into docs configuring the probe port to avoid conflict

xref: #1960

@lukidzi lukidzi added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels Oct 21, 2024
@lukidzi lukidzi transferred this issue from kumahq/kuma Oct 21, 2024
@jijiechen
Copy link
Member

These port unfortunately can't be configured via dataplane manifest.
Regarding you questions of "configuring multiple services again single Dataplane", I don't get your actual idea. It's recommended to run only a single dataplane on a host.

@wahmedswl
Copy link
Author

@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.

@jijiechen
Copy link
Member

Conceptually a dataplane is a running instance of a service, so the relation service:dataplane has a 1:N mapping. In a typical microservices architecture, services are isolated units serving different business functionalities; and dataplanes are instances of each of these services.
On the other hand, technically, we generate different service objects/resources when a dataplane defines multiple ports in its manifests.

@vovasoft
Copy link

export KUMA_READINESS_PORT=9903
export KUMA_APPLICATION_PROBE_PROXY_PORT=0
kuma-dp run

It's not work

@Automaat
Copy link
Contributor

The quickstart demo now works after rewritting it, and errors from this issues are now solved by: #2005

@jijiechen
Copy link
Member

Hi @vovasoft we'll continue discussing in this issue #2010

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
kind/bug A bug triage/accepted The issue was reviewed and is complete enough to start working on it
Projects
None yet
Development

No branches or pull requests

5 participants