Add field to enable openfaas operator

[viveksyngh]

This commit adds field enable_openfaas_operator to deploy OpenFaaS with operator

Signed-off-by: Vivek Singh vivekkmr45@yahoo.in

Description

How Has This Been Tested?

I have tested this on my local k3s cluster with this repo with crd deployed https://github.com/viveksyngh/openfaas-functions/runs/1562603783

k get crd
NAME                        CREATED AT
addons.k3s.cattle.io        2020-12-16T08:28:16Z
helmcharts.helm.cattle.io   2020-12-16T08:28:16Z
functions.openfaas.com      2020-12-16T08:29:28Z
profiles.openfaas.com       2020-12-16T08:29:28Z
sealedsecrets.bitnami.com   2020-12-16T08:30:10Z
tunnels.inlets.inlets.dev   2020-12-16T08:31:48Z

Checklist:

I have:

• [ ] checked my changes follow the style of the existing code / OpenFaaS repos
• [x] updated the documentation and/or roadmap in README.md
• [x] read the CONTRIBUTION guide
• [ ] signed-off my commits with git commit -s
• [ ] added unit tests

[alexellis]

I think we should have added enable_ingress_operator as ingress_operator: true/false.. so I think that might be why you named this filed accordingly.

Could you put openfaas_operator: true/false instead? defaulting to false.

[alexellis]

Let's change the ingress option at the same time?

[viveksyngh]

setting these values to true/false wouldn't cause issue while users try to deploy without editing it ?

[alexellis]

They are already true/false values. The operator is new, so not a concern and AFAIK nobody is using the Ingress Operator with OFC, in which case keeping its default of false will have no mal effects.

[alexellis]

Just to clarify, I'm just asking for you to rename the variables to remove the enable_ suffix.

[viveksyngh]

Updated