Make it possible to disable ingress/route

[weisdd]

If you deploy a grafana with an Ingress set in the spec and then remove Ingress from the spec, Ingress object remains in the cluster.

A dangling ingress is not necessarily a big issue, because it's very unlikely for someone to specify ingress and then delete it. Though, if it's something that doesn't require much effort to fix, it'd be nice to do so.

[NissesSenap]

How do we want to handle the creation of ingress/route? One solution would be to just say that if ingress/route is empty don't create a ingress or route, which seems like the easiest way.
But the bad thing here is that the OCP users that is currently used to have a route auto created for them won't get that fuctionallity.

Personally I think it's better that we have a consistent way of working and I think route and ingress should work the same way. So my suggestion is to have ingress/route disabled by default.

Another option is of course to keep the current way of working but we add some kind of ingress_enabled resource but it's kind of ugly and you could still have ingress config defined and have ingress_enabled: false and it would still be disabled which is a rather strange thing from a user point of view.

This would be good to fix before rc0.

[NissesSenap]

@tamcore Is this something that you are still open to look in to?
We are unable to keep up with the discussion in the other repo since it have been archived.

[weisdd]

@NissesSenap Shall we unarchive the experimental repo for a moment, transfer all outstanding issues to this repo, and then archive the experimental one again?

[NissesSenap]

It's the same issue, we had some discussions in there. I think we should be okay to keep this one instead.

[pb82]

fixed in #1028