This release of the Contour Operator includes support for:
- Ownership Labeling: The operator will only manage resources that include the operator's name/namespace labels. This will ensure the operator does not unintentionally manage existing resources and provides a mechanism to migrate existing Contour installs to being managed by the operator.
- Network Publishing: Users can now manage network configuration through the
Contourcustom resource. For example, a user can provision a Contour environment where Envoy uses a non-default container port or is front-ended by a NodePort service. Currently, the API is restricted to managing Envoy network settings.