Run the demo in one kind cluster and publish the connector image#8
Closed
dejanzele wants to merge 1 commit into
Closed
Run the demo in one kind cluster and publish the connector image#8dejanzele wants to merge 1 commit into
dejanzele wants to merge 1 commit into
Conversation
4ccc6e6 to
80e3cd7
Compare
Signed-off-by: Dejan Zele Pejchev <pejcev.dejan@gmail.com>
80e3cd7 to
6b9ac66
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 fromdeploy/Dockerfile).deploy/kubernetes/connector.yamlruns it as a Deployment and Service that the backend routesarmadatasks to.setup.shdeploys it into the demo cluster, anddeploy/README.mdcovers running it against your own backend.Quickstart
Start Armada with the armada-operator quickstart (
make kind-all+armadactl create queue flyte), rundemo/setup.sh, thenexamples/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 atlocalhost:5001/v2through a same-origin sidecar proxy in the console pod, and Armada's Lookout shows the job atlocalhost:30000.Removed
deploy/app.py— theflyte.deploy(ConnectorEnvironment)deploy path, superseded bydeploy/kubernetes/connector.yaml(plain manifest, published image). No test depended on it, anddeploy/README.mdanddocs/getting-started.mdnow point at the manifest.c0) and thehost.docker.internalwiring from the demo. The connector runs in-cluster and the backend reaches it over cluster DNS.cp311-abi3-macosx_10_12_x86_64), so it loads under an x86_64 interpreter too.Validated end to end:
demo/setup.shthenexamples/hello.pyprintshello armada, from an Armada pod, and the run renders in the Flyte console.🤖 Generated with Claude Code