# Kong-Ingress-Controller and CRD

**URL:** <https://discuss.konghq.com/t/kong-ingress-controller-and-crd/6149>\
**Category:** Questions\
**Tags:** kubernetes\
**Created:** [April 28, 2020, 1:07am UTC](https://discuss.konghq.com/t/kong-ingress-controller-and-crd/6149 "2020-04-28T01:07:01Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![traines](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/traines/32/158_2.png) [@traines](https://discuss.konghq.com/u/traines)\
**Post date:** [April 28, 2020, 4:52pm UTC](https://discuss.konghq.com/t/kong-ingress-controller-and-crd/6149/2 "2020-04-28T16:52:13Z")

</div>

By default yes. There are two options to restrict its scope:

The [–watch-namespace argument](https://github.com/Kong/kubernetes-ingress-controller/blob/master/docs/references/cli-arguments.md) (or environment variable) restricts the controller to one namespace and one namespace only.

The [kubernetes.io/ingress.class annotation](https://github.com/Kong/kubernetes-ingress-controller/blob/master/docs/references/annotations.md#kubernetesioingressclass) allows you to indicate which configuration the controller should use. This allows you to use only a subset of ingress configuration across all namespaces. On the controller end, this is chosen using the `--ingress-class` argument/`CONTROLLER_INGRESS_CLASS` environment variable, and defaults to `kong`.

Note that there are some nuances to which resources require the annotation, and that resources with _no_ annotation are always handled: [Dbless: Kong ingress.class != kong doesn't work with KongConsumer type: key-auth](https://discuss.konghq.com/t/dbless-kong-ingress-class-kong-doesnt-work-with-kongconsumer-type-key-auth/6115)

---

_[View the full topic](https://discuss.konghq.com/t/kong-ingress-controller-and-crd/6149)._