Support GitOps with an option to output as YAML

[braunsonm]

Right now in order to deploy a function you need to run func deploy on a machine that is configured with access to your Kubernetes cluster.

In a GitOps approach, func deploy would have a parameter to output the generated Knative Service CR as YAML for example func deploy --build false -o yaml > knative-service.yml. This would allow GitOps tools like ArgoCD and Flux to read this committed YAML document in the source repository.

[lkingland]

Yes, exporting a .yaml is on our roadmap. If you don't want CI to have cluster access, you can use func build to update a container, and then define your service directly with service.yaml checked into source control

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[snavarro-factorial]

Just wanted to do a bump on this exporting function, since we manage our cluster with ArgoCD and being able to create a yaml from CLI would help.

[knative-prow]

@arnauvp-factorial: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.