-
Notifications
You must be signed in to change notification settings - Fork 89
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
Expose override in qhub-config.yaml for prefect #799
Labels
type: enhancement 💅🏼
New feature or request
Comments
Tested it and got the following resuts:
Tying to solve the folowing error:
|
Error solved and deplymen was suecessuf, simple test on qhub-config: prefect:
enabled: true
overrides:
prefect_agent:
prefectLabels: [dev, prod]
job:
resources:
requests:
memory: 20Gi Output on Prefec-agent service (by K9s): Environment:
│ PREFECT__CLOUD__AGENT__LABELS: ["dev","prod"] │
│ JOB_MEM_REQUEST: 20Gi |
This issue has been automatically marked as stale because there was no recent activity in 60 days. Remove the stale label or add a comment, otherwise, this issue will automatically be closed in 7 days if no further activity occurs. |
github-actions
bot
added
the
status: stale 🥖
Not up to date with the default branch - needs update
label
Nov 15, 2021
viniciusdc
removed
the
status: stale 🥖
Not up to date with the default branch - needs update
label
Nov 16, 2021
viniciusdc
changed the title
Remove local helm chart, provide overrides, and expose override in qhub-config.yaml for prefect
Expose override in qhub-config.yaml for prefect
Nov 16, 2021
Closed by #813 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Currently the prefect chart provided in QHub is too restrictive. Would like to provide the option for more flexible Prefect deployments while making the helm chart follow prefect more closely.
Acceptance Criteria
qhub-config.yaml
in prefect that allows user based overridesThe text was updated successfully, but these errors were encountered: