-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Can there be a k8s-specific mode #9714
Comments
能不能通过apisix的ingress controller输出为yaml,然后apisix通过刷新yaml的模式,达到全量crd的模式 |
are u interested in this #4388 |
This issue has been marked as stale due to 350 days of inactivity. It will be closed in 2 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the dev@apisix.apache.org list. Thank you for your contributions. |
This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time. |
Description
apisix目前支持全量yaml模式,但是又一个痛点就是devops需要有k8s得权限去操作configmap,我们是cicd分开,devops做ci部分,cd又argocd做,而且实际运行过程中etcd总出问题,一会死一个节点,难以维护
能不能有一种支持以K8S的crd为配置中心的模式,这样不用将所有的东西放在yaml中难以维护,还要授权,也不用在去维护单独的etcd集群
The text was updated successfully, but these errors were encountered: