Merge branch 'main' into fix/airflow-scheduled-job

Author: maltesander

demos/signal-processing/create-nifi-ingestion-job.yaml

@@ -74,7 +74,7 @@ data:
     import urllib3
 
     # As of 2022-08-29 we cant use "https://nifi:8443" here because <h2>The request contained an invalid host header [<code>nifi:8443</code>] in the request [<code>/nifi-api</code>]. Check for request manipulation or third-party intercept.</h2>
-    ENDPOINT = f"https://nifi-node-default-0.nifi-node-default.{os.environ['NAMESPACE']}.svc.cluster.local:8443" # For local testing / developing replace it, afterwards change back to f"https://nifi-node-default-0.nifi-node-default.{os.environ['NAMESPACE']}.svc.cluster.local:8443"
+    ENDPOINT = f"https://nifi-node-default-0.nifi-node-default-headless.{os.environ['NAMESPACE']}.svc.cluster.local:8443" # You can replace this for local development but don't forget to revert it after.
     USERNAME = "admin"
     PASSWORD = open("/nifi-admin-credentials/admin").read()
 

docs/modules/demos/pages/jupyterhub-keycloak.adoc

@@ -146,9 +146,11 @@ proxy-648bf7f45b-62vqg       1/1     Running     0          56m
 
 ----
 
-The `proxy` Pod has an associated `proxy-public` service with a statically-defined port (31095), exposed with type NodePort. The `keycloak` Pod has a Service called `keycloak` with a fixed port (31093) of type NodePort as well.
-In order to reach the JupyterHub web interface, navigate to this service.
+The `proxy` Pod has an associated `proxy-public` service with a statically-defined port (31095), exposed with type NodePort.
+The `keycloak` Pod has a Service called `keycloak` with a fixed port (31093) of type NodePort as well.
 The node port IP can be found in the ConfigMap `keycloak-address` (written by the Keycloak Deployment as it starts up).
+Both the Keycloak and the JupyterHub web interface can be accessed via this address, on ports 31093 and 31095 respectively.
+
 On Kind this can be any node - not necessarily the one where the proxy Pod is running.
 This is due to the way in which Docker networking is used within the cluster.
 On other clusters it will be necessary to use the exact Node on which the proxy is running.

stacks/signal-processing/nifi.yaml

@@ -11,7 +11,6 @@ spec:
     custom: oci.stackable.tech/demos/nifi:2.4.0-postgresql
     # pullPolicy: IfNotPresent
   clusterConfig:
-    listenerClass: external-unstable
     authentication:
       - authenticationClass: nifi-users
     sensitiveProperties:
@@ -36,6 +35,8 @@ spec:
             capacity: "4Gi"
           stateRepo:
             capacity: "1Gi"
+    roleConfig:
+      listenerClass: external-unstable
     roleGroups:
       default:
         replicas: 1

stacks/trino-iceberg/trino.yaml

@@ -7,7 +7,6 @@ spec:
   image:
     productVersion: "476"
   clusterConfig:
-    listenerClass: external-unstable
     catalogLabelSelector:
       matchLabels:
         trino: trino
@@ -29,6 +28,8 @@ spec:
     roleGroups:
       default:
         replicas: 1
+    roleConfig:
+      listenerClass: external-unstable
   workers:
     config:
       resources: