Doc Feedback: Clustering Gateways and Key Managers with key caching
Open
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Location : https://apim.docs.wso2.com/en/latest/deploy-and-publish/deploy-on-gateway/api-gateway/scaling-the-gateway/
This needs updating with reference to the new gateway / control plane deployment patterns for 4.x which does not mention deploying the key manager separately.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start at the scaling-the-gateway page linked in the issue and review its clustering guidance against the 4.x gateway and control plane deployment patterns. Update the documentation so it addresses key manager deployment and caching; done means the page accurately reflects whether the key manager is deployed separately.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100