Adds Namespace Support to Contour API

[danehans]

Adds namespace support to the Contour API type. Partially fixes issue #18.

/cc @jpeach @Miciah @stevesloka

[danehans]

Another option is to add the namespace name as a string and remove the namespaceSpec struct. If this option is preferred, I suggest the operator removes namespace deletion support. It may be safer for the operator to not support namespace deletion since it can cause significant side effects. Thoughts @jpeach?

[stevesloka]

@danehans do you need to have namespace be a param or just create the instance of Contour in the same namespace where the CRD is created?

[jpeach]

@danehans do you need to have namespace be a param or just create the instance of Contour in the same namespace where the CRD is created?

This would remove the possibility of different Contour resources specifying the same namespace. OTOH, it implies a different privilege model for being able to install Contour 🤷

[danehans]

@danehans do you need to have namespace be a param or just create the instance of Contour in the same namespace where the CRD is created?

@stevesloka typically an instance of the CRD, Contour in this case, exists in the same namespace as the operator and the operand(s), e.g. the Contour deployment, Envoy daemonset, etc. exist in a separate namespace (projectcontour by default). It's the operand namespace that this PR intends to address.

[jpeach]

lgtm