Skip to content

replace k8s.exec with an RPC client-server #204

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.

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

Closed
wants to merge 28 commits into from

Conversation

isegall-da
Copy link

@isegall-da isegall-da commented Feb 12, 2025

k8s.exec is not reliable enough for long operations, and often leads to the callback not being called and the runner hanging.

@isegall-da isegall-da requested a review from a team as a code owner February 12, 2025 19:10
@nikola-jokic
Copy link
Contributor

Hey @isegall-da,

What is the purpose of this PR?

@isegall-da
Copy link
Author

I'm sorry, did not mean to upstream this (yet ?).
This PR replaces the k8s.exec operation for executing steps on the workflow pod with an RPC client-server that is more reliable and resistant e.g. to network disconnects, as we have been experiencing issues with that exec call. Having said that, I will close this PR for now. Anybody interested is welcome to take a look at the fork instead.

@isegall-da isegall-da closed this Feb 13, 2025
@isegall-da isegall-da changed the title Isegall/rpc replace k8s.exec with an RPC client-server Feb 13, 2025
@nikola-jokic
Copy link
Contributor

No problem! ☺️

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