fix(docs): Update getting-started script pre-25.7.0

[NickLarsenNZ]

• Use NiFi 2.4.0 (fix docs to remove the experimental marker)
• Fix jq query to use new output from stackablectl
• Update the getting_started guide to use the Listener address

Check and Update Getting Started Script

Part of stackabletech/issues#742

Note

During a Stackable release we need to check (and optionally update) the
getting-started scripts to ensure they still work after product and operator
updates.

# Some of the scripts are in a code/ subdirectory
# pushd docs/modules/superset/examples/getting_started
# pushd docs/modules/superset/examples/getting_started/code
pushd $(fd -td getting_started | grep examples); cd code 2>/dev/null || true

# Make a fresh cluster (~12 seconds)
kind delete cluster && kind create cluster
./getting_started.sh stackablectl

# Make a fresh cluster (~12 seconds)
kind delete cluster && kind create cluster
./getting_started.sh helm

popd

[NickLarsenNZ]

Successfully tested ./getting_started.sh helm:

Installing Operators with Helm
Pulled: oci.stackable.tech/sdp-charts/commons-operator:0.0.0-dev
Digest: sha256:a00b9869e04c5f361b610330e5a759f1826cb4a4ba4c4a406aa71bbf23d1f9a8
NAME: commons-operator
LAST DEPLOYED: Tue Jul 15 11:14:23 2025
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
Pulled: oci.stackable.tech/sdp-charts/secret-operator:0.0.0-dev
Digest: sha256:f0a7c4b8892682115ca480eab55d5477796c9fe1216a7b1574be1aa6c65742b1
NAME: secret-operator
LAST DEPLOYED: Tue Jul 15 11:14:32 2025
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
Pulled: oci.stackable.tech/sdp-charts/listener-operator:0.0.0-dev
Digest: sha256:0fc15aa38b1e4b78d241a76c47d7f01cb9161479bf06bc18ac539f6a3a5784e3
NAME: listener-operator
LAST DEPLOYED: Tue Jul 15 11:14:37 2025
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
Pulled: oci.stackable.tech/sdp-charts/zookeeper-operator:0.0.0-dev
Digest: sha256:7fc3451a1dc246a142dd826bb5b168f3971f00931f71539bfe04953fafea6bc4
NAME: zookeeper-operator
LAST DEPLOYED: Tue Jul 15 11:14:47 2025
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
Pulled: oci.stackable.tech/sdp-charts/nifi-operator:0.0.0-dev
Digest: sha256:b51f0dcccd3e39338ec0535078ae977147459b6a587fda9c8261af0b77f0fe06
NAME: nifi-operator
LAST DEPLOYED: Tue Jul 15 11:14:54 2025
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
Installing ZooKeeper
zookeepercluster.zookeeper.stackable.tech/simple-zk created
Create a ZNode
zookeeperznode.zookeeper.stackable.tech/simple-nifi-znode created
Awaiting ZooKeeper rollout finish
Waiting for 1 pods to be ready...
partitioned roll out complete: 1 new pods have been updated...
Create NiFi admin credentials
secret/simple-admin-credentials created
authenticationclass.authentication.stackable.tech/simple-nifi-users created
Create a NiFi instance
nificluster.nifi.stackable.tech/simple-nifi created
Awaiting NiFi rollout finish
pod/simple-nifi-node-default-0 condition met
Getting the NiFi endpoint with kubectl
Get first node address from Listener
NodeAddress: 172.18.0.2
Get HTTPS node port from Listener
NodePort: 31686
Create NiFi url
NiFi web interface: https://172.18.0.2:31686
Starting nifi tests
Getting NiFi credentials
Checking if NiFi is reachable at https://172.18.0.2:31686
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 172.18.0.2:31686...
* ALPN: curl offers h2,http/1.1
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
  0     0    0     0    0     0      0      0 --:--:--  0:00:16 --:--:--     0* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
{ [41 bytes data]
* TLSv1.3 (IN), TLS handshake, Request CERT (13):
{ [131 bytes data]
* TLSv1.3 (IN), TLS handshake, Certificate (11):
{ [1951 bytes data]
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
{ [264 bytes data]
* TLSv1.3 (IN), TLS handshake, Finished (20):
{ [52 bytes data]
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.3 (OUT), TLS handshake, Certificate (11):
} [8 bytes data]
* TLSv1.3 (OUT), TLS handshake, Finished (20):
} [52 bytes data]
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / x25519 / RSASSA-PSS
* ALPN: server accepted h2
* Server certificate:
*  subject: CN=generated certificate for pod
*  start date: Jul 15 09:10:30 2025 GMT
*  expire date: Jul 16 05:35:24 2025 GMT
*  issuer: CN=secret-operator self-signed
*  SSL certificate verify result: self-signed certificate in certificate chain (19), continuing anyway.
*   Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
* Connected to 172.18.0.2 (172.18.0.2) port 31686
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://172.18.0.2:31686/
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: 172.18.0.2:31686]
* [HTTP/2] [1] [:path: /]
* [HTTP/2] [1] [user-agent: curl/8.12.1]
* [HTTP/2] [1] [accept: */*]
} [5 bytes data]
> GET / HTTP/2
> Host: 172.18.0.2:31686
> User-Agent: curl/8.12.1
> Accept: */*
>
* Request completely sent off
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [2211 bytes data]
< HTTP/2 302
< date: Tue, 15 Jul 2025 09:17:12 GMT
< content-security-policy: frame-ancestors 'self'
< x-content-type-options: nosniff
< x-frame-options: SAMEORIGIN
< x-xss-protection: 1; mode=block
< strict-transport-security: max-age=31540000
< location: /nifi/
< content-length: 0
* Ignoring the response-body
* setting size while ignoring
<
  0     0    0     0    0     0      0      0 --:--:--  0:00:16 --:--:--     0
* Connection #0 to host 172.18.0.2 left intact
* Issue another request to this URL: 'https://172.18.0.2:31686/nifi/'
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [50 bytes data]
* Re-using existing connection with host 172.18.0.2
* [HTTP/2] [3] OPENED stream for https://172.18.0.2:31686/nifi/
* [HTTP/2] [3] [:method: GET]
* [HTTP/2] [3] [:scheme: https]
* [HTTP/2] [3] [:authority: 172.18.0.2:31686]
* [HTTP/2] [3] [:path: /nifi/]
* [HTTP/2] [3] [user-agent: curl/8.12.1]
* [HTTP/2] [3] [accept: */*]
} [5 bytes data]
> GET /nifi/ HTTP/2
> Host: 172.18.0.2:31686
> User-Agent: curl/8.12.1
> Accept: */*
>
* Request completely sent off
{ [5 bytes data]
< HTTP/2 200
< date: Tue, 15 Jul 2025 09:17:12 GMT
< content-security-policy: frame-ancestors 'self'
< x-content-type-options: nosniff
< x-frame-options: SAMEORIGIN
< x-xss-protection: 1; mode=block
< strict-transport-security: max-age=31540000
< last-modified: Tue, 15 Jul 2025 09:17:11 GMT
< content-length: 28277
< content-type: text/html
< accept-ranges: bytes
<
{ [16295 bytes data]
100 28277  100 28277    0     0   1734      0  0:00:16  0:00:16 --:--:--  1734
* Connection #0 to host 172.18.0.2 left intact
Getting NiFi JWT token
Checking if NiFi cluster is ready (1/15) ... not ready yet!
Retrying in 10 seconds...
Checking if NiFi cluster is ready (2/15) ... not ready yet!
Retrying in 10 seconds...
Checking if NiFi cluster is ready (3/15) ... not ready yet!
Retrying in 10 seconds...
Checking if NiFi cluster is ready (4/15) ... not ready yet!
Retrying in 10 seconds...
Checking if NiFi cluster is ready (5/15) ... not ready yet!
Retrying in 10 seconds...
Checking if NiFi cluster is ready (6/15) ... not ready yet!
Retrying in 10 seconds...
Checking if NiFi cluster is ready (7/15) ... not ready yet!
Retrying in 10 seconds...
Checking if NiFi cluster is ready (8/15) ... yes
Checking if NiFi cluster has 1 nodes ... yes
NiFi cluster started up successfully!

[sbernauer]

LGTM. thanks!
I like that it's now much shorter.
Pls still feel free to switch back to multi-step endpoint gathering