yep, it's right! Add the `ApisixPluginConfig.yaml` to here[1] and include it to `kustomization.yaml`[2]
[1]: https://github.com/apache/apisix-ingress-controller/tree/master/samples/deploy/crd/v1beta1 [2]: https://github.com/apache/apisix-ingress-controller/blob/master/samples/deploy/crd/v1beta1/kustomization.yaml 一世纸醉金迷 <[email protected]> 于2021年9月23日周四 上午11:04写道： > Hi, i'm joining. > I had subscribed the dev mail list successful right now. > So if i split this function into multiple tasks, my first aim is to `Add > ApisixPluginConfig custom resource. Only need to modify YAML.`, > is it correct > > On 2021/09/22 08:36:09, Jintao Zhang <[email protected]> wrote: > > # background > > > > Many functions of Apache APISIX are now provided through plugins. In > > scenarios where APISIX is used extensively, *these configurations are > often > > reusable.* > > > > In February of this year, plugin config capabilities has been added to > > Apache APISIX. [1] > > > > I propose to add a custom resource of `ApisixPluginConfig` to Apache > APISIX > > Ingress to support this feature.[2] > > > > # implement > > > > * Add an `ApisixPluginConfig` custom resources. It can be converted to > > APISIX's `plugin_config`, Use its name as its id; > > * When we add this configuration to `ApisixRoute`, use its name as an > index. > > > > > > > > [1]: https://github.com/apache/apisix/pull/3567 > > [2]: > https://apisix.apache.org/docs/apisix/architecture-design/plugin-config > >
