Gloo edge pod is going into crashloopback

[podilavenky]

Gloo Edge Version

1.11.x (latest stable)

Kubernetes Version

1.21.x

Describe the bug

I deployed gloo edge with variable kantive enabled true and knative version is 1.3.2. but gloo pod is in crashloopback state. Below is the error in gloo pod log, It's looks like rback permission issue. Error in setup: creating base Virtual service resource client: list check failed: virtualservices.gateway.ssolo.io is forbidden: User "system:services count:gloo-system:gloo" cannot list resource "virtualservices" in API group "gateway.solo.io" at the cluster scope

Not: I installed knative manually and all deployments are in AWS fargate and Eks.

Steps to reproduce the bug

I followed documentation and installed using helm clmmand

Expected Behavior

Pod has to run

Additional Context

No response

[podilavenky]

I just resolved the issue by adding rback clusterrole to API group gateway.solo.io. But this is not coming with default helm install

[jenshu]

we should fix the clusterrole to have the correct apiGroups