Update controller-gen and regenerate manifests and bundle

Due to the previous dependency updates, the old version was no longer compatible and would panic when trying to generate code containing DeepCopy, DeepCopyInto, and DeepCopyObject method implementations.

Author: iamjoemccormick

operator/Makefile

@@ -164,7 +164,7 @@ ENVTEST ?= $(LOCALBIN)/setup-envtest
 
 ## Tool Versions
 KUSTOMIZE_VERSION ?= v3.8.7
-CONTROLLER_TOOLS_VERSION ?= v0.9.2
+CONTROLLER_TOOLS_VERSION ?= v0.14.0
 
 KUSTOMIZE_INSTALL_SCRIPT ?= "https://raw.githubusercontent.com/kubernetes-sigs/kustomize/master/hack/install_kustomize.sh"
 .PHONY: kustomize

operator/api/v1/zz_generated.deepcopy.go

@@ -2,7 +2,6 @@
 apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRole
 metadata:
-  creationTimestamp: null
   name: manager-role
 rules:
 - apiGroups:

operator/bundle/manifests/beegfs.csi.netapp.com_beegfsdrivers.yaml

@@ -173,15 +173,21 @@ From the *operator/* directory
 ### Prepare Changes For a Pull Request
 <a name="prepare-changes-for-a-pull-request"></a>
 
-If you have done manual testing of changes with builds created from the dev
-environment, you'll want to unset any custom VERSION environment variables or
-changes to the Makefile for the version. Then run through the following sequence
-to generate the necessary changes without pushing any builds to the registry.
+If you have done manual testing of changes with builds created from the dev environment, you'll want
+to unset any custom VERSION or IMAGE_TAG_BASE variable overridden using the environment or changes
+to the Makefile . Then run through the following sequence to generate the necessary changes without
+pushing any builds to the registry.
 
 * make generate manifests
 * make build
 * make manifests bundle
 
+Note: Generally the VERSION set in the Makefile and in various manifests should not be updated until
+it is time to actually release a new version of the driver. If this version is updated beforehand,
+then it becomes difficult to find all the places in the repository where the old version needs to be
+updated when it is actually time to release. Unless a new Git tag is pushed, the container images
+tagged with a released version of the operator and bundle will not be overwritten.
+
 ### Update the operator-sdk version
 <a name="update-the-operator-sdk-version"></a>