We are delighted to present version 1.15.0 of Contour Operator, which provides a method for packaging, deploying, and managing Contour.

A big thank you to everyone who contributed to the release.

Major Changes

NodePortService configuration

Adds support for configuring an Envoy Service of type NodePort. Previously, provisioning multiple Contours would fail when using "NodePortService" network publishing due to port collisions. This release adds the following:

• A nodePorts field to Envoy network publishing for explicitly specifying http/https nodeports.
• When nodePorts is unspecified, the Kubernetes cluster will auto-assign random nodePort values.

Note: Previously, nodeports 30080 and 30443 were statically assigned for the Envoy HTTP/HTTPS Service ports. With this change, these nodeports are auto-assigned by Kubernetes if nodePorts is unspecified. To maintain backwards compatibility with the previous default, assign the nodeports. For example:

apiVersion: operator.projectcontour.io/v1alpha1
kind: Contour
metadata:
  name: contour-sample
spec:
  networkPublishing:
    envoy:
      type: NodePortService
      nodePorts:
        - name: http
          portNumber: 30080
        - name: https
          portNumber: 30443

Thanks @danehans for implementing this feature in #317!

Bugs Fixed

• When a ClusterIP Envoy service was being used, it was not being deleted when the Contour was removed. #292 fixes this. Thanks @nak3!
• When a ClusterIP Envoy service was requested along with a Gateway, the service was not being created. #293 fixes this. Thanks @nak3!
• The Contour deployment was not being updated when the Contour spec changed. #300 fixes this. Thanks @nak3!