澄潭

Admin API 有的，不过这块后面还会做调整，现阶段对接集成要考虑未来的兼容性问题，所以目前还未正式公开，加入钉钉开发群可以看到群文档。 权重路由是控制台后续会做的，目前 ingress 注解是支持的可以参考：https://github.com/alibaba/higress/blob/main/samples/nacos-discovery/multi-destination.yaml 健康检查可以基于 istio envoyfilter 来实现，可以参考下这个[issue comment](https://github.com/istio/istio/issues/10537#issuecomment-555548652)，对应 higress 上的可以 work 的配置： 注意需要先开启 istio api的支持：https://higress.io/zh-cn/docs/ops/deploy-by-helm#%E6%94%AF%E6%8C%81-istio-crd%E5%8F%AF%E9%80%89 ```yaml apiVersion: networking.istio.io/v1alpha3 kind: EnvoyFilter metadata: name: health-check namespace: higress-system spec: configPatches:...

@SandyLing 目前还没有这个功能，可以到这里提个issue：https://github.com/higress-group/higress-console/issues

@Ink-33 Is this draft PR ready for review, or is there still unfinished work?

@Ink-33 Please add an e2e test for it.

@Ink-33 Please add e2e test cases, refer to: https://github.com/alibaba/higress/pull/759/files#diff-00090f4cf6417f2566ebc91e56b6b5d0e12a834a184f4b814d51bc89581d796b

> > @Ink-33 Please add e2e test cases, refer to: https://github.com/alibaba/higress/pull/759/files#diff-00090f4cf6417f2566ebc91e56b6b5d0e12a834a184f4b814d51bc89581d796b > > got it. I would like to add three parts of test cases including normal, rejected, and normal...

> @johnlanni allow 里面配置多个 consumer 且全部验证失败应该返回哪个错误码给请求，或者直接用 verify failed 兜底呢？ > >  返回 403 即可，错误原因可以用 not allowed，跟jwt本身凭证不合法区分下

@Ink-33 Is there any progress?

@OnlyPiglet Yes, I will support it soon.

> 你好，请问采用annotation方式来配置ingress后是否需要额外手动安装auth wasm 插件？ 不需要，这个basic auth功能已经内置了