Each rook operator will need to deploy its own admission controller. in this PR only the admission controller for Ceph is being implemented. Wherever there is something specific to the ceph admission controller we should add it to the name.

We really need some unit tests for the new admission package. These functions that create service, deployment, or pod specs are generally simple to test. You can see other operator unit tests for examples where services or other resources are created.

Integration tests will also confirm the admission controller can start and run successfully. I believe we could keep this fairly simple and get a lot of validation with these steps:

• In the CreateCephOperator() method:
  • Create the RBAC. The easiest thing might be to add the yaml to GetRookOperator() in the ceph_manifests.go.
  • Call out to the script that generates the self-signed cert
• After the tests start the operator around this line, verify that the admission controller is in running state

	if !h.k8shelper.IsPodInExpectedState("rook-ceph-admission-controller", onamespace, "Running") {
		logger.Error("admission controller is not running")
		return false, err
	}

Added integration tests

As a follow-up PR, please also add unit tests in addition to the integration tests.

In case the service spec has changed between releases, the k8sutils.CreateOrUpdateService() method will help here.

Instead of returning false, I'd suggest and assert.Fail() and then allow the test to continue. This will raise an error to fail the test, but it won't prevent the test from running.

You're configuring the admission controller after the helm chart is installed, which means the operator will already be running. You need to configure the admission controller before launching the helm chart.