Migrate from Gloo Gateway

Migrate Gloo Gateway 2.0 resources to Solo Enterprise for kgateway 2.1.

Starting in 2.1, Gloo Gateway is renamed to Solo Enterprise for kgateway, an enterprise version of the kgateway open source project version 2.2. The update standardizes Solo.io’s branding by removing Gloo from all resources, such as Kubernetes custom resource definitions (CRDs) and Helm charts.

Helm Installation Changes

Review the following table of Helm installation changes between the 2.0 and 2.1 versions.

2.0 Helm installation

Review the following Helm installation commands for the 2.0 version.

helm upgrade -i gloo-gateway-crds \
  oci://us-docker.pkg.dev/solo-public/gloo-gateway/charts/gloo-gateway-crds \
  --create-namespace --namespace gloo-system --version 2.0.2

helm upgrade -i gloo-gateway \
  oci://us-docker.pkg.dev/solo-public/gloo-gateway/charts/gloo-gateway \
  -n gloo-system --version 2.0.2 \
  --set-string licensing.glooGatewayLicenseKey=$GLOO_LICENSE_KEY

2.1 Helm installation

Review the following Helm installation commands for the 2.1 version.

helm upgrade -i enterprise-kgateway-crds \
  oci://us-docker.pkg.dev/solo-public/enterprise-kgateway/charts/enterprise-kgateway-crds \
  --create-namespace --namespace kgateway-system --version 2.1.5

helm upgrade -i enterprise-kgateway \
  oci://us-docker.pkg.dev/solo-public/enterprise-kgateway/charts/enterprise-kgateway \
  -n kgateway-system --version 2.1.5 \
  --set-string licensing.licenseKey=$GLOO_LICENSE_KEY

GatewayClass changes

Any Gateway resources referencing gatewayClassName: gloo-gateway-v2 must be updated to gatewayClassName: enterprise-kgateway.

CRD changes

Review the following CRD changes between the 2.0 and 2.1 versions.

Renamed Enterprise CRDs

The API group changed from gloo.solo.io to enterprisekgateway.solo.io.

Unchanged kgateway OSS CRDs

These gateway.kgateway.dev CRDs exist in both versions with no changes.

Unchanged supporting CRDs

Unchanged Gateway API CRDs

Standard Kubernetes Gateway API v1.4.0 CRDs (gateway.networking.k8s.io) are the same in both versions.

• BackendTLSPolicy
• GatewayClass
• Gateway
• GRPCRoute
• HTTPRoute
• ReferenceGrant

New CRD in 2.1

Enterprise traffic policy changes

The GlooTrafficPolicy (2.0) is now EnterpriseKgatewayTrafficPolicy (2.1). Beyond the rename, there are field-level changes within the spec.

Renamed fields

All enterprise-specific gloo-prefixed fields are now ent-prefixed:

Unchanged fields

These fields exist in both versions with no changes:

• autoHostRewrite
• buffer
• cors
• csrf
• extAuth
• extProc
• headerModifiers
• rateLimit
• rbac
• retry
• targetRefs
• targetSelectors
• timeouts
• transformation

New fields in 2.1

Removed Fields in 2.1

Summary of traffic policy changes

Note the following differences between the 2.0 and 2.1 resources for traffic policy.

1. apiVersion: gloo.solo.io/v1alpha1 -> enterprisekgateway.solo.io/v1alpha1
2. kind: GlooTrafficPolicy -> EnterpriseKgatewayTrafficPolicy
3. namespace: gloo-system -> kgateway-system
4. glooExtAuth -> entExtAuth
5. glooRateLimit -> entRateLimit
6. glooTransformation -> entTransformation
7. Namespace references within the spec also updated to kgateway-system

2.0 GlooTrafficPolicy

apiVersion: gloo.solo.io/v1alpha1
kind: GlooTrafficPolicy
metadata:
  name: my-policy
  namespace: gloo-system
spec:
  targetRefs:
    - group: gateway.networking.k8s.io
      kind: HTTPRoute
      name: my-route
  glooExtAuth:
    authConfigRef:
      name: my-auth
      namespace: gloo-system
  glooRateLimit:
    global:
      descriptors:
        - key: generic_key
          value: per-route
  glooTransformation:
    stages:
      - requestTransformation:
          transformationTemplate:
            headers:
              x-custom:
                text: "hello"

2.1 EnterpriseKgatewayTrafficPolicy

apiVersion: enterprisekgateway.solo.io/v1alpha1
kind: EnterpriseKgatewayTrafficPolicy
metadata:
  name: my-policy
  namespace: kgateway-system
spec:
  targetRefs:
    - group: gateway.networking.k8s.io
      kind: HTTPRoute
      name: my-route
  entExtAuth:
    authConfigRef:
      name: my-auth
      namespace: kgateway-system
  entRateLimit:
    global:
      descriptors:
        - key: generic_key
          value: per-route
  entTransformation:
    stages:
      early:
        requests:
          - transformationTemplate:
              headers:
                x-custom:
                  text: "hello"

Example: Gateway

Note the namespace and gatewayClassName changes.

2.0 Gateway

apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: my-gateway
  namespace: gloo-system
spec:
  gatewayClassName: gloo-gateway-v2
  listeners:
    - name: http
      port: 8080
      protocol: HTTP

2.1 Gateway

apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: my-gateway
  namespace: kgateway-system
spec:
  gatewayClassName: enterprise-kgateway
  listeners:
    - name: http
      port: 8080
      protocol: HTTP

Migration checklist

Next steps

1. Review the rest of the release notes for any other changes that you want to prepare for before you upgrade.

2. Upgrade from Gloo Gateway 2.0 to Solo Enterprise for kgateway 2.1.