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

Add nb-culler cronjob #9

Merged
merged 1 commit into from
Feb 14, 2024
Merged

Add nb-culler cronjob #9

merged 1 commit into from
Feb 14, 2024

Conversation

DanNiESh
Copy link
Collaborator

@DanNiESh DanNiESh commented Feb 6, 2024

relevant issues: nerc-project/operations#404,
nerc-project/operations#387,
nerc-project/operations#337

In this PR, I didn't change the namespace from our testing namespace ope-rhods-testing-1fef2f to rhods-notebooks because we need to confirm that everything operates as expected before we proceed to apply this cronjob to rhods-notebooks.

cronjobs/nb-culler/cronjob.yaml Outdated Show resolved Hide resolved
cronjobs/nb-culler/cronjob.yaml Outdated Show resolved Hide resolved
cronjobs/nb-culler/cronjob.yaml Outdated Show resolved Hide resolved
@computate
Copy link
Member

Thanks for working hard on this @DanNiESh and @dystewart to ensure this culler cronjob doesn't affect every notebook. I'm following up with Professor Lance Galletti to identify the uptime constraints for his class as well.

@DanNiESh DanNiESh force-pushed the cronjob branch 4 times, most recently from 019764e to c7c9eb4 Compare February 8, 2024 18:57
Copy link
Member

@computate computate left a comment

Choose a reason for hiding this comment

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

Well done!

Copy link
Collaborator

@IsaiahStapleton IsaiahStapleton left a comment

Choose a reason for hiding this comment

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

Looks good

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.

4 participants