Skip to content

fix(docs): Airflow - specify default namespace #396

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
adwk67 merged 1 commit into from
Mar 17, 2026
Merged

fix(docs): Airflow - specify default namespace #396

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 5 additions & 6 deletions docs/modules/demos/pages/airflow-scheduled-job.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,13 +5,12 @@ Install this demo on an existing Kubernetes cluster:

[NOTE]
====
The namespace `airflow-demo` will be assumed in this guide.
It will be created if it doesn't exist.
The `default` namespace must be used for this demo.
====

[source,console]
----
$ stackablectl demo install airflow-scheduled-job -n airflow-demo
$ stackablectl demo install airflow-scheduled-job -n default
----

[WARNING]
Expand Down Expand Up @@ -175,7 +174,7 @@ We can use the kafka-producer script bundled with Kafka to write to this topic (

[source,bash]
----
kubectl exec -n airflow-demo kafka-broker-default-0 -c kafka -- bash -c \
kubectl exec -n default kafka-broker-default-0 -c kafka -- bash -c \
'echo "Hello World at: $(date)" | /stackable/kafka/bin/kafka-console-producer.sh \
--bootstrap-server $BOOTSTRAP_SERVER \
--topic test-topic \
Expand All @@ -187,7 +186,7 @@ You can do this by either displaying the pod logs directly (e.g. if you are usin

[source,bash]
----
kubectl logs -n airflow-demo airflow-triggerer-default-0 --tail=30
kubectl logs -n default airflow-triggerer-default-0 --tail=30
----

The logs show that our message was detected, triggering the job:
Expand Down Expand Up @@ -316,7 +315,7 @@ The patch can be applied like this:

[source,console]
----
kubectl patch airflowcluster airflow --type="merge" --patch-file stacks/airflow/patch_airflow.yaml -n airflow-demo
kubectl patch airflowcluster airflow --type="merge" --patch-file stacks/airflow/patch_airflow.yaml -n default
----

Wait for Airflow to come back up, and you should now see the generated DAGs.
Expand Down
Loading