Skip to content
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]Support deploying vineyard cluster independently and deploy the engines on called #2710

Merged
merged 1 commit into from
Jun 2, 2023

Commits on Jun 1, 2023

  1. * Deploy the engines when the session calls the function of creating …

    …engine instances.
    
    * Deploy the vineyard deployment if not exist.
    * Add a new option for KubernetesLauncher to deploy the engines in the eager mode or lazy mode.
    * Split the create_engine_instances into two steps.
    - Allocate the engine instances.
    - Distribute the relevant process to the engine instances.
    * Add a new pytest on kubernetes to test the lazy mode.
    * Add a new label for engine pods to indicate the specific engine.
    * Set the engine_selector of all engine kubernetes resources.
    * Create different engine statefulset based on object_id for gae and gle.
    * Delete all engine kubernetes resources based on engine_selector for gae and gie.
    * Bump up the upload-artifact to v3
    
    Signed-off-by: Ye Cao <caoye.cao@alibaba-inc.com>
    dashanji committed Jun 1, 2023
    Configuration menu
    Copy the full SHA
    13dda85 View commit details
    Browse the repository at this point in the history