Upgrade conditions

[ValClarkson]

Checklist:

• Have you added an explanation of what your changes do and why you'd like them to be included?
• Have you updated or added documentation for the change, as applicable?
• Have you tested your changes on all related environments with successful results, as applicable?
  • Have you added automated tests?

Type of Changes:

• [x ] New feature
• Bug fix
• Documentation
• Testing enhancement
• Other

What is the current behavior (link to any open issues here)?

What is the new behavior (if this is a feature change)?

• Breaking change (fix or feature that would cause existing functionality to change)

Added conditions for upgrading the cluster

Other Information:

[dsessler7]

So I think we want something similar to what Ben did on lines 259-274 in crunchybridgecluster_controller.go where we check to see if an error condition is in place. If there is an error condition, we check the observed generation. If the observed generation hasn't changed, meaning the customer hasn't changed the spec, then we want to return early.

[dsessler7]

Couple nitpicks, but looks good otherwise.