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

Who is using APISIX ingress controller?(欢迎使用 APISIX ingress controller 的个人和公司在此留言) #501

Open
gxthrj opened this issue May 26, 2021 · 8 comments · Fixed by #1334
Labels

Comments

@gxthrj
Copy link
Contributor

gxthrj commented May 26, 2021

Who is using APISIX ingress controller?

Sincerely thank everyone who constantly keeps on using and supporting APISIX ingress controller. We will try our best to make APISIX ingress controller better and make the community and ecology more prosperous.

The original intention of this issue

  • We’d like to listen to the community to make APISIX ingress controller better.
  • We want to attract more partners to contribute to APISIX ingress controller.
  • Learn more about the practical use scenarios of APISIX ingress controller to facilitate the next step of planning.

What we expect from you

Please submit a comment in this issue to include the following information:

your company, school or organization.
your city and country.
your contact info: blog, email, twitter (at least one).
for what business scenario do you use APISIX ingress controller.

You can refer to the following sample answer:

* Organization: api7.ai
* Location: ShenZhen, China
* Contact: kvn@apache.org
* Purpose: As a API gateway control plane in Kubernetes to configure APISIX.

Thanks again for your participation! Your support is the motivation for us to move forward.
Apache APISIX community

谁在使用 APISIX ingress controller

感谢正在使用和关注 APISIX ingress controller 的开发者,我们会持续投入,让 APISIX ingress controller 项目和社区更加繁荣。

这个 issue 的出发点

  • 聆听社区的声音,让 APISIX ingress controller 解决实际的问题
  • 吸引更多的开发者参与和贡献
  • 更多的了解 APISIX ingress controller 的实际使用场景,以便后续版本的计划

我们期待您能提供

在此提交一条评论, 评论内容包括:

您所在公司、学校或组织
您所在的城市、国家
您的联系方式: 微博、邮箱、微信 (至少一个)
您将 APISIX ingress controller 用于哪些业务场景

可以参考下面的示例:

组织:api7.ai
地点:中国深圳
联系方式: kvn@apache.org
使用场景:在 Kubernetes 集群中作为 API 网关控制平面来配置 APISIX 。

多谢您的支持!
Apache APISIX 社区

@gxthrj gxthrj pinned this issue May 26, 2021
@Donghui0
Copy link
Contributor

组织: igetcool.com (少年得到)
地点: 中国北京
联系方式: oliverDong1991
使用场景: 处理 南北 + 部分东西流量. 原使用 traefik, 正在全量替换中...

@gxthrj
Copy link
Contributor Author

gxthrj commented May 31, 2021

@Donghui0 Thanks for your report.

@hansongll
Copy link

组织:Guanwei(观为智慧)
地点:中国南京
联系方式: 254845@qq.com
使用场景:在 Kubernetes 集群中作为 API 网关,目前使用 traefik,正在考虑APISIX 。

@chzhuo
Copy link
Contributor

chzhuo commented Sep 14, 2021

组织:upyun(又拍云)
地点:中国杭州
联系方式: chzhuo
使用场景:作为k8s容器网关,替换ingress-nginx,少部分业务使用中,稳定后彻底切换

@yin6516008
Copy link

Organization: NIIMBOT
Location: WuHan,China
Contact: yinming@niimbot.com
Purpose: Kubernetes gateway cluster entry, currently use AliCloud cloud native gateway, could not be a custom function, considering some migrated to apisix-ingress

组织:武汉精臣智慧标识科技有限公司
地点:中国·武汉
方式:yinming@niimbot.com
使用场景:�Kubernetes集群网关入口,目前使用阿里云云原生网关,因无法自定义功能,考虑部分迁移至apisix-ingress

@tao12345666333
Copy link
Member

xref: apache/apisix#487

@LinkMaq
Copy link
Contributor

LinkMaq commented Sep 14, 2022

Organization: KubeGems
Location: ChengDu,China
Contact: support@kubegems.io
Purpose: Use apisix as one of the types for gateway chosen by the tenant.

组织:KubeGems
地点:中国·成都
方式:support@kubegems.io
使用场景:使用 apisix 作为租户自定义网关类型的选项(开发中...)

@tao12345666333 tao12345666333 linked a pull request Sep 15, 2022 that will close this issue
9 tasks
@Yousri
Copy link
Contributor

Yousri commented Sep 20, 2022

组织:xmfunny ( 真有趣公司 )
地点:中国厦门
联系方式: Yousri (qingxianyan at gmail dot com)
使用场景:用于内网 kubernetes 集群 API 网关,少部分业务(主要SDK)结合 APISIX 使用中,目前其他大部分还是Traefik,待研究学习中;外网线上ACK部署用于代替阿里云 API 网关产品的功能;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants