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

Allow usage of plain Pod owned by integrations that are disabled #2481

Closed
3 tasks
alculquicondor opened this issue Jun 26, 2024 · 1 comment · Fixed by #2493
Closed
3 tasks

Allow usage of plain Pod owned by integrations that are disabled #2481

alculquicondor opened this issue Jun 26, 2024 · 1 comment · Fixed by #2493
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@alculquicondor
Copy link
Contributor

What would you like to be added:

Allow Pods to be managed by the pod integration if they are owned by a job integration that is disabled.

The current check is only for whether an integration exists, regardless of whether it's enabled.

Why is this needed:

Use cases of elastic jobs (such as RayCluster) that don't require atomicity can be served via pod integration.

Completion requirements:

This enhancement requires the following artifacts:

  • Design doc
  • API change
  • Docs update

The artifacts should be linked in subsequent comments.

@alculquicondor alculquicondor added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 26, 2024
@alculquicondor
Copy link
Contributor Author

/assign @trasc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants