SUSE 徽标 SUSE 联邦徽标 退出 SUSE 联邦  >
客户中心
帐户
您好
更新您的帐户 注销
登录 创建帐户 更新您的帐户
中文(简体)  
语言 Deutsch English Español Français 中文(简体) 日本語 한국어 Português (Brasil)
购买
查看购物车
SUSE Logo Exit SUSE Federal  >
Shop SUSECON 24 Customer
联邦解决方案
产品
解决方案
支持和服务
合作伙伴
社区
关于
联系方式
免费下载
 
 
 
 
Back
Back
关键业务型 Linux 运行平台
  • SUSE Linux Enterprise Server

    提高可用性、效率和创新性

  • SUSE Linux Enterprise Server for SAP Applications

    适用于 SAP 应用程序和数据库的经过优化且具有恢复能力的平台

  • SUSE Manager

    面向企业 DevOps 和 IT Operations 的开放源代码基础设施管理解决方案

  • SUSE Liberty Linux

    Mixed Linux environment support

企业级容器管理平台
  • Rancher Prime

    Kubernetes 管理平台

  • Harvester

    Kubernetes 上的虚拟化

  • Longhorn

    Cloud Native Storage

  • NeuVector Prime

    零信任容器安全

边缘计算平台
  • K3S

    专为边缘环境打造的轻量级 Kubernetes 发行版

  • SUSE Linux Enterprise Micro

    超可靠、无法篡改的 Linux 操作系统

  • Real Time

    减少系统延迟并加快响应速度

所有产品
  • 运行 SAP 运行 SAP
  • 公共云 公共云
  • 安全 安全
Back
解决方案
  • 混合云 IT
    业务关键型 Linux

    运行并保护云和本地工作负载

  • 运行SAP解决方案
    运行SAP解决方案

    以最可靠、最容易管理的方式运行SAP解决方案

  • 企业级容器管理
    企业级容器管理

    编制云原生应用程序

  • 边缘创新
    边缘创新

    将基本产品——从汽车到医疗设备——转化为智能产品,并提供优质的客户体验

  • 人工智能
    人工智能

    运行企业专用 GenAI 解决方案

  • SUSE Public Cloud
    SUSE Public Cloud

    在 Amazon EC2 或 Microsoft Azure 上运行

  • 安全
    安全

    保护您的数字化企业

行业
  • 汽车
  • 电信
  • 银行和金融服务
  • 医疗保健
  • 制造
  • 零售
  • 技术和软件
  • 联邦
  • 医药
  • 能源
Back
支持服务
  • 产品支持订阅

    SUSE 客户中心

  • 高级支持服务

    直接联系指定的高级团队

  • 长期服务支持

    保持现有产品版本

  • 续订您的支持订阅

    Partners with cloud providers

  • AWS
  • Microsoft Azure
  • Google
SUSE 全球服务
  • 咨询服务
  • 培训和认证
  • 优质技术咨询服务
支持资源
  • SUSE 支持用户指南
  • 增补程序与更新
  • 产品文档
  • 知识库
  • 产品支持生命周期
  • Package Hub

    SUSE Linux Enterprise Server 社区软件包

  • 驱动程序搜索
  • 支持论坛
  • 开发人员服务
  • beta 测试计划
  • 安全
Back
合作伙伴
  • 合作伙伴计划
  • 寻找合作伙伴
  • 成为合作伙伴
  • SUSE 合作伙伴门户登录
Back
社区
  • SUSE 博客
  • SUSE 论坛
  • 开放源代码贡献
  • openSUSE.org
Back
关于
  • 关于我们
  • 领导团队
  • 招贤纳士
  • 新闻编辑室
  • 成功案例
  • 投资者关系
  • 社会影响
  • SUSE 徽标和品牌
  • 活动 & 网络研讨会
  • 商店
JUMP TO
Support Matrix

RANCHER 2.9.X

  • 2.9.1

RANCHER 2.8.X

  • 2.8.7
  • 2.8.6
  • 2.8.5
  • 2.8.4
  • 2.8.3
  • 2.8.2
  • 2.8.1

RANCHER 2.7.X

  • 2.7.15
  • 2.7.14
  • 2.7.13
  • 2.7.12
  • 2.7.11
  • 2.7.10
  • 2.7.9
  • 2.7.6
  • 2.7.5
  • 2.7.4
  • 2.7.3
  • 2.7.2
  • 2.7.1
  • 2.7.0

RANCHER 2.6.X

  • 2.6.14
  • 2.6.13
  • 2.6.12
  • 2.6.11
  • 2.6.10
  • 2.6.9
  • 2.6.8
  • 2.6.7
  • 2.6.6
  • 2.6.5
  • 2.6.4
  • 2.6.3
  • 2.6.2
  • 2.6.1
  • 2.6.0

RANCHER 2.5.X

  • 2.5.16
  • 2.5.15
  • 2.5.14
  • 2.5.13
  • 2.5.12
  • 2.5.11
  • 2.5.10
  • 2.5.9
  • 2.5.8
  • 2.5.7
  • 2.5.6
  • 2.5.5
  • 2.5.4
  • 2.5.3
  • 2.5.2
  • 2.5.1
  • 2.5.0

RANCHER 2.4.X

  • 2.4.18
  • 2.4.17
  • 2.4.15
  • 2.4.14
  • 2.4.13
  • 2.4.12
  • 2.4.11
  • 2.4.10
  • 2.4.9
  • 2.4.8
  • 2.4.7
  • 2.4.6
  • 2.4.5
  • 2.4.4
  • 2.4.3
  • 2.4.2

RKE 1

  • 1.30
  • 1.29
  • 1.28
  • 1.27
  • 1.26
  • 1.25
  • 1.24
  • 1.23

RKE 2

  • 1.31
  • 1.30
  • 1.29
  • 1.28
  • 1.27
  • 1.26
  • 1.25
  • 1.24
  • 1.23

K3S

  • 1.31
  • 1.30
  • 1.29
  • 1.28
  • 1.27
  • 1.26
  • 1.25
  • 1.24
  • 1.23

HARVESTER

  • 1.3.x
  • 1.2.x
  • 1.1.x
  • 1.0.x

LONGHORN

  • 1.6.x
  • 1.5.x
  • 1.4.x

NEUVECTOR

  • NeuVector

Longhorn v1.6.x

Product Lifecycle & Support Phases

All Longhorn releases will go through three stages: In Development, Latest, and then finally Stable. Please ensure you do not upgrade your production cluster to anything other than a listed Stable version. Use Latest versions for test purposes only.

All versions listed below have an EOL date of 01 August 2025, one year and six months after the release of the first stable version.

ReleaseReleased
1.6.2 - Stable23 May 2024
1.6.1 - Stable29 Mar 2024
1.6.001 Feb 2024 
PHASESDESCRIPTION
GA to EOM

Upon General Availability of all major and minor releases, products are fully supported and maintained until the End of Maintenance date. Support entails general troubleshooting of a specific issue to isolate potential causes. Issue resolution is pursued through one or more of the following: 

  • Applying configuration changes.
  • Upgrade recommendation to an existing newer version of product.
  • Code-level maintenance in the form of product updates; typically, results in a maintenance release, which is a newer version of product that was not existing at the time the issue was encountered.
EOM to EOL

After a product release reaches its End of Maintenance date, no further code-level maintenance will be provided, except for critical security-related fixes on a request basis. Product will continue to be supported until it reaches End of Life, in the form of: 

  • General troubleshooting of a specific issue to isolate potential causes.
  • Upgrade recommendation to an existing newer version of product - Issue resolution limited to applying configuration changes and/or an upgrade recommendation to an existing newer version of product.
EOL

Once a product release reaches its End of Life date, the customer may continue to use the product within the terms of product licensing agreement.

- Support Plans from SUSE do not apply to product releases past their EOL date.

 

Scope of Support

A Longhorn support entitlement includes Longhorn components and the following operating systems and platform architectures. Furthermore, Longhorn is supported to run on any certified Kubernetes distributions and versions, such as the actively supported versions of RKE2 and K3s. Experimental or Preview features are not eligible for support.

Verified Operating Systems

The following Linux OS distributions and versions have been verified during release testing. However, this does not imply that Longhorn exclusively supports these distributions. Essentially, Longhorn should function well on any certified Kubernetes cluster running on Linux nodes with a wide range of general-purpose operating systems, as well as verified container-optimized operating systems like SLE Micro. 

OPERATING SYSTEMVERIFIED VERSIONS
Oracle Linux9.3
RHEL9.3
Rocky Linux9.3
SLE Micro5.5
SLES15 SP5
Ubuntu22.04
Talos 1.6.1

Supported Platform Architectures

  • AMD64
  • ARM64

Hardware Requirements

To get a Longhorn cluster up and running with the supported features, the following minimum hardware is required. For other best practices, please refer to the official document at https://longhorn.io/docs/1.6.0/best-practices/. If any preview or experimental features require additional resource requirements, please check the corresponding document to adjust the setup.

TypeRequirements
Cluster3 Nodes for running Longhorn components
CPU4 CPUs per node
Memory4 GiB per node
Disk PerformanceLocal SSD/NVMe disks are highly recommended for optimal storage performance of volumes
Network Card10Gbps Ethernet


 

SUSE 徽标
  • 招贤纳士
  • 法律
  • 反奴隶制声明
  • 反奴隶制声明
  • 关于
  • 您的通讯自选设置
  • 联系方式
  • 与我们联系
  • WeChat
WeChat QR
支持: Open a Support Case
© ©SUSE,保留所有权利 Cookie Settings 隐私与 Cookie 策略 and Cookie Policy