bump controller-tools to v0.2.0

[estroz]

Description of the change: bump controller-tools to v0.2.0 and update CRD generator API/unit tests.

Motivation for the change: controller-tools k8s deps versions should match those of controller-runtime when possible. #1143 requires some changes in this release too.

Note: #1607 should be closed once the refactor base branch is merged with master.

[estroz]

Two changes that need discussion:

1. CRD manifests can contain multiple specified versions, so CRD file naming should change from <group>_<version>_<kind>_crd.yaml to something else. For example, controller-tools uses <group>_<resource>.yaml for CRD's. To stick with our prior suffix convention and make it clear what the file contains I suggest <group>_<resource>_crd.yaml.
2. The CRD generator permits legacy support for spec.version but not simultaneously with spec.versions. The checkCRDVersions() function permits both forms as long as spec.version is the first element in spec.versions, which is correct behavior. How should we handle this discrepancy? Do we need to do anything aside from log a warning about spec.version deprecation and error if the expected versioning spec is not met?

/cc @joelanford @AlexNPavel @hasbro17 @lilic

[hasbro17]

@estroz Can we rebase or cherry pick #1652 into the refactor/controller-runtime-v0.2.0 branch?
And update the tag from // +genclient:nonNamespaced to // +kubebuilder:resource:path=<lowercase-kind-plural>,scope=Namespaced

Or do you want to do that as a separate PR?

[lilic]

@estroz For .1 I think we should follow the convention that kubebuilder has, so it will make it easier to migrate, do they have anything established already?

For 2. I think the log about the deprecation and error out if spec is not met, sounds good to me.

[lilic]

Can we update the CHANGELOG.

@hasbro17 if you are the one doing the migration guide we should make a note of the versions/version in there as well.

Otherwise lgtm

[estroz]

CRD file naming changes were quite extensive and touched both Helm and Ansible docs/tests. PTAL.

/cc @lilic @hasbro17 @AlexNPavel @joelanford @jmrodri @fabianvf

[estroz]

@lilic kubebuilder would generate a CRD file name cache.example.com_memcacheds.yaml. IMO cache_memcacheds_crd.yaml looks much nicer and contains all the necessary uniqueness/information that the kubebuilder name gives. WDYT?

[lilic]

@lilic kubebuilder would generate a CRD file name cache.example.com_memcacheds.yaml. IMO cache_memcacheds_crd.yaml looks much nicer and contains all the necessary uniqueness/information that the kubebuilder name gives. WDYT?

Since we are moving to kubebuilder at some point, I would suggest we go the kubebuilder way as we probably will have to change it then anyways.

[joelanford]

/lgtm

[hasbro17]

LGTM