Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: Add Q&A section for ingress controller #1895

Closed
Revolyssup opened this issue Jul 19, 2023 · 3 comments
Closed

docs: Add Q&A section for ingress controller #1895

Revolyssup opened this issue Jul 19, 2023 · 3 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@Revolyssup
Copy link
Contributor

Current State

All the tutorials install Apisix with service type NodePort and access APISIX either by nodeport or by curl'ing into the Pod. Users might have questions like how can APISIX be exposed as service type LoadBalancer? and how can the Ingress resource be allocated Address?

Desired State

Answer these questions in the Q&A section on installing APISIX with ingress.

@lingsamuel lingsamuel moved this to 📋 Backlog in Apache APISIX backlog Jul 20, 2023
@tao12345666333 tao12345666333 added the documentation Improvements or additions to documentation label Jul 24, 2023
@Revolyssup
Copy link
Contributor Author

@tao12345666333 Can I add these qa to existing FAQ here ? https://apisix.apache.org/docs/ingress-controller/FAQ/

@tao12345666333
Copy link
Member

Sure!

@moonming moonming moved this from 📋 Backlog to 🏗 In progress in Apache APISIX backlog Jul 27, 2023
@AlinsRan AlinsRan moved this from 🏗 In progress to 👀 In review in Apache APISIX backlog Jul 28, 2023
@Revolyssup
Copy link
Contributor Author

Completed #1907

@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in Apache APISIX backlog Aug 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
Archived in project
Development

No branches or pull requests

2 participants