Add Kubernetes discovery support in Network Connector
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- java, kubernetes
- Domain
- backend, distributed-systems, infrastructure
Research direction
Start by examining the Network Connector’s existing discovery agents and the Karaf Cellar integration referenced in the issue. Define how a Kubernetes discovery agent should discover brokers, then identify suitable implementation and test entry points; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Description
Currently, the Network Connector supports several discovery agents (multicast, ...).
To integrate smoothly in a Kubernetes environment, we could provide a Kubernetes discovery agent able to discover brokers on the kube (exactly as we did on Karaf Cellar).
NB: we could also consider other discovery agents (hazelcast, ignite, ...), we can create specific issue for that.
- Dominant language
- Java
- Stars
- 2.5k
- Forks
- 1.5k
- Avg merge
- 14h 42m
- Merged PRs (30d)
- 85
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from apache/activemq
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
apache/activemq#2558 · 2 comments ·
Maintainers usually reply within 1 day
-
Stale
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
apache/activemq#1999 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 74/100
apache/activemq#1871 · 2 comments ·
Maintainers usually reply within 1 day
-
Topic expiry task loads the whole JDBC topic store into the heap on PostgreSQL (AMQ-6067 fix is ineffective with pgjdbc)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
apache/activemq#2630 · 3 comments ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
objectionary/hone-maven-plugin#1295 ·
Maintainers usually reply within 1 day
-
Clarify Javadoc for Logger methods taking Object... arguments with regards to Throwable detectionOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
[Bug] The shared instance selector's placeholder and no-match text ignore the display languagePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
apache/rocketmq-dashboard#5561 ·
Maintainers usually reply within 3 days