Start waiting for certs to be ready before sending data to the channel

[tenzen-y]

What this PR does / why we need it:
Currently, the controller checks if the cert-generator is enabled before starting setupControllers.

katib/cmd/katib-controller/v1beta1/main.go

Lines 136 to 149 in 7f0d922

	ctx := signals.SetupSignalHandler()
	certsReady := make(chan struct{})
	defer close(certsReady)
	if initConfig.CertGeneratorConfig.Enable {
	if err = cert.AddToManager(mgr, initConfig.CertGeneratorConfig, certsReady); err != nil {
	log.Error(err, "Failed to set up cert-generator")
	}
	} else {
	certsReady <- struct{}{}
	}
	// The setupControllers will register controllers to the manager
	// after generated certs for the admission webhooks.
	go setupControllers(mgr, certsReady, hookServer)

So, if the cert-generator is disabled, the controller sends data to certsReady channel before the controller starts waiting for certs to get ready. By this behavior, in the katib-with-kubeflow, the controller eternally keeps waiting for the certs to get ready.

katib/cmd/katib-controller/v1beta1/main.go

Lines 170 to 171 in 7f0d922

	// The certsReady blocks to register controllers until generated certs.
	<-certsReady

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Checklist:

• Docs included if any changes are user facing

[andreyvelich]

/lgtm

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andreyvelich, tenzen-y

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [andreyvelich,tenzen-y]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment