THIS IS NOT READY FOR REAL USE IN ANY WAY, SHAPE, OR FORM.

If you just want to try this out quickly (or for debugging purposes), you can use this to quickly run the operator locally while still pointing it at your remote OpenShift cluster.

(Note that you will not see any deployments of the operator running in the cluster using this method.)

export OPERATOR_NAME=amq-broker-operator
operator-sdk up local --namespace=jasee

operator-sdk build docker.io/jacobsee/amq-operator
docker push docker.io/jacobsee/amq-operator

(if you're not me, then... use a different repository. Remember to change deploy/operator.yaml if you do.)

You're going to need cluster-admin for this. I'm not happy about that either.

oc apply -f deploy/service_account.yaml
oc apply -f deploy/role.yaml
oc apply -f deploy/role_binding.yaml
oc apply -f deploy/crds/jacobsee_v1alpha1_amqbroker_crd.yaml
oc apply -f deploy/operator.yaml

Get yourself a nice AMQBroker resource, like this one

apiVersion: jacobsee.com/v1alpha1
kind: AMQBroker
metadata:
  name: example-amqbroker
spec:
  username: test_user
  password: test_pass

and deploy it (it's included as an example).

oc apply -f deploy/crds/jacobsee_v1alpha1_amqbroker_cr.yaml

You should see a deployment example-amqbroker-deployment, a service example-amqbroker-service, and a route example-amqbroker-route.

If you access the route, it should take you to the AMQ management console (after a few minutes of booting up... it's not instantaneous).

Unit testing of the reconcile loop can be ran with go test ./pkg/controller/amqbroker. This stands up a fake kube API for our operator to operate against, creates an AMQBroker custom resource, and triggers a reconcile event on that resource.

You're right, I haven't added those things, you should give it a try. I just did this to quickly learn about operators.

pkg/apis/jacobsee/v1alpha1/amqbroker_types.go

pkg/controller/amqbroker/amqbroker_controller.gouMBy9M2P6A2xS3