-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
K8s code executor #3419
K8s code executor #3419
Conversation
@microsoft-github-policy-service agree company="Samsung SDS" |
@questcollector hey thanks for the PR! We will get back to you in a few days. |
This PR is against AutoGen 0.2. AutoGen 0.2 has been moved to the 0.2 branch. Please rebase your PR on the 0.2 branch or update it to work with the new AutoGen 0.4 that is now in main. |
da2097e
to
dd3154b
Compare
I rebased it on 0.2 branch. I'll update kubernetes pod commandline code executor to align to autogen 0.4 as new PR👌 |
@questcollector - thanks! well done. I think there are just a couple of pre-commit checks to fix to green the CI |
we're happy to take this for 0.2, for 0.4 how do the guidelines seem to you (https://microsoft.github.io/autogen/dev/user-guide/extensions-user-guide/index.html#creating-your-own-community-extension) @questcollector ? |
oops 😅 I applied pre-commit. Thank you. |
Looks like there are still CI issues here that need to be fixed before this can be merged. (I reverted a seemingly unrelated change to gitignore) |
Oh sorry for extra works, I fixed test code. |
Why are these changes needed?
Using docker container for code executor is inconvenient when utilizing autogen through a kubernetes cluster.
Code executor using Kubernetes pod can address security concerns by leveraging Kubernetes RBAC policies.
New feature
Test cases
Documentation
LICENSE
Related issue number
#2967
Checks