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

Add cloud provider specific configuration #1847

Open
lahabana opened this issue Jul 18, 2024 · 1 comment
Open

Add cloud provider specific configuration #1847

lahabana opened this issue Jul 18, 2024 · 1 comment
Labels
triage/accepted The issue was reviewed and is complete enough to start working on it
Milestone

Comments

@lahabana
Copy link
Contributor

Description

Diana suggested this:

I think it could go into the Kuma in Production section since it seems like it would only relate to production instances?

For a title, maybe something like "Cloud Provider Configuration Best Practices"?

For page formatting, a page that we have that's similar is https://docs.konghq.com/gateway/latest/production/performance/benchmark/. Different topic, but it still goes over best practices. I'd think a page with the following sections could be a good starting point:

intro paragraph here

Prerequisites

if applicable

How to configure your cloud provider for Kong Mesh

I'd probably keep this section to be just a list of common cloud providers with a link to their docs about how to configure (rather than us writing their docs for them, those are harder to maintain)

Cloud provider configuration best practices

AWS

content specific to AWS, not sure how long this section would be, but consider grouping h4 headings here if there's similar topics like "Policy configuration" or "Zone control plane configuration"

another cloud provider here

more specific best practices for that provider
If the page gets really long, consider breaking the cloud providers (like AWS) into their own page with maybe a main page that they're nested under that contains general recommendations that applies to all cloud providers

@lahabana lahabana added this to the 2.9.x milestone Jul 18, 2024
@github-actions github-actions bot added the triage/pending This issue will be looked at on the next triage meeting label Jul 18, 2024
@michaelbeaumont
Copy link
Contributor

@lahabana should this be on website?

@michaelbeaumont michaelbeaumont 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 Jul 22, 2024
@michaelbeaumont michaelbeaumont transferred this issue from kumahq/.github Jul 22, 2024
@lahabana lahabana modified the milestones: 2.9.x, 2.10.x Sep 23, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
triage/accepted The issue was reviewed and is complete enough to start working on it
Projects
None yet
Development

No branches or pull requests

2 participants