Skip to content

Commit 596285e

Browse files
committed
fix doc structure
1 parent a4a7327 commit 596285e

File tree

1 file changed

+29
-32
lines changed

1 file changed

+29
-32
lines changed

site/content/releases.md

Lines changed: 29 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,38 @@ doctypes:
66
title: Releases
77
toc: true
88
weight: 2100
9-
## 3.7.1
9+
---
10+
{{< note >}}
11+
FIPS compliant images are currently impacted by compatibility issues with a dependent library.
1012

11-
06 Nov 2024
13+
We recommend against:
14+
1. Patching older FIPS images, which could re-introduce the incompatible dependency.
15+
2. Building new custom FIPS images.
16+
{{< /note >}}
1217

13-
### <i class="fa-solid fa-bomb"></i> Breaking Changes
18+
{{< note >}}
19+
In our next major release, `v4.0.0`, the default log library for NGINX Ingress Controller will be changed from `golang/glog` to `log/slog`.
20+
This will mean that logs generated by NGINX Ingress Controller will be in a structured format with the option to choose a `string` or `json` output.
21+
This will not affect logs generated by NGINX.
22+
To ensure backwards compatibility, we will ensure the existing log format, `glog`, will be maintained through a configuration option for the next 3 releases.
23+
{{< /note >}}
1424

15-
### <i class="fa-solid fa-rocket"></i> Features
25+
{{< important >}}
26+
CRD version removal notice.
27+
In our next major release, `v4.0.0`, support for the following apiVersions for these listed CRDs will be dropped:
28+
1. `k8s.nginx.org/v1alpha` for `GlobalConfiguration`
29+
2. `k8s.nginx.org/v1alpha` for `Policy`
30+
3. `k8s.nginx.org/v1alpha` for `TransportServer`
31+
32+
Prior to upgrading, **please ensure** that any of these resources deployed as `apiVersion: k8s.nginx.org/v1alpha1` are upgraded to `apiVersion: k8s.nginx.org/v1`
33+
If a resource of `kind: GlobalConfiguration`, `kind: Policy` or `kind: TransportServer` are deployed as `apiVersion: k8s.nginx.org/v1alpha1`, these resources will be **deleted** when upgrading from, at least, `v3.4.0` to `v4.0.0`
34+
35+
When `v4.0.0` is released, the release notes will contain the required upgrade steps to go from `v3.X.X` to `v4.X.X`
36+
{{< /important >}}
37+
38+
## 3.7.1
39+
40+
06 Nov 2024
1641

1742
### <i class="fa-solid fa-bug-slash"></i> Fixes
1843

@@ -40,34 +65,6 @@ versions: 1.25-1.31.
4065

4166

4267
---
43-
{{< note >}}
44-
FIPS compliant images are currently impacted by compatibility issues with a dependent library.
45-
46-
We recommend against:
47-
1. Patching older FIPS images, which could re-introduce the incompatible dependency.
48-
2. Building new custom FIPS images.
49-
{{< /note >}}
50-
51-
{{< note >}}
52-
In our next major release, `v4.0.0`, the default log library for NGINX Ingress Controller will be changed from `golang/glog` to `log/slog`.
53-
This will mean that logs generated by NGINX Ingress Controller will be in a structured format with the option to choose a `string` or `json` output.
54-
This will not affect logs generated by NGINX.
55-
To ensure backwards compatibility, we will ensure the existing log format, `glog`, will be maintained through a configuration option for the next 3 releases.
56-
{{< /note >}}
57-
58-
{{< important >}}
59-
CRD version removal notice.
60-
In our next major release, `v4.0.0`, support for the following apiVersions for these listed CRDs will be dropped:
61-
1. `k8s.nginx.org/v1alpha` for `GlobalConfiguration`
62-
2. `k8s.nginx.org/v1alpha` for `Policy`
63-
3. `k8s.nginx.org/v1alpha` for `TransportServer`
64-
65-
Prior to upgrading, **please ensure** that any of these resources deployed as `apiVersion: k8s.nginx.org/v1alpha1` are upgraded to `apiVersion: k8s.nginx.org/v1`
66-
If a resource of `kind: GlobalConfiguration`, `kind: Policy` or `kind: TransportServer` are deployed as `apiVersion: k8s.nginx.org/v1alpha1`, these resources will be **deleted** when upgrading from, at least, `v3.4.0` to `v4.0.0`
67-
68-
When `v4.0.0` is released, the release notes will contain the required upgrade steps to go from `v3.X.X` to `v4.X.X`
69-
{{< /important >}}
70-
7168
## 3.7.0
7269

7370
30 Sept 2024

0 commit comments

Comments
 (0)