Skip to content

Run the demo in one kind cluster and publish the connector image#8

Closed
dejanzele wants to merge 1 commit into
mainfrom
polish-enduser-docs
Closed

Run the demo in one kind cluster and publish the connector image#8
dejanzele wants to merge 1 commit into
mainfrom
polish-enduser-docs

Conversation

@dejanzele

@dejanzele dejanzele commented Jul 9, 2026

Copy link
Copy Markdown
Member

The demo now runs entirely in one kind cluster: Armada (via the armada-operator quickstart), the Flyte 2 backend, and the connector. The client and browser reach the API and console over port-forwards, and every hop between components is cluster DNS. A Flyte task submits through the in-cluster connector to in-cluster Armada, runs as an Armada job, and the run renders in the Flyte console.

Connector image

The connector is published as dpejcev/armada-flyte-connector (multi-arch, built from deploy/Dockerfile). deploy/kubernetes/connector.yaml runs it as a Deployment and Service that the backend routes armada tasks to. setup.sh deploys it into the demo cluster, and deploy/README.md covers running it against your own backend.

Quickstart

Start Armada with the armada-operator quickstart (make kind-all + armadactl create queue flyte), run demo/setup.sh, then examples/hello.py. The happy path needs no environment variables: the cluster name, images, connector endpoint, blob store, and example endpoints all default to their in-cluster values. The Flyte console serves the run graph at localhost:5001/v2 through a same-origin sidecar proxy in the console pod, and Armada's Lookout shows the job at localhost:30000.

Removed

  • deploy/app.py — the flyte.deploy(ConnectorEnvironment) deploy path, superseded by deploy/kubernetes/connector.yaml (plain manifest, published image). No test depended on it, and deploy/README.md and docs/getting-started.md now point at the manifest.
  • The host-run connector (c0) and the host.docker.internal wiring from the demo. The connector runs in-cluster and the backend reaches it over cluster DNS.
  • The "x86_64 Python cannot load obstore" warning in the install docs. obstore ships a macOS x86_64 wheel (cp311-abi3-macosx_10_12_x86_64), so it loads under an x86_64 interpreter too.

Validated end to end: demo/setup.sh then examples/hello.py prints hello armada, from an Armada pod, and the run renders in the Flyte console.

🤖 Generated with Claude Code

@dejanzele dejanzele force-pushed the polish-enduser-docs branch from 4ccc6e6 to 80e3cd7 Compare July 10, 2026 12:32
@dejanzele dejanzele changed the title Make the demo Flyte UI work and guide the end-user path from hello to the DAG Run the demo in one kind cluster and publish the connector image Jul 10, 2026
Signed-off-by: Dejan Zele Pejchev <pejcev.dejan@gmail.com>
@dejanzele dejanzele force-pushed the polish-enduser-docs branch from 80e3cd7 to 6b9ac66 Compare July 10, 2026 12:56
@dejanzele

Copy link
Copy Markdown
Member Author

Superseded by the split into #9 (CI + connector image), #10 (Gang scheduling), and #11 (local devbox). Merge order: #9, then #10 and #11.

@dejanzele dejanzele closed this Jul 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant