Update CRD for IngressOperator

[alexellis]

Signed-off-by: Alex Ellis (OpenFaaS Ltd) alexellis2@gmail.com

Description

Update CRD for IngressOperator

Motivation and Context

Fixes: #718

The CRD doesn't appear to have been synced after merging openfaas/ingress-operator#40

Testing

helm upgrade openfaas --install chart/openfaas \
    --namespace openfaas  \
    --set basic_auth=true \
    --set functionNamespace=openfaas-fn \
    --set ingressOperator=true

The CRD applied and worked followed by:

kubectl -n openfaas logs deployment/ingress-operator
I1129 15:32:24.947893       1 main.go:52] Starting FunctionIngress controller version: 0.6.6 commit: 01e49ccaa4eafe1bb019803cc485decaca3badbc
W1129 15:32:24.948382       1 client_config.go:543] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I1129 15:32:24.950844       1 controller.go:122] Setting up event handlers
I1129 15:32:24.950954       1 controller.go:183] Waiting for informer caches to sync
I1129 15:32:25.051267       1 controller.go:188] Starting workers
I1129 15:32:25.051326       1 controller.go:194] Started workers

I then applied a FunctionIngress record and got:

NAMESPACE   NAME       CLASS    HOSTS                  ADDRESS      PORTS   AGE
openfaas    nodeinfo   <none>   nodeinfo.myfaas.club   172.18.0.2   80      15s

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)