CRDs are installed despite of createCRDs: false

[vkryzh]

I believe, issue is introduced here - cce949e

Expected Behaviour

createCRDs: false - no CRDs should be installed

Current Behaviour

createCRDs: false - 3 CRDs are installed (policies, roles, jwtissuers)

Who is this for?

Corva

List All Possible Solutions and Workarounds

• add flag to new CRDs to skip their installation

Steps to Reproduce (for bugs)

1. Install latest Openfaas with only createCRDs: false in values override
2. Have CRDs installed

Context

With Namespace admin permissions we cannot install CRDs, so their installation should be moved to a different place. And, as it stated in chart documentation, we should be able to do this using simple flag.

[alexellis]

Hi @vkryzh

In order to help you out here quickly, we will need to know what commands you're running (including the skip CRD option)

These items are included in the issue templates in most places, if you don't see them in a repo, go ahead and add in the extra context.

We're missing:

• Steps to Reproduce (for bugs)
• Context (i.e. why is this needed for you?)

Alex

[vkryzh]

Hey @alexellis . Added context, thank you.

[alexellis]

Hi @vkryzh

Those IAM-based CRDs can be suppressed via --skip-crds being passed into Helm

I'm having a look at the docs for "namespaced installation" at the moment so will get this closed.

The full commands you're using would always be appreciated. It will help us avoid this back and forth and guesswork, which ultimately help us to help you.

Hope this helps.

Alex

[alexellis]

Related to this issue, we've consolidated the way CRDs will be created, feel free to comment:

#1212