Skip to content

Conversation

@avilches
Copy link
Contributor

@avilches avilches commented Dec 4, 2025

Summary

The K8s deployment generates the images from all the services (gateway, scheduler and Ray base image of functions). When the Ray image is generated, it installs Qiskit Serverless from the client folder. This means that every time we deploy the services, the latest version of the client in main branch is used, which may include unfinished changes.

This PR changes how the Ray base image for functions is generated. Instead of copying the client, it just installs it from pip. This will allow deploying the services at any time without worrying about the client state.

@avilches avilches requested a review from a team as a code owner December 4, 2025 14:03
@avilches avilches self-assigned this Dec 4, 2025
@avilches avilches requested a review from Tansito December 4, 2025 14:04
Copy link
Member

@Tansito Tansito left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should also review our current deployment process before merge this as it affects how we are doing the releases.


RUN pip install -r requirements.txt --no-cache-dir &&\
pip install . --no-cache-dir &&\
RUN pip install --no-cache-dir qiskit-serverless &&\
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we use the version to have control over what qiskit-serverless we are installing?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I was thinking to do something similar as we are already doing with DYNAMIC_DEPENDENCIES_FILE. But then I realize what will be the point to not use the latest version published. Right now, we are using the latest version not published yet.

@Tansito Tansito marked this pull request as draft December 4, 2025 14:39
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.

2 participants