[ 
https://issues.apache.org/jira/browse/COMDEV-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ming Wen closed COMDEV-388.
---------------------------
    Resolution: Invalid

> Apache APISIX: support apply certificates from Let’s Encrypt or any other 
> ACMEv2 service
> ----------------------------------------------------------------------------------------
>
>                 Key: COMDEV-388
>                 URL: https://issues.apache.org/jira/browse/COMDEV-388
>             Project: Community Development
>          Issue Type: Improvement
>          Components: GSoC/Mentoring ideas
>            Reporter: Ming Wen
>            Priority: Major
>
> *Apache APISIX*
> Apache APISIX is a dynamic, real-time, high-performance API gateway, based on 
> the Nginx library and etcd.
> APISIX provides rich traffic management features such as load balancing, 
> dynamic upstream, canary release, circuit breaking, authentication, 
> observability, and more.
> You can use Apache APISIX to handle traditional north-south traffic, as well 
> as east-west traffic between services. It can also be used as a k8s ingress 
> controller.
> h3. Background
> The data plane of Apache APISIX supports dynamic loading of ssl certificates, 
> but the control plane does not have the support of ACME.
> Although users can use other tools to obtain ACME certificates, and then call 
> the admin API to write them into Apache APISIX, this is not convenient for 
> many users.
> *Task*
> In the Apache APISIX dashboard (https://github.com/apache/apisix-dashboard) 
> project, add support for ACME, which can automatically obtain and update 
> certificates
> *Relevant Skills*
> TypeScript
> Golang
> familiar with Apache APISIX's admin API
> *Mentor*
> Ming Wen, PMC of Apache APISIX, wenm...@apache.org



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Reply via email to