v0.4.0

Changes:

• Delete legacy deploy directory. This was used in the previous versions to allow Kustomize to deploy Replika using remote manifests. Now, we are publishing manifests bundles directly in the releases. This will make the manifests atomic.
• Implement bundle-build on Makefile
• Add deprecation notice for directory deploy and update README reflecting all deployment possibilities
• Automate artifacts (bundles, binaries, Docker images) building in releases flow
• Docker images are now published in Github Container Registry

Contributors:
@sebastocorp @achetronic

v0.3.0

Breaking changes:

• Replika CR has been graduated to v1beta1

Changes:

• Update building tools: upgrade Go to v1.19.5 and kubebuilder to v3.8.0
• Docker images are being created for several architectures now: linux/amd64, linux/arm64, linuxs390x, linux/ppc64le for those having special servers out there

Notes:

• This upgrade grants compatibility with Kubernetes v1.25

Contributors:
@sebastocorp @achetronic

v0.2.5

Changes:

• Fix a label and its selectors in the deployment manifests which was hardcoded by the kubebuilder bootstraping stage. Now the label is control-plane: replika
• Add extra labels and selectors in the deployment manifests
• Add a sample manifest for the Replika custom resource of the v1alpha1
• Add license

v0.2.4

Changes:

• Fix function to update status of a Replika
• Clean unneeded code
• Refactor error messages: now they are all together declared in constants

v0.2.3

Changes:

• Fix the function to update the targets. Now it use another approach: patches instead of update

v0.2.2

Changes:

• Remove the rests of operator-sdk, now it's a full kubebuilder project
• Refactor the order of the reconciliation process
• Erase some unneeded conditions for the status

v0.2.0

Changes:

• The make kustomization-build command separate the manifests in directories now, using the kind for the name. This grants the best organization if the number of manifests increases with time
• Better examples written in the README file to explain how to be able to replicate other kind of resources
• Some error logs are now info logs to give a better idea when the controller is working well and not