Func cli command to generate deployment artifacts about keda HOT 4 CLOSED

if we fail when Kore isn't installed, we're essentially saying you can't deploy Azure Functions to Kubernetes via the cli without Kore.. we need to give people the choice of whether or not they want extra components to go along with Azure Functions.

I expect many people who are just getting started with Azure Functions for testing/dev/evaluation purposes wouldn't need Kore from the get go.

Regarding the helmless installation - I agree, I don't like it either. Helm 3 should come out without tiller, meaning only a client side Helm component.
We can always take the route of simply putting everything in a single .yaml file and calling kubectl apply on it.

from keda.

I think the func deploy command should focus on creating the appropriate ScaledObject resources - the installation of Kore is a seperate concern and should be assumed that Kore is installed.

The func deploy command will first check to see if Kore is running. If not, it will issue a log message saying it's skipping autoscale creation.

from keda.

I'm ok with that - but would likely prefer it fails outright if it doesn't see Kore running. And it would be nice if I didn't have to go as far as installing helm on my cluster to get Kore installed. But that's likely not a big deal as I expect most people with something in Kubernetes will reasonably have a helm client / tiller already setup.

from keda.

I think most of the points here are covered. See https://github.com/Azure/Kore/wiki/Using-core-tools-with-Kore-and-Osiris for details.

from keda.