You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* The performance of the https://docs.stackable.tech/home/stable/hdfs/usage-guide/security.html#\_authorization[OPA Authorizer] has been greatly improved.
63
-
This _can_ be a breaking change so please make sure to read the hdfs-utils https://github.com/stackabletech/hdfs-utils/releases/tag/v0.4.0[release notes] for details.
64
-
* The User Info Fetcher HTTP API has been replaced with a Rego library. Please see https://docs.stackable.tech/home/nightly/opa/usage-guide/user-info-fetcher#_user_info_fetcher_api[user-info-fetcher API] for more information.
65
-
66
-
Logging::
67
-
68
-
* Apache NiFi: The ephemeral EmptyDir Volumes used to store log files before being aggregated have their size increased from a default of 33 MiB to 500 MiB.
69
-
Additionally the interval in which Logback checks if the maximum log file size has been reached was lowered from 60 seconds to 5 seconds.
70
-
71
-
Monitoring::
72
-
73
-
* https://github.com/prometheus/jmx_exporter[JMX Exporter] is a tool which allows us to expose JMX metrics as Prometheus metrics.
74
-
It is used by the following products: Hadoop, HBase, Hive, Kafka, Spark, Trino and ZooKeeper.
75
-
In the previous SDP release (24.7) we upgraded JMX Exporter from 0.20 to 1.0.1.
76
-
Unfortunately version 1.0.1 has a severe performance degradation which has been https://github.com/prometheus/jmx_exporter/pull/1009[fixed upstream] but is not yet released.
77
-
This SDP release (24.11) contains a fixed version bringing performance back to normal levels.
78
-
79
57
Security::
80
58
81
59
* The Stackable Data Platform now supports provisioning TLS certificates using https://cert-manager.io/[cert-manager].
82
60
* Added support for customizing `sAMAccountName` generation in secret operator.
83
61
* The Stackable Secret Operator now requests permission to read Listeners, which is required to provision secrets for listener volumes with the `listeners.stackable.tech/listener-name` annotation.
84
62
85
-
Commons::
86
-
87
-
* Pod Enrichment is now deprecated, and will be removed in the next release. Once removed, the SDP will no longer set any `enrichment.stackable.tech/` annotations on Pods.
88
-
89
63
Listener::
90
64
91
65
* The Stackable Operator for Kafka now uses the Stackable Listener Operator, allowing connectivity to be customized.
92
-
* The `ListenerClass.spec.serviceAnnotations` are now correctly propagated to created Service objects.
93
66
* Listeners can now be configured to use either IP addresses or fully qualified domain names (FQDNs).
94
67
95
68
Dependencies::
96
69
97
-
* Apache HBase: The hadoop-azure module was added to the image and is contained in the classpath.
98
-
This makes it possible to use the Azure Data Lake Storage Gen2 (ADLS) instead of HDFS.
99
-
See the xref:hbase:usage-guide/adls.adoc[usage guide] for detailed information.
70
+
Apache HBase: The hadoop-azure module was added to the image and is contained in the classpath.
71
+
This makes it possible to use the Azure Data Lake Storage Gen2 (ADLS) instead of HDFS.
72
+
See the xref:hbase:usage-guide/adls.adoc[usage guide] for detailed information.
100
73
101
74
Operations::
102
75
103
-
* The Stackable Operator for HDFS now supports upgrading existing HDFS installations.
104
-
However, this process requires some manual intervention as described https://docs.stackable.tech/home/nightly/hdfs/usage-guide/upgrading/[here].
76
+
The Stackable Operator for HDFS now supports upgrading existing HDFS installations.
77
+
However, this process requires some manual intervention as described https://docs.stackable.tech/home/nightly/hdfs/usage-guide/upgrading/[here].
105
78
106
79
Misc::
107
80
@@ -110,15 +83,50 @@ Misc::
110
83
See documentation xref:nifi:usage_guide/security#host-header-check[here].
111
84
* Apache Airflow: Allow custom arbitrary python code in `webserver_config.py`.
112
85
* Apache Superset: Allow custom arbitrary python code in `superset_config.py`.
113
-
* The size of the operator deployed CRDs was reduced significantly https://github.com/stackabletech/issues/issues/627[here].
114
86
115
87
Images::
116
88
89
+
Support the `restricted-v2` SecurityContextConstraint (SCC) in OpenShift.
90
+
Stackable currently defaults to the `nonroot-v2` SCC but we plan on migrating to the `restricted-v2` SCC in the future.
91
+
117
92
* Our Docker images now exclusively make use of numeric user IDs in `USER` statements allowing the use of `securityContext.runAsNonRoot`
118
93
* The group id of all files relevant to our products is now set to `0`.
119
94
This allows the images to be run with an arbitrary user as every container user will always belong to the root group (`0`).
120
-
This is required on OpenShift when migrating to the `restricted-v2` SecurityContextConstraint (SCC).
121
-
Stackable currently defaults to the `nonroot-v2` SCC but we plan on migrating to the `restricted-v2` SCC in the future.
95
+
This is required on OpenShift when migrating to the `restricted-v2` SCC.
96
+
97
+
=== Platform improvements
98
+
99
+
Vulnerabilities::
100
+
101
+
More than 142 CVEs were fixed in the Stackable product images.
102
+
This includes 11 critical and 55 high-severity CVEs.
103
+
104
+
Authorization::
105
+
106
+
* The performance of the https://docs.stackable.tech/home/stable/hdfs/usage-guide/security.html#\_authorization[OPA Authorizer] has been greatly improved.
107
+
This _can_ be a breaking change so please make sure to read the hdfs-utils https://github.com/stackabletech/hdfs-utils/releases/tag/v0.4.0[release notes] for details.
108
+
* The User Info Fetcher HTTP API has been replaced with a Rego library. Please see https://docs.stackable.tech/home/nightly/opa/usage-guide/user-info-fetcher#_user_info_fetcher_api[user-info-fetcher API] for more information.
109
+
110
+
Logging::
111
+
112
+
Apache NiFi: The ephemeral EmptyDir Volumes used to store log files before being aggregated have their size increased from a default of 33 MiB to 500 MiB.
113
+
Additionally the interval in which Logback checks if the maximum log file size has been reached was lowered from 60 seconds to 5 seconds.
114
+
115
+
Monitoring::
116
+
117
+
https://github.com/prometheus/jmx_exporter[JMX Exporter] is a tool which allows us to expose JMX metrics as Prometheus metrics.
118
+
It is used by the following products: Hadoop, HBase, Hive, Kafka, Spark, Trino and ZooKeeper.
119
+
In the previous SDP release (24.7) we upgraded JMX Exporter from 0.20 to 1.0.1.
120
+
Unfortunately version 1.0.1 has a severe performance degradation which has been https://github.com/prometheus/jmx_exporter/pull/1009[fixed upstream] but is not yet released.
121
+
This SDP release (24.11) contains a fixed version bringing performance back to normal levels.
122
+
123
+
Listener::
124
+
125
+
The `ListenerClass.spec.serviceAnnotations` are now correctly propagated to created Service objects.
126
+
127
+
Misc::
128
+
129
+
The size of the operator deployed CRDs was reduced significantly (see: https://github.com/stackabletech/issues/issues/627[stackabletech/issues#627]).
122
130
123
131
Bug fixes::
124
132
@@ -134,6 +142,13 @@ Bug fixes::
134
142
* Apache HBase: The operator now does not https://github.com/stackabletech/hbase-operator/pull/584[ignore the `hbaseRootdir` config property at role level].
135
143
* Apache Kakfa: The bootstrap Kafka service is now included in https://github.com/stackabletech/kafka-operator/pull/741[certificate SANs].
136
144
145
+
=== Platform deprecations
146
+
147
+
Commons::
148
+
149
+
Pod Enrichment is now deprecated, and will be removed in the next release.
150
+
Once removed, the SDP will no longer set any `enrichment.stackable.tech/` annotations on Pods.
151
+
137
152
=== Product versions
138
153
139
154
As with previous SDP releases, many product images have been updated to their latest versions.
@@ -211,8 +226,8 @@ These OpenShift versions are no longer supported:
211
226
212
227
==== Listener operator
213
228
214
-
* BREAKING: All ListenerClasses now default to using DNS hostnames, previously NodePort ListenerClasses (such as external-unstable) would use IP addresses.
215
-
Hence, all Nodes must now have resolvable hostnames, or the NodePort ListenerClasses must be configured to set `.spec.preferredAddressType: IP`.
229
+
BREAKING: All ListenerClasses now default to using DNS hostnames, previously NodePort ListenerClasses (such as external-unstable) would use IP addresses.
230
+
Hence, all Nodes must now have resolvable hostnames, or the NodePort ListenerClasses must be configured to set `.spec.preferredAddressType: IP`.
0 commit comments