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

Added flyte scheduler in helm #1374

Merged
merged 26 commits into from
Sep 25, 2021
Merged

Added flyte scheduler in helm #1374

merged 26 commits into from
Sep 25, 2021

Conversation

yindia
Copy link
Contributor

@yindia yindia commented Aug 25, 2021

Test:
Override helm values

workflow_scheduler:
  enabled: true
  type: native
 
flytescheduler:
  # -- Replicas count for Flyteadmin deployment
  replicaCount: 1
  image:
    # -- Docker image for Flyteadmin deployment
    repository: evalsocket/flytescheduler
    # -- Docker image tag
    tag: latest # FLYTEADMIN_TAG
    # -- Docker image pull policy
    pullPolicy: IfNotPresent

Install Flyte

helm install -n flyte -f values-sandbox.yaml --create-namespace flyte . 

Test:

  • if flytescheduler pre-check will wait for flyteadmin in the init container...It will only start after flyteadmin is healthy
  • If flyteadmin didn't start successfully then flytescheduler will retry and after retry exhaustion it will restart the pod
  • If flyteadmin goes down after flytescheduler init container success then pre-check will not responsible, it will be handle by scheduler retry

Not Tested:

  • Pre check with auth

Signed-off-by: Yuvraj [email protected]

yindia added 2 commits August 25, 2021 20:41
Signed-off-by: Yuvraj <[email protected]>
Signed-off-by: Yuvraj <[email protected]>
@yindia yindia changed the title [WIP] Added flyte scheduler in helm Added flyte scheduler in helm Aug 25, 2021
@yindia yindia marked this pull request as ready for review August 25, 2021 15:52
@yindia yindia requested a review from sbrunk August 25, 2021 15:56
Copy link
Contributor

@EngHabu EngHabu left a comment

Choose a reason for hiding this comment

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

We shouldn't merge this until we merge flytescheduler PR... otherwise, looks good!

charts/flyte/templates/common/secret-auth.yaml Outdated Show resolved Hide resolved
yindia added 4 commits August 31, 2021 11:36
Signed-off-by: Yuvraj <[email protected]>
Signed-off-by: Yuvraj <[email protected]>
Signed-off-by: Yuvraj <[email protected]>
@pmahindrakar-oss
Copy link
Contributor

We need to be able to scale admin and scheduler services separately.
The current changes will cause multiple scheduler instances if admin replicas are increased which we dont want

Signed-off-by: Yuvraj <[email protected]>
charts/flyte-core/templates/flytescheduler/configmap.yaml Outdated Show resolved Hide resolved
@@ -48,7 +48,7 @@ spec:
name: config-volume
- name: auth
secret:
secretName: flyte-propeller-auth
secretName: flyte-common-auth
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this a bug?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

no i moved it in a commen secret

charts/flyte-core/values-eks.yaml Show resolved Hide resolved
charts/flyte-core/values.yaml Outdated Show resolved Hide resolved
charts/flyte/templates/common/secret-auth.yaml Outdated Show resolved Hide resolved
Signed-off-by: Yuvraj <[email protected]>
Signed-off-by: Yuvraj <[email protected]>
Signed-off-by: Yuvraj <[email protected]>
@yindia yindia requested a review from EngHabu September 18, 2021 07:12
charts/flyte-core/templates/flytescheduler/configmap.yaml Outdated Show resolved Hide resolved
charts/flyte/templates/flytescheduler/configmap.yaml Outdated Show resolved Hide resolved
charts/flyte/values-eks.yaml Outdated Show resolved Hide resolved
charts/flyte/values.yaml Show resolved Hide resolved
Signed-off-by: Yuvraj <[email protected]>
@yindia yindia requested a review from EngHabu September 21, 2021 16:02
charts/flyte-core/values.yaml Outdated Show resolved Hide resolved
charts/flyte/values.yaml Show resolved Hide resolved
charts/flyte/values.yaml Outdated Show resolved Hide resolved
deployment/eks/flyte_helm_generated.yaml Outdated Show resolved Hide resolved
deployment/sandbox/flyte_helm_generated.yaml Outdated Show resolved Hide resolved
deployment/sandbox/flyte_helm_generated.yaml Outdated Show resolved Hide resolved
Signed-off-by: Yuvraj <[email protected]>
Signed-off-by: Yuvraj <[email protected]>
Signed-off-by: Yuvraj <[email protected]>
EngHabu
EngHabu previously approved these changes Sep 23, 2021
Copy link
Contributor

@EngHabu EngHabu left a comment

Choose a reason for hiding this comment

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

Just a couple of nits...

charts/flyte-core/values.yaml Outdated Show resolved Hide resolved
charts/flyte/values.yaml Outdated Show resolved Hide resolved
app.kubernetes.io/managed-by: Helm
spec:
initContainers:
- command:
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we not need to run migrations here too? this can be added in the future...

Copy link
Contributor Author

@yindia yindia Sep 24, 2021

Choose a reason for hiding this comment

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

No, currently flyteadmin will handle the migration...When we have a separate DB for flytescheduler then we can run migration here
CC: @pmahindrakar-oss

Copy link
Contributor

Choose a reason for hiding this comment

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

Hi @EngHabu , we are relying on the admin running the migration script for now but it can easily be decoupled to run as a separate init container for scheduler specific tables in the future

Signed-off-by: Yuvraj <[email protected]>
@pmahindrakar-oss pmahindrakar-oss merged commit e3f9211 into master Sep 25, 2021
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.

5 participants