hashicorp / hashicorp/consul

Consul Admin Partitions should cascade the consul service to all admin partitions

Open
#16,189 0 comments 4 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
30.1k
Forks
4.6k
Avg merge
1d 18h
Merged PRs (30d)
39

Description

So when you utilize admin partitions, you get different visibility into the consul services depending on if this is the default admin partition or a non default

**Default admin partition**
* Overview shows the nodes and their leadership status
* Services section shows the consul services and the nodes
* Running an nslookup against that default admin partition gives the correct node ip addresses for the consul services
image

**Non default admin partition**
* Overview shows the nodes and their leadership status
* Services section does not show the consul services or any of the nodes
* Running an nslookup against the non default admin partition gives no results for consul.service.consul
image

### The change/feature ask TLDR
We should update consul so that the consul service is inherited by all admin partitions so people can do lookups against the consul.service.consul entry, etc

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the reported difference between the default and non-default admin partitions, checking the Services view and consul.service.consul lookup in each. Trace the existing admin-partition service registration and inheritance behavior, then verify that the consul service and node addresses are visible and resolvable from every admin partition.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
distributed-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.