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

Publish a dedicated image to run kjobctl slurm init container #6

Open
mbobrovskyi opened this issue Dec 3, 2024 · 5 comments
Open
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@mbobrovskyi
Copy link
Contributor

What would you like to be added:

To simplify the development of the slurm support in kjobctl. Also, not to use outdated images.
The new image could be generic for kjobctl , or specific for the slurm support (maybe kjobctl-slurm), to be discussed.

Why is this needed:

The discussion kubernetes-sigs/kueue#3072 (comment).
The available images in registry.k8s.io (see https://explore.ggcr.dev/?repo=registry.k8s.io) are very limited in tooling, or old. We could not find a new image which would have: bash and nslookup (with bind-tools).

@mbobrovskyi
Copy link
Contributor Author

/kind feature

@k8s-ci-robot
Copy link
Contributor

@mbobrovskyi: The label(s) kind/feature cannot be applied, because the repository doesn't have them.

In response to this:

/kind feature

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@mbobrovskyi
Copy link
Contributor Author

/kind feature

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Dec 6, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 6, 2025
@mbobrovskyi
Copy link
Contributor Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 6, 2025
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

No branches or pull requests

3 participants