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

Feature: k3s runtime support #3900

Closed
5 of 8 tasks
cuisongliu opened this issue Sep 11, 2023 · 13 comments
Closed
5 of 8 tasks

Feature: k3s runtime support #3900

cuisongliu opened this issue Sep 11, 2023 · 13 comments
Assignees
Labels
kind/feature New feature or request response-expired

Comments

@cuisongliu
Copy link
Collaborator

cuisongliu commented Sep 11, 2023

What is the problem this feature will solve?

If you have solution,please describe it

No response

What alternatives have you considered?

#2863

@cuisongliu cuisongliu added the kind/feature New feature or request label Sep 11, 2023
@cuisongliu cuisongliu self-assigned this Sep 11, 2023
@cuisongliu
Copy link
Collaborator Author

  1. reset 直接指定master和node无法reset 不执行脚本
  2. 删除节点后无法重加入节点 等6分钟都无法加入,
 balancer k3s-agent-load-balancer 127.0.0.1:6444 -> [apiserver.cluster.local:6443] [default: apiserver.cluster.local:6443]"
et CA certs: Get \"https://127.0.0.1:6444/cacerts\": read tcp 127.0.0.1:52942->127.0.0.1:6444: read: connection reset by peer"
et CA certs: Get \"https://127.0.0.1:6444/cacerts\": read tcp 127.0.0.1:16982->127.0.0.1:6444: read: connection reset by peer"
  1. endable 服务加超时处理

@sealos-ci-robot
Copy link
Member

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


  1. Reset cannot be reset by directly specifying master and node, and the script will not be executed.
  2. After deleting the node, you cannot rejoin the node. You cannot join the node after waiting for 6 minutes.
 balancer k3s-agent-load-balancer 127.0.0.1:6444 -> [apiserver.cluster.local:6443] [default: apiserver.cluster.local:6443]"
et CA certs: Get \"https://127.0.0.1:6444/cacerts\": read tcp 127.0.0.1:52942->127.0.0.1:6444: read: connection reset by peer"
et CA certs: Get \"https://127.0.0.1:6444/cacerts\": read tcp 127.0.0.1:16982->127.0.0.1:6444: read: connection reset by peer"
  1. Endable service plus timeout processing

@codering
Copy link

codering commented Oct 12, 2023

最新版本已经可以用k3s runtime 了吗?

@sealos-ci-robot
Copy link
Member

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


Is the latest version available for k3s runtime?

@cuisongliu
Copy link
Collaborator Author

最新版本已经可以用k3s runtime 了吗?

4.4的最新版支持,但是集群镜像需要更换一下。更换成 k3s:1.25-latest 。但是没有做全面的测试

@sealos-ci-robot
Copy link
Member

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


Is the latest version available for k3s runtime?

The latest version of 4.4 supports it, but the cluster image needs to be replaced. Replaced with k3s:1.25-latest. But no comprehensive testing has been done

Copy link

stale bot commented Dec 11, 2023

This issue has been automatically closed because we haven't heard back for more than 60 days, please reopen this issue if necessary.

@cuisongliu
Copy link
Collaborator Author

需要做测试

@stale stale bot removed the response-expired label Dec 12, 2023
@sealos-ci-robot
Copy link
Member

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


Need to do testing

@BanKnight
Copy link

需要做测试

什么时候做好测试呢?我想试下部署k3s版本了

@sealos-ci-robot
Copy link
Member

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


Need to do testing

When will the test be done? I want to try deploying the k3s version

Copy link

stale bot commented Feb 25, 2024

This issue has been automatically closed because we haven't heard back for more than 60 days, please reopen this issue if necessary.

@stale stale bot closed this as completed Apr 25, 2024
@cuisongliu cuisongliu reopened this May 5, 2024
@stale stale bot removed the response-expired label May 5, 2024
Copy link

stale bot commented Jul 5, 2024

This issue has been automatically closed because we haven't heard back for more than 60 days, please reopen this issue if necessary.

@stale stale bot closed this as completed Sep 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request response-expired
Projects
None yet
Development

No branches or pull requests

4 participants