Yes, that looks valid to me.
I’d also recommend to add --set postgresql.enabled=false and --set env.database="off", which deploys the controller without a database and doesn’t even require the two sub-charts.
So we have kong installed as an ingress controller now, but I’m having issues deploying an application ingress. The application install gets this error in the Rancher UI for the APP:
Failed to install app ci-settings-auth-proxy. Error: release ci-settings-auth-proxy failed: kongingresses.configuration.konghq.com is forbidden: User "u-o2uifphcfl" cannot create kongingresses.configuration.konghq.com in the namespace "app-services"
Is this really about my user permissions? We don’t think so, since I am an owner of the namespace “app-services”.
Just curious, how did you resolve this? I don’t have any experience with Rancher but sharing the fix here will help folks who run into the same problem in future.
That’s what it looks like.
This again could be something Rancher specific (I’m not sure).
Could you check in with Rancher folks how they handle CRDs (Custom Resource Definitions)?