Image Agent Demo
This document provides detailed steps for running the Image Agent proof-of-concept (PoC) demo.
In this demo, we will use the Rossoctl UI to import and deploy both the Image Service Agent and the Image Tool. During deployment, we'll configure the A2A protocol for managing agent calls and MCP for enabling communication between the agent and the image tool.
Once deployed, we will query the agent using a natural language prompt. The agent will then invoke the tool and return the image data as a response.
This demo illustrates how Rossoctl manages the lifecycle of all required components: agents, tools, protocols, and runtime infrastructure.
Here's a breakdown of the sections:
- In Set Up, you'll run a script to rebuild and roll out the UI image
- In Import New Agent, you'll build and deploy the
image_serviceagent. - In Import New Tool, you'll build and deploy the
image_tooltool. - In Validate the Deployment, you'll verify that all components are running and operational.
- In Chat with the Image Agent, you'll interact with the agent and confirm it responds correctly with randomly generated images.
Prerequisites: Ensure you've completed the Rossoctl platform setup as described in the Installation section.
You should also open the Agent Platform Demo Dashboard as instructed in the Connect to the Rossoctl UI section.
Import New Agent
To deploy the Image Agent:
- Navigate to Import New Agent in the Rossoctl UI.
- In the Select Namespace to Deploy Agent drop-down, choose the
<namespace>where you'd like to deploy the agent. (These namespaces are defined in your.envfile.) - Under Environment Variables, configure LLM settings using one of these methods:
- Click Import .env File and import
.env.openaior.env.ollamafrom the agent examples repo, or - Manually add env vars:
LLM_API_BASE,LLM_API_KEY, andLLM_MODEL(see Using Local Models for values)
- Click Import .env File and import
- In the Agent Source Repository URL field, use the default:
https://github.com/rossoctl/examples
Or use a custom repository accessible using the GitHub ID specified in your
.envfile. - For Git Branch or Tag, use the default
mainbranch (or select another as needed). - Set Protocol to
a2a. - Under Specify Source Subfolder:
- Click
Select from examples - Choose:
a2a/image_service
- Click
- Click Build & Deploy New Agent to deploy.
Note: The ollama environmental variable set specifies llama3.2:3b-instruct-fp16 as the default model. To download the model, run ollama pull llama3.2:3b-instruct-fp16. Please ensure an Ollama server is running in a separate terminal via ollama serve.
Import New Tool
To deploy the Image Tool using Shipwright:
- Navigate to Import New Tool in the UI.
- Select the same
<namespace>as used for the agent. - Select "Build from source" as the deployment method.
- Use the same source repository: https://github.com/rossoctl/examples
- Choose the
mainbranch or your preferred branch. - Set Select Protocol to
streamable_http. - Under Specify Source Subfolder:
- Select:
mcp/image_tool
- Select:
- Click Build & Deploy New Tool to deploy.
You will be redirected to a Build Progress page where you can monitor the Shipwright build. Once the build succeeds, the Deployment and Service for the tool will be created automatically.
Validate The Deployment
Depending on your hosting environment, it may take some time for the agent and tool deployments to complete.
To verify that both the agent and tool are running:
-
Open a terminal and connect to your Kubernetes cluster.
-
Use the namespace you selected during deployment to check the status of the pods:
installer$ kubectl get po -n <your-ns>NAME READY STATUS RESTARTS AGEimage-service-8bb4644fc-4d65d 1/1 Running 0 1mimage-tool-5bb675dd7c-ccmlp 1/1 Running 0 1m -
Tail the logs to ensure both services have started successfully. For the agent:
installer$ kubectl logs -f deployment/image-service -n <your-ns>Defaulted container "image-service" out of: image-service, rossoctl-client-registration (init)INFO: Started server process [18]INFO: Waiting for application startup.INFO: Application startup complete.INFO: Uvicorn running on http://0.0.0.0:8000 (Press CTRL+C to quit)For the tool:
installer$ kubectl logs -f deployment/image-tool -n <your-ns>Defaulted container "image-tool" out of: image-tool, rossoctl-client-registration (init)INFO: Started server process [19]INFO: Waiting for application startup.INFO: Application startup complete.INFO: Uvicorn running on http://0.0.0.0:8000 (Press CTRL+C to quit) -
Once you see the logs indicating that both services are up and running, you're ready to proceed to Chat with the Image Agent.
Chat with the Image Agent
Once the deployment is complete, you can run the demo:
-
Navigate to the Agent Catalog in the Rossoctl UI.
-
Select the same
<namespace>used during the agent deployment. -
Under Available Agents in
, select image-serviceand click View Details. -
Scroll to the bottom of the page. In the input field labeled Say something to the agent..., enter:
Give me a 200x200 image -
You will see the Agent Thinking... message. Depending on the speed of your hosting environment, the agent will return a image response.
-
You can tail the log files (as shown in the Validate the Deployment section) to observe the interaction between the agent and the tool in real time.
If you encounter any errors, check the Troubleshooting section.
Cleanup
To cleanup the agents and tools in the UI, go to the Agent Catalog and Tool Catalog
respectively and click the Delete button next to each.
You can also manually remove them from the cluster:
installer$ kubectl delete deployment image-service image-tool -n <your-ns>
installer$ kubectl delete service image-service image-tool -n <your-ns>