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
Copy file name to clipboardExpand all lines: modules/ROOT/pages/getting-started.adoc
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,11 +32,11 @@ Install the Stackable command line utility xref:management:stackablectl:index.ad
32
32
33
33
The Stackable operators are components that translate the service definitions deployed via Kubernetes into deploy services on the worker nodes. These can be installed on any node that has access to the Kubernetes control plane. In this example we will install them on the controller node.
34
34
35
-
Stackable operators can be installed using `stackablectl`. Run the following commands to install ZooKeeper, Kafka and NiFi from the Stackable 24.11 release.
35
+
Stackable operators can be installed using `stackablectl`. Run the following commands to install ZooKeeper, Kafka and NiFi from the Stackable 25.3 release.
Copy file name to clipboardExpand all lines: modules/ROOT/partials/release-notes/release-22.11.adoc
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ This is the third release of the Stackable Data Platform, which this time focuse
9
9
10
10
The following new major platform features were added:
11
11
12
-
CPU and memory limits configurable::
12
+
===== CPU and memory limits configurable
13
13
14
14
The operators now https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/[request] resources from Kubernetes for the products and required CPU and memory can now also be configured for all products.
15
15
If your product instances are less performant after the update, the new defaults might be set too low and we recommend to xref:kafka:usage-guide/storage-resources.adoc[set custom requests] for your cluster.
@@ -24,7 +24,7 @@ If your product instances are less performant after the update, the new defaults
Copy file name to clipboardExpand all lines: modules/ROOT/partials/release-notes/release-22.6.adoc
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,37 +13,37 @@ While we are very proud of this release it is our first one and we'll add new fe
13
13
14
14
==== Platform features
15
15
16
-
Easily install production ready data applications::
16
+
===== Easily install production ready data applications
17
17
18
18
Using a familiar declarative approach, users can easily install data applications such as Apache Kafka or Trino across multiple cloud Kubernetes providers or on their own data centers.
19
19
The installation process is fully automated while also providing the flexibility for the user to tune relevant aspects of each application.
20
20
21
-
Monitoring::
21
+
===== Monitoring
22
22
23
23
All products have monitoring with prometheus enabled.
24
24
xref:operators:monitoring.adoc[Learn more]
25
25
26
-
Service discovery::
26
+
===== Service discovery
27
27
28
28
Products on the Stackable platform use service discovery to easily interconnect with each other.
29
29
xref:concepts:service_discovery.adoc[Learn more]
30
30
31
-
Configuration overrides::
31
+
===== Configuration overrides
32
32
33
33
All operators support configuration overrides, these are documented in the specific operator documentation pages.
34
34
35
-
Common S3 configuration::
35
+
===== Common S3 configuration
36
36
37
37
Many products support connecting to S3 to load and/or store data.
38
38
There is a common resource for S3 connections and buckets across all operators that can be reused.
39
39
xref:concepts:s3.adoc[Learn more]
40
40
41
-
Roles and role groups::
41
+
===== Roles and role groups
42
42
43
43
To support hybrid hardware clusters, the Stackable platform uses the concept of role groups.
44
44
Services and applications can be configured to maximize hardware efficiency.
* https://github.com/stackabletech/spark-k8s-operator/pull/126[Apache Spark on K8s]
22
22
23
-
Support for internal and external TLS::
23
+
===== Support for internal and external TLS
24
24
25
25
The following operators support operating the products at a maximal level of transport security by using TLS certificates to secure internal and external communication:
For every role that you specify (e.g. HDFS namenodes or Trino workers) a PDB is created.
18
18
This will determine the extent to which roles for a given application may be inactive at any given time.
19
19
See xref:concepts:operations/pod_disruptions.adoc[the documentation] for more details.
20
20
21
-
Graceful shutdown::
21
+
===== Graceful shutdown
22
22
Graceful shutdown refers to the managed, controlled shutdown of service instances in the manner intended by the software authors.
23
23
Typically, an instance will receive a signal indicating the intent for the server to shut down, and it will initiate a controlled shutdown.
24
24
Our operators configure a sensible amount of time Pods are granted to properly shut down without disrupting the availability of the product.
25
25
See xref:concepts:operations/graceful_shutdown.adoc[the documentation] for more details.
26
26
27
-
Signed SDP product images::
27
+
===== Signed SDP product images
28
28
As of this release all Stackable product images are signed (the signing of operator images was delivered in SDP 23.7).
29
29
Please see this xref:guides:enabling-verification-of-image-signatures.adoc[tutorial] for more information.
30
30
31
-
Airflow KubernetesExecutor::
31
+
===== Airflow KubernetesExecutor
32
32
Airflow clusters can now be configured to use Kubernetes executors, whereby pods are spun up for job tasks and terminated when complete, thus offering an alternative way to use resources without the need for job queuing.
33
33
34
-
Overridable Java security settings::
34
+
===== Overridable Java security settings
35
35
For JVM-based products (i.e. Druid, HBase, HDFS, Hive, Kafka, NiFi, Spark, Trino and ZooKeeper) it is now possible to provide custom security settings that override the default values.
36
36
This allows the user to control things such as DNS lookup caches.
37
37
38
-
Stackable Cockpit::
38
+
===== Stackable Cockpit
39
39
This release includes a very early preview version of Stackable Cockpit, a browser-based management tool which interacts with the Stackable data platform to display e.g. deployed stacklets and their status.
40
40
41
-
stackablectl::
41
+
===== stackablectl
42
42
Our command line tool has been re-worked to use the same backbone as Stackable Cockpit: you can find out about the recent enhancements by visiting the online xref:management:stackablectl:index.adoc[documentation].
43
43
44
-
Listener operator::
44
+
===== Listener operator
45
45
The listener-operator was introduced in release 23.1 and the associated ServiceType field in 23.4.
46
46
In this release we introduce configurable ListenerClass _presets_ that map to the service types appropriate for different environments.
47
47
This is discussed in more detail in the xref:listener-operator:listenerclass.adoc[documentation].
48
48
49
-
Openshift certification::
49
+
===== Openshift certification
50
50
All Stackable operators in the 23.11 release have been certified for Openshift versions 4.11-4.13 and can be installed directly from the OperatorHub UI: image:openshift_operatorhub.png[OperatorHub in Openshift portal]
51
51
52
-
Product features::
52
+
===== Product features
53
53
54
54
Additionally, there are some other individual product features that are noteworthy:
Copy file name to clipboardExpand all lines: modules/ROOT/partials/release-notes/release-23.4.adoc
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,19 +29,19 @@ It is recommended to install <<Release 23.4.1>> instead, as it contains relevant
29
29
30
30
The following new major platform features were added:
31
31
32
-
Cluster Operation::
32
+
===== Cluster Operation
33
33
34
34
The first part of xref:concepts:operations/cluster_operations.adoc[Cluster operations] was rolled out in every applicable Stackable Operator.
35
35
This supports pausing the cluster reconciliation and stopping the cluster completely.
36
36
Pausing reconciliation will not apply any changes to the Kubernetes resources (e.g. when changing the custom resource).
37
37
Stopping the cluster will set all replicas of StatefulSets, Deployments or DaemonSets to zero and therefore result in the deletion of all Pods belonging to that cluster (not the PVCs).
38
38
39
-
Status Field::
39
+
===== Status Field
40
40
41
41
Operators of the Stackable Data Platform create, manage and delete Kubernetes resources: in order to easily query the health state of the products - and react accordingly - Stackable Operators use several predefined condition types to capture different aspects of a product's availability.
42
42
See this xref:contributor:adr/ADR027-status[ADR] for more information.
43
43
44
-
Default / Custom Affinities::
44
+
===== Default / Custom Affinities
45
45
46
46
In Kubernetes there are different ways to influence how Pods are assigned to Nodes.
47
47
In some cases it makes sense to co-locate certain services that communicate a lot with each other, such as HBase regionservers with HDFS datanodes.
@@ -50,29 +50,29 @@ There may also be additional requirements e.g. placing important services - such
50
50
This release implements default affinities that should suffice for many scenarios out-of-the box, while also allowing for custom affinity rules at a role and/or role-group level.
51
51
See this xref:contributor:adr/ADR026-affinities.adoc[ADR] for more information.
52
52
53
-
Log Aggregation::
53
+
===== Log Aggregation
54
54
55
55
The logging framework (added to the platform in Release 23.1) offers a consistent custom resource configuration and a separate, persisted sink (defaulting to OpenSearch).
56
56
This has now been rolled out across all products.
57
57
See this xref:contributor:adr/adr025-logging_architecture[ADR] and this xref:concepts:logging.adoc[concepts page] for more information.
58
58
59
-
Service Type::
59
+
===== Service Type
60
60
61
61
The Service type can now be specified in all products.
62
62
This currently differentiates between the internal ClusterIP and the external NodePort and is forward compatible with the xref:listener-operator:listenerclass.adoc[ListenerClass] for the automatic exposure of Services via the Listener Operator.
63
63
This change is not backwards compatible with older platform releases.
64
64
For security reasons, the default is set to the cluster-internal (ClusterIP) ListenerClass.
65
65
A cluster can be exposed outside of Kubernetes by setting clusterConfig.listenerClass to external-unstable (NodePort) or external-stable (LoadBalancer).
66
66
67
-
New Versions::
67
+
===== New Versions
68
68
69
69
No new product versions are supported in this platform release.
70
70
71
-
Deprecated Versions::
71
+
===== Deprecated Versions
72
72
73
73
No product versions have been deprecated in this platform release.
74
74
75
-
Product features::
75
+
===== Product features
76
76
77
77
Additionally, there are some individual product features that are noteworthy:
0 commit comments