Expose more information about the cluster via the HTTP API and UI
- Dominant language
- Go
- Stars
- 30.1k
- Forks
- 4.6k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 39
Description
There are some configuration options in Consul that would be useful for operators but are not exposed once the agent is running.
Some of these include:
- Primary datacenter
- Whether ACLs are enabled on all agents
- Whether Connect is enabled on all servers
- Whether RPCs are encrypted with TLS
Since the information for most these is distributed around the cluster, we would need to decide what's a good way to display the information.
For example, if ACLs are enabled in all but a few agents, we should likely provide a way to find out what agents do not have them enabled.
Contributor guide
Research direction
Start by tracing the existing HTTP API and UI entry points for cluster and agent configuration. Determine how primary datacenter, ACLs, Connect, and RPC TLS status are distributed across the cluster, then define a consistent way to expose partial or differing values and how operators can identify exceptions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, distributed-systems, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100