Functions CRD and Operator

[lkingland]

Functions CRD and Operator

This is a discussion intended to help define the validity and scope of a Functions CRD and Operator.

Overview

Developers familiar with Kubernetes are accustomed to kubectl apply -f. Providing a simple CRD which defines enough about a function for the cluster to perform a build and deploy internally would both adhere to this paradigm but also be nearly frictionless from a developer's perspective given a properly configured cluster, with no required local dependencies other than kubectl and a cluster connection.

Scope

There are no features on our roadmap which require a CRD. Everything can be accomplished (and probably should be accomplished) with the existing Serving and Eventing structures. Even auto-update is likely better mediated via CI/CD than as an internal operator. Therefore the scope of this CRD and Operator is likely quite narrow: just enough to trigger an in-cluster build and deploy using a CRD which is essentially a pointer to a repository.

Considerations

One key consideration is the necessity of a properly configured cluster, with extensive user feedback to ensure this is the case.