|
1 | 1 | # Change Log
|
2 | 2 |
|
| 3 | +## 34.3.0    |
| 4 | + |
| 5 | +* fix(Traefik Hub): AIServices are available in API Gateway |
| 6 | +* fix(Traefik Hub): :bug: handle main and latest build |
| 7 | +* feat: :sparkles: add missing microcks provider for Hub |
| 8 | +* feat(deps): update traefik docker tag to v3.3.3 |
| 9 | +* chore: update CRDs to v1.14.1 |
| 10 | + |
| 11 | +### Default value changes |
| 12 | + |
| 13 | +```diff |
| 14 | +diff --git a/traefik/values.yaml b/traefik/values.yaml |
| 15 | +index 4f93924..2d8ac73 100644 |
| 16 | +--- a/traefik/values.yaml |
| 17 | ++++ b/traefik/values.yaml |
| 18 | +@@ -948,6 +948,34 @@ hub: |
| 19 | + experimental: |
| 20 | + # -- Set to true in order to enable AI Gateway. Requires a valid license token. |
| 21 | + aigateway: false |
| 22 | ++ providers: |
| 23 | ++ microcks: |
| 24 | ++ # -- Enable Microcks provider. |
| 25 | ++ enabled: false |
| 26 | ++ auth: |
| 27 | ++ # -- Microcks API client ID. |
| 28 | ++ clientId: "" |
| 29 | ++ # -- Microcks API client secret. |
| 30 | ++ clientSecret: "" |
| 31 | ++ # -- Microcks API endpoint. |
| 32 | ++ endpoint: "" |
| 33 | ++ # -- Microcks API token. |
| 34 | ++ token: "" |
| 35 | ++ # -- Microcks API endpoint. |
| 36 | ++ endpoint: "" |
| 37 | ++ # -- Polling interval for Microcks API. |
| 38 | ++ pollInterval: 30 |
| 39 | ++ # -- Polling timeout for Microcks API. |
| 40 | ++ pollTimeout: 5 |
| 41 | ++ tls: |
| 42 | ++ # -- TLS CA |
| 43 | ++ ca: "" |
| 44 | ++ # -- TLS cert |
| 45 | ++ cert: "" |
| 46 | ++ # -- TLS insecure skip verify |
| 47 | ++ insecureSkipVerify: false |
| 48 | ++ # -- TLS key |
| 49 | ++ key: "" |
| 50 | + redis: |
| 51 | + # -- Enable Redis Cluster. Default: true. |
| 52 | + cluster: # @schema type:[boolean, null] |
| 53 | +``` |
| 54 | + |
3 | 55 | ## 34.2.0   
|
4 | 56 |
|
5 | 57 | **Release date:** 2025-01-28
|
@@ -351,17 +403,17 @@ index be89b00..9b4379c 100644
|
351 | 403 | There are multiple breaking changes in this release:
|
352 | 404 |
|
353 | 405 | 1. The default port of `traefik` entrypoint has changed from `9000` to `8080`, just like the Traefik Proxy default port
|
354 |
| - * You _may_ have to update probes accordingly (or set this port back to 9000) |
| 406 | + * You _may_ have to update probes accordingly (or set this port back to 9000) |
355 | 407 | 2. `publishedService` is enabled by default on Ingress provider
|
356 |
| - * You _can_ disable it, if needed |
| 408 | + * You _can_ disable it, if needed |
357 | 409 | 3. The `POD_NAME` and `POD_NAMESPACE` environment variables are now set by default, without values.
|
358 |
| - * It is no longer necessary to add them in values and so, it can be removed from user values. |
| 410 | + * It is no longer necessary to add them in values and so, it can be removed from user values. |
359 | 411 | 4. In _values_, **certResolvers** specific syntax has been reworked to align with Traefik Proxy syntax.
|
360 |
| - * PR [#1214](https://github.com/traefik/traefik-helm-chart/pull/1214) contains a complete before / after example on how to update _values_ |
| 412 | + * PR [#1214](https://github.com/traefik/traefik-helm-chart/pull/1214) contains a complete before / after example on how to update _values_ |
361 | 413 | 5. Traefik Proxy 3.2 supports Gateway API v1.2 (standard channel)
|
362 |
| - * It is recommended to check that other software using Gateway API on your cluster are compatible |
363 |
| - * There is a breaking change on CRD upgrade in this version, it _may_ do not work out of the box |
364 |
| - * See [release notes](https://github.com/kubernetes-sigs/gateway-api/releases/tag/v1.2.0) of gateway API v1.2 on how to upgrade their CRDs and avoid issues about invalid values on v1alpha2 version |
| 414 | + * It is recommended to check that other software using Gateway API on your cluster are compatible |
| 415 | + * There is a breaking change on CRD upgrade in this version, it _may_ do not work out of the box |
| 416 | + * See [release notes](https://github.com/kubernetes-sigs/gateway-api/releases/tag/v1.2.0) of gateway API v1.2 on how to upgrade their CRDs and avoid issues about invalid values on v1alpha2 version |
365 | 417 |
|
366 | 418 | The CRDs needs to be updated, as documented in the README.
|
367 | 419 |
|
|
0 commit comments