Skip to content

CHANGELOG.md

Latest commit

 

History

History
60 lines (44 loc) · 2.17 KB

CHANGELOG.md

File metadata and controls

60 lines (44 loc) · 2.17 KB

Changelog

Table of Contents

v0.1.1

Release date: 2022-09-24

Maturity: ALPHA

Added

  • HTTPRoute support was added. If version of control plane image is at least 2.6, the Gateway=true feature gate is enabled, so the control plane can pick up the HTTPRoute and configure it on data plane. #302

v0.1.0

Release date: 2022-09-15

Maturity: ALPHA

This is the initial release which includes basic functionality at an alpha level of maturity and includes some of the fundamental APIs needed to create gateways for ingress traffic.

Initial Features

  • The GatewayConfiguration API was added to enable configuring Gateway resources with the options needed to influence the configuration of the underlying ControlPlane and DataPlane resources. #43
  • GatewayClass support was added to delineate which Gateway resources the operator supports. #22
  • Gateway support was added: used to create edge proxies for ingress traffic. #6
  • The ControlPlane API was added to deploy Kong Ingress Controllers which can be attached to DataPlane resources. #5
  • The DataPlane API was added to deploy Kong Gateways. #4
  • The operator manages certificates for control and data plane communication and configures mutual TLS between them. It cannot yet replace expired certificates. #103

Known issues

When deploying the gateway-operator through the bundle, there might be some leftovers from previous operator deployments in the cluster. The user needs to delete all the cluster-wide leftovers (clusterrole, clusterrolebinding, validatingWebhookConfiguration) before re-installing the operator through the bundle.