- this is related to PR #175
- ObjectMeta.Labels and ObjectMeta.Annotations are merged when
patching instead of replace.

- this is related and a followup to feature in PR #175
- SetControllerReference should be called after override is applied since
the object's name and namespace could be modified by the override.
- delete the unit test which asserts that sts's ns can be overwritten
by override; the test is incorrect and will never pass, since
cluster-scoped resources (sts in this case), can not be owned by objects
in a other namespace.

Update issue templates

Small readme changes

Remove boilerplate from bug report. Ask for relevant information to reproduce a bug in software.

- related to issue #143
- add reasoning about why the CRD won't install in a 1.18 k8s
cluster
- move Override KEP into proposals/implemented

- RabbitmqResourceBuilder is used sed in all tests in
internal/resource for the same purpose
- Use the same variable name for consistency

- we do not need to create a new sts builder in each test spec

- also update helm chart description

Remove deprecated `bases` from kustomization files

This addresses issue #183

* Add statefulSet override

- new crd properties: spec.override.statefulSet, which is
our own definition of appsv1.StatefulSet, which allows users to provide
a patch that will be applied on top of generated statefulset definition
as an override.
- new type EmbeddedObjectMeta, which is a partially metav1.ObjectMeta;
it is used in StatefulSet, PodTemplateSpec, and PersistentVolumeClaim.
- custom types are needed because of the pruning behavior of
`preserveUnknownFields: false`, which is going to be the default
behavior for crd v1.
- all fields in the custom StatefulSetSpec are optional; including
selector, serviceName...etc

`bases` is a deprecated section of the kustomize API, and is replaced by
`resources` in v2.1.0 onwards. Since we use kustomize 3.X, this moves
our kustomization yamls to the new accepted format.

This also moves our Makefile away from using `kubectl <apply/delete>
-k`, which uses kubectl's older, bundled version of Kustomize v2.0.3
(see [this issue](https://github.com/kubernetes/kubectl/issues/818)).

Declare Go 1.13 in module file

* Add environment setup to KinD README

Added a step to set up environment variables before running `make
deploy-kind`

* Fixed various typos in README

This brings spelling of resources to be more consistent:
* `RabbitmqCluster` for the CR
* `cluster-operator` for the operator & image

* Add supported version/License/Copyright to README

* helm charts cleanup
* Add mtls, remove repo references to charts makefile
* Update template test version number
* remove references in makefile
* Update wording
Co-authored-by: James McNeil <jmcneil@pivotal.io>

Add beta notice to README

Multiline description and mTLS property

This software is provided as a beta pre-release. This commit updates the
README to reflect this.

Remove GH actions cause we dont have access to them

* Remove CI-related code from repo

- CI specified config is moved to CI repo and rest is templated as env vars
- Rename OPERATOR_IMAGE and split with registry url
- Adds Makefil env var description to README
Co-authored-by: Feroz Jilla <fjilla@pivotal.io>

* a few rabbitmqcluster examples

* typo

Set default rabbit version to 3.8.5

- related to issue #167

Adds mutual TLS
Co-authored-by: James McNeil <jmcneil@vmware.com>

ReconcileSuccess status condition

Update Operator Chart metadata

We actively develop and build using Go 1.13. Our mod file should reflect
this information.

MPL license in controller and config files