release 0.3.0 (#184)

Author: LiorLieberman

CHANGELOG.md

@@ -2,15 +2,40 @@
 
 ## Table of Contents
 
+- [v0.3.0](#v030)
 - [v0.3.0-rc1](#v030-rc1)
 - [v0.2.0](#v020)
 - [v0.2.0-rc1](#v020-rc1)
 - [v0.1.0](#v010)
 - [v0.1.0-rc1](#v010-rc1)
 
+## v0.3.0
+
+## Major Themes
+
+### New Notifications Package
+
+new notifications package to provide mechanism for providers to display useful information generated during conversion process (#160, @Devaansh-Kumar)
+
+## Changes by Kind
+
+### Feature
+
+- Added notifications for Apisix (#176, @Devaansh-Kumar)
+- Added notifications for Istio provider (#171, @Devaansh-Kumar)
+- Added notifications for Kong (#173, @Devaansh-Kumar)
+- Added notifications for ingress-nginx (#177, @Devaansh-Kumar)
+- GCE now will display useful information generated during conversion process via the new notification package. (#169, @sawsa307)
+
+### Bug or Regression
+
+- Fix nginx canary annotation conversion (#182, @levikobi)
+- Fixed an issue that when the ingress class annotation is not specified on a GKE Ingress, the translation would result in a Gateway without name. (#167, @sawsa307)
+
 ## v0.3.0-rc1
 
 ## Changes by Kind
+
 ### Feature
 
 - Add a `--kubeconfig` flag to specify kubeconfig file location (#133, @YTGhost)
@@ -36,12 +61,15 @@
 ## v0.2.0
 
 ### Major Themes
+
 #### Providers storage
+
 Providers now fetch resources and store them in their local storage.
 This expands to ingress fetching. It is no longer happening on i2gw package and moved to be fetched at the provider level.
 
 #### New Providers
-Istio and APISIX support has been added. 
+
+Istio and APISIX support has been added.
 To check what features are currently supported please visit [Istio](https://github.com/kubernetes-sigs/ingress2gateway/blob/v0.2.0/pkg/i2gw/providers/istio/README.md) and [APIXIS](https://github.com/kubernetes-sigs/ingress2gateway/blob/v0.2.0/pkg/i2gw/providers/apisix/README.md).
 
 ### Feature
@@ -66,12 +94,15 @@ To check what features are currently supported please visit [Istio](https://gith
 ## v0.2.0-rc1
 
 ### Notable changes since v0.1.0
+
 #### Providers storage
+
 Providers now fetch resources and store them in their local storage.
 This expands to ingress fetching. It is no longer happening on i2gw package and moved to be fetched at the provider level.
 
 #### New Providers
-Istio and APISIX support has been added. 
+
+Istio and APISIX support has been added.
 To check what features are currently supported please visit [Istio](https://github.com/kubernetes-sigs/ingress2gateway/blob/v0.2.0-rc1/pkg/i2gw/providers/istio/README.md) and [APIXIS](https://github.com/kubernetes-sigs/ingress2gateway/blob/v0.2.0-rc1/pkg/i2gw/providers/apisix/README.md).
 
 ### Feature
@@ -93,6 +124,7 @@ To check what features are currently supported please visit [Istio](https://gith
 - Gateway API has been bumped to v1.0.0. (#98, @mlavacca)
 
 ## v0.1.0
+
 The first official release of ingress2gateway.
 
 ### Notable changes since v0.1.0-rc1
@@ -102,4 +134,5 @@ The first official release of ingress2gateway.
 - [Kong Provider] Add support for converting the `konghq.com/plugins` ingress annotation to a list of `ExtensionRef` HTTPRoute filters. (#72, @mlavacca)
 
 ## v0.1.0-rc1
-initial release candidate. 
+
+initial release candidate.

README.md

@@ -36,7 +36,7 @@ To contribute a new provider support - please read [PROVIDER.md](PROVIDER.md).
 ### Via go install
 
 If you have a Go development environment locally, you can install ingress2gateway
-with `go install github.com/kubernetes-sigs/ingress2gateway@v0.2.0`
+with `go install github.com/kubernetes-sigs/ingress2gateway@v0.3.0`
 
 This will put `ingress2gateway` binary in `$(go env GOPATH)/bin`