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.

Sign up for GitHub

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

Jump to bottom

[proposal] add cri v1 api to koord-runtime-proxy #1051

Closed
maaoBit opened this issue Feb 24, 2023 · 7 comments
Closed

[proposal] add cri v1 api to koord-runtime-proxy #1051

maaoBit opened this issue Feb 24, 2023 · 7 comments
Labels
kind/proposal Create a report to help us improve lifecycle/stale

Comments

@maaoBit
Copy link

maaoBit commented Feb 24, 2023

What is your proposal:
Koord-runtime-proxy support cri v1 api, and support v1alpha in parallel

Why is this needed:
According to kubernetes/kubernetes#110618, k8s v1.26 removed cri v1alpha2 support.
In order to run on k8s 1.26+, koord-runtime-proxy support cri v1 api.

Is there a suggested solution, if so, please add it:
@maaoBit maaoBit added the kind/proposal Create a report to help us improve label Feb 24, 2023
@maaoBit maaoBit mentioned this issue Feb 24, 2023
Closed
3 tasks
@stale
Copy link

stale bot commented May 25, 2023

This issue has been automatically marked as stale because it has not had recent activity.
This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the issue is closed
    You can:
  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Close this issue or PR with /close
    Thank you for your contributions.

@stale
Copy link

stale bot commented Jun 24, 2023

This issue has been automatically closed because it has not had recent activity.
This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the issue is closed
    You can:
  • Reopen this PR with /reopen
    Thank you for your contributions.

@stale stale bot closed this as completed Jun 24, 2023
@saintube saintube mentioned this issue Aug 14, 2023
Closed
@saintube saintube mentioned this issue Aug 26, 2023
Closed
@hormes
Copy link
Member

hormes commented Aug 28, 2023

/reopen

@koordinator-bot koordinator-bot bot reopened this Aug 28, 2023
@koordinator-bot
Copy link

@hormes: Reopened this issue.

In response to this:

/reopen

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/test-infra repository.

@hormes
Copy link
Member

hormes commented Aug 28, 2023 •
edited
Loading

Let me sort out the ideas, the support of cri-api api version:

version cri-api supported kubelet import
1.19 v1alpha2 v1alpha2
1.20 v1alpha2, v1 v1alpha2
1.21 v1alpha2, v1 v1alpha2
1.22 v1alpha2, v1 v1alpha2
1.23 v1alpha2, v1 v1
1.24 v1alpha2, v1 v1
1.25 v1alpha2, v1 v1
1.26 v1 v1

We try our best to be compatible with various usages, and transparently forward unsupported interfaces to the backend.

@stale stale bot removed the lifecycle/stale label Aug 28, 2023
@hormes hormes mentioned this issue Aug 29, 2023
Merged
@stale Stale
Copy link

stale bot commented Nov 27, 2023

This issue has been automatically marked as stale because it has not had recent activity.
This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the issue is closed
    You can:
  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Close this issue or PR with /close
    Thank you for your contributions.

@stale Stale
Copy link

stale bot commented Dec 27, 2023

This issue has been automatically closed because it has not had recent activity.
This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the issue is closed
    You can:
  • Reopen this PR with /reopen
    Thank you for your contributions.

@stale stale bot closed this as completed Dec 27, 2023
@saintube saintube mentioned this issue Aug 30, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/proposal Create a report to help us improve lifecycle/stale
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

runtime-proxy: support cri v1 api maaoBit/koordinator
2 participants
@hormes @maaoBit