# ClusterRole and ClusterRoleBinding creation

**URL:** <https://discuss.konghq.com/t/clusterrole-and-clusterrolebinding-creation/6435>\
**Category:** Questions\
**Tags:** kubernetes\
**Created:** [June 5, 2020, 3:51pm UTC](https://discuss.konghq.com/t/clusterrole-and-clusterrolebinding-creation/6435 "2020-06-05T15:51:20Z")\
**Posts on this page:** 1\
**Showing post:** 13

<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:** [June 12, 2020, 10:03pm UTC](https://discuss.konghq.com/t/clusterrole-and-clusterrolebinding-creation/6435/13 "2020-06-12T22:03:27Z")

</div>

Not officially yet. Do you have a local registry you can push images to?

Although we don’t have a pre-built image, you should be able to check out [the controller code locally](https://github.com/Kong/kubernetes-ingress-controller), apply the change suggested in [andrevtg’s comment](https://github.com/Kong/kubernetes-ingress-controller/issues/717#issuecomment-639917754), and then build/push it like so:

```auto
export REGISTRY=gcr.io/grozny-ivan-1581; export TAG=0.9.0-dev; make container; docker push gcr.io/grozny-ivan-1581/kong-ingress-controller:0.9.0-dev

```

Sub in your registry for the `gcr.io` example there and update your deployment to use the custom image.

That change ignores `KongClusterPlugin` entirely, which will work for your use case, and should suffice for testing, but it’s not what we’ll actually do in the end. We need to support both environments with cluster-wide access and those without, so we’d need to add some sort of toggle between those modes.

---

_[View the full topic](https://discuss.konghq.com/t/clusterrole-and-clusterrolebinding-creation/6435)._