Provide CRD and resources as library

[eljoth]

The workflow I am expecting from the Pulumi operator is as follows:

1. Create a repository with a working Pulumi program, containing the Pulumi operator.
2. Deploy the project to a cluster manually one time.
3. Let the Operator handle changes in desired state automatically (see Git branches or tags not working #103, Add support to track Git repo branches by polling / using webhooks to act on branch updates #50)

Currently, the developer has to either deploy the crd on his own by applying the yaml or translate the existing yaml into his pulumi program. In both cases it needs unnecessary effort to keep the Operator updated by manually changing those files and keep them updated.

Affected feature

Provide the CRD and all resources required as library (e.g. Go Module) to make as well deploying as upgrading easier. Developers just update the dependency and take care of changes breaking their code and all they have to do is push the changes to their repo. Pulumi Operator will notice that there are changes and redeploy itself in an updated version. This feature enables a Helm-like experience with the addition of all advantages Pulumi has to offer.

[eljoth]

Maybe we could make use of crd2pulumi to automate this procedure?

[UnstoppableMango]

Not sure if it's been mentioned elsewhere, but the CRDs don't seem to map cleanly when using crd2pulumi because of the name clashes with the Pulumi/pulumi namespace