cheyang
/
fluid
mirror of https://github.com/fluid-cloudnative/fluid.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Prepare release 0.9 (#3249) 

* Prepare release 0.9, To #48332556

Signed-off-by: cheyang <cheyang@163.com>

* Prepare release 0.9, To #48332556

Signed-off-by: cheyang <cheyang@163.com>

* Prepare release 0.9, To #48332556

Signed-off-by: cheyang <cheyang@163.com>

---------

Signed-off-by: cheyang <cheyang@163.com>
This commit is contained in:
cheyang 2023-05-24 20:07:27 +08:00 committed by GitHub
parent 4c782561d8
commit 39fb3dbc6d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
7 changed files with 153 additions and 51 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

75
CHANGELOG.md
View File

@ -1,5 +1,79 @@
# Fluid Release Notes
## v0.9.0
### Breaking Changes
- Change matching pod requests mode of webhook from namespaceSelector to objectSelector
### Features
- Add thinRuntime to simplify integration with third-party storage systems
- Addon component for Fluid's open source CubeFS, NFS
- Support for accessing data across namespaces
- Support for subDataset
- Native acceleration system EFCRuntime for distributed file systems NFS, GPFS
- Support dataMigrate for data migration operations (currently only supported by JuiceFSRuntime)
- Add customizable configuration for cache cleanup timeout and maximum retry times, Webhook timeout limits
- Add Dataload configuration for ImagePullSecrets, node affinity
- RBAC permission reduction
- Upgrade to golang 1.18
- Support for installing Fluid via Helm Repo
### Refactoring
- Use data operation framework to construct data migrate, load, backup behaviors
### Bug Fix
- [JindoRuntime should support configurable env variables](https://github.com/fluid-cloudnative/fluid/issues/3154)
- [Could not set nodeAffinity in dataset](https://github.com/fluid-cloudnative/fluid/issues/2772)
- [Runtime helm release stuck in "pending-install" status](https://github.com/fluid-cloudnative/fluid/issues/2764)
- [CSI failed to recover FUSE mount point for AlluxioRuntime ](https://github.com/fluid-cloudnative/fluid/issues/2719)
- [[JuiceFS] FUSE pod scheduled failed because of conflict port](https://github.com/fluid-cloudnative/fluid/issues/2668)
- [Fluid csi on rke2 k8s(1.22) use mount output empty,it caused app pod not work](https://github.com/fluid-cloudnative/fluid/issues/2613)
### Runtime Upgrade
- AlluxioRuntime is upgrade from v2.8.2 to v2.9.1
- JindoRuntime is upgraded from from 4.5.1 to 4.6.7
- JuicefsRuntime is upgraded from v1.0.0 to v1.0.4
## v0.8.0
### Features
- Lifecycle management of Serverless Job with fluid sidecar support
- Enabling Runtime Controller on demand
- Arm64 support with JuicefsRuntime
- Container Network with short-circuit read support
- Leader election support for Controllers and Webhook
- Automatic CRD upgrader
- Restrict Pod scheduling to dataset cache nodes
- Tens of thousands of nodes support
- Image pull secrets support
- GCS support for Alluxio Runtime
### Refactorings
- Port Allocation with different strategies: bitmap and random
### Bug Fix
- [Runtime cannot complete deletion when restarting controller](https://github.com/fluid-cloudnative/fluid/issues/1970)
- [Pod update failed with fluid webhook injection enabled](https://github.com/fluid-cloudnative/fluid/issues/2053)
- [Unhandled exception in gopkg.in/yaml.v3](https://github.com/fluid-cloudnative/fluid/issues/1869)
- [Webhook failed to load root certificates: unable to parse bytes as PEM block](https://github.com/fluid-cloudnative/fluid/issues/1399)
- [Plugin delete the csi socket when restarting unexpectly](https://github.com/fluid-cloudnative/fluid/issues/2088)
### Runtime Upgrade
- AlluxioRuntime is upgrade from v2.7.2 to v2.8
- JindoRuntime is upgraded from Jindo Engine to JindoFSX Engine, and the version is from 3.8 to 4.5.1
- JuiceRuntime is upgraded from v0.11.0 to v1.0.0
## v0.7.0
### Breaking Changes
@ -25,6 +99,7 @@
- Fix “[Failed to delete dataload when target dataset is removed](https://github.com/fluid-cloudnative/fluid/issues/1419)”
- Fix “[node-driver-registrar will not receive any volume umount in subdirectories of kubelet-dir](https://github.com/fluid-cloudnative/fluid/issues/1048)”
## v0.6.0
### Features

1
README-zh_CN.md
View File

@ -14,6 +14,7 @@
|![更新](static/bell-outline-badge.svg) 最新进展：|
|------------------|
|May. 24th, 2023. Fluid v0.9.0 **发布**! 添加thinRuntime以简化与第三方存储系统的集成，跨命名空间访问数据，支持子数据集，新的数据操作，如数据迁移，分布式文件系统的本地加速系统EFCRuntime等等。详情参见 [CHANGELOG](CHANGELOG.md)。|
|Sep. 03th, 2022. Fluid v0.8.0 **发布**! 提供一系列新功能，包括基于Fluid边车支持的Serverlesss作业生命周期管理，按需启动Runtime controller，自动化CRD更新, 严格的pod与数据集节点的调度机制， JuicefsRuntime的Arm64支持, Alluxio Runtime的GCS支持等等，详情参见 [CHANGELOG](CHANGELOG.md)。|
|Mar. 16th, 2021. Fluid v0.5.0 **发布**! 提供一系列新功能，包括提供数据集缓存的在线弹性扩缩容，元数据备份与恢复，Fuse全局模式部署等，详情参见 [CHANGELOG](CHANGELOG.md)。|
|Nov. 6th, 2020. Fluid v0.4.0 **发布**! 提供一系列新功能和修复上一版本的遗留问题，包括提供主动的数据预热，详情参见 [CHANGELOG](CHANGELOG.md)。|

1
README.md
View File

@ -27,6 +27,7 @@ English | [简体中文](./README-zh_CN.md)
| ![notification](static/bell-outline-badge.svg) What is NEW! |
| ------------------------------------------------------------ |
| May. 24th, 2023. Fluid v0.9.0 is **RELEASED**! It provides various new features, such as adding thinRuntime to simplify integration with third-party storage systems, access data across namespaces, subDataset support, new data Operation like dataMigrate, native acceleration system EFCRuntime for distributed file systems, and so on. Please check the [CHANGELOG](CHANGELOG.md) for details. |
| Sep. 03th, 2022. Fluid v0.8.0 is **RELEASED**! It provides various new features, such as Lifecycle management of Serverless Job with fluid sidecar support, Enable runtime controller on demand, Automatic CRD upgrader, Restrict pod scheduling to dataset cache nodes, Arm64 support with JuicefsRuntime, GCS support for Alluxio Runtime, and so on. Please check the [CHANGELOG](CHANGELOG.md) for details. |
| Mar. 02th, 2022. Fluid v0.7.0 is **RELEASED**! It provides various new features, such as Fuse sidecar auto injection for all the runtimes (suitable for serverless environment), Fuse auto recovery and upgrade, lazy fuse mount mode, support JuiceFS cache runtime and so on. Please check the [CHANGELOG](CHANGELOG.md) for details. |
| Aug. 11th, 2021. Fluid v0.6.0 is **RELEASED**! It provides various new features, such as dataset cache autoscaling and cronscaling, dataset cache aware Pod scheduling, HA support for cache Runtime. Please check the [CHANGELOG](CHANGELOG.md) for details. |

2
charts/fluid/fluid/Chart.yaml
View File

@ -18,7 +18,7 @@ version: 0.9.0
# This is the version number of the application being deployed. This version number should be
# incremented each time you make changes to the application.
appVersion: 0.9.0-0f7d87c
appVersion: 0.9.0-37e17c6
home: https://github.com/fluid-cloudnative/fluid
keywords:
- category:data

22
charts/fluid/fluid/values.yaml
View File

@ -4,7 +4,7 @@
workdir: /tmp
crdUpgrade:
image: fluidcloudnative/fluid-crd-upgrader:v0.9.0-0f7d87c
image: fluidcloudnative/fluid-crd-upgrader:v0.9.0-37e17c6
## if unspecified, will use built-in variable `.Release.Namespace`.
namespace: fluid-system
@ -15,7 +15,7 @@ image:
dataset:
replicas: 1
controller:
image: fluidcloudnative/dataset-controller:v0.9.0-0f7d87c
image: fluidcloudnative/dataset-controller:v0.9.0-37e17c6
csi:
featureGates: "FuseRecovery=false"
@ -24,7 +24,7 @@ csi:
registrar:
image: fluidcloudnative/csi-node-driver-registrar:v2.3.0
plugins:
image: fluidcloudnative/fluid-csi:v0.9.0-0f7d87c
image: fluidcloudnative/fluid-csi:v0.9.0-37e17c6
kubelet:
kubeConfigFile: /etc/kubernetes/kubelet.conf
certDir: /var/lib/kubelet/pki
@ -44,7 +44,7 @@ runtime:
init:
image: fluidcloudnative/init-users:v0.9.0
controller:
image: fluidcloudnative/alluxioruntime-controller:v0.9.0-0f7d87c
image: fluidcloudnative/alluxioruntime-controller:v0.9.0-37e17c6
runtime:
image: alluxio/alluxio-dev:2.9.0
fuse:
@ -62,7 +62,7 @@ runtime:
fuse:
image: registry.cn-shanghai.aliyuncs.com/jindofs/jindo-fuse:4.6.7
controller:
image: fluidcloudnative/jindoruntime-controller:v0.9.0-0f7d87c
image: fluidcloudnative/jindoruntime-controller:v0.9.0-37e17c6
init:
portCheck:
enabled: false
@ -76,7 +76,7 @@ runtime:
init:
image: fluidcloudnative/init-users:v0.9.0
controller:
image: fluidcloudnative/goosefsruntime-controller:v0.9.0-0f7d87c
image: fluidcloudnative/goosefsruntime-controller:v0.9.0-37e17c6
runtime:
image: ccr.ccs.tencentyun.com/qcloud/goosefs:v1.2.0
fuse:
@ -86,19 +86,19 @@ runtime:
enabled: false
runtimeWorkers: 3
controller:
image: fluidcloudnative/juicefsruntime-controller:v0.9.0-0f7d87c
image: fluidcloudnative/juicefsruntime-controller:v0.9.0-37e17c6
fuse:
image: juicedata/juicefs-fuse:v1.0.4-4.9.2
thin:
replicas: 1
enabled: false
controller:
image: fluidcloudnative/thinruntime-controller:v0.9.0-0f7d87c
image: fluidcloudnative/thinruntime-controller:v0.9.0-37e17c6
efc:
replicas: 1
enabled: false
controller:
image: fluidcloudnative/efcruntime-controller:v0.9.0-0f7d87c
image: fluidcloudnative/efcruntime-controller:v0.9.0-37e17c6
imagePullPolicy: Always
init:
image: registry.cn-zhangjiakou.aliyuncs.com/nascache/init-alifuse:v1.2.2-19dcee9
@ -111,7 +111,7 @@ runtime:
webhook:
enabled: true
image: fluidcloudnative/fluid-webhook:v0.9.0-0f7d87c
image: fluidcloudnative/fluid-webhook:v0.9.0-37e17c6
replicas: 1
timeoutSeconds: 15
reinvocationPolicy: IfNeeded
@ -120,4 +120,4 @@ fluidapp:
enabled: true
replicas: 1
controller:
image: fluidcloudnative/application-controller:v0.9.0-0f7d87c
image: fluidcloudnative/application-controller:v0.9.0-37e17c6

51
docs/en/userguide/install.md
View File

@ -27,12 +27,20 @@ Create namespace:
$ kubectl create ns fluid-system
```
Add Fluid repository to Helm repos and keep it up-to-date
```shell
$ helm repo add fluid https://fluid-cloudnative.github.io/charts
$ helm repo update
```
Install Fluid with:
```shell
$ helm install fluid fluid.tgz
$ helm install fluid fluid/fluid
NAME: fluid
LAST DEPLOYED: Fri Sep 2 19:03:56 2022
LAST DEPLOYED: Wed May 24 18:17:16 2023
NAMESPACE: default
STATUS: deployed
REVISION: 1
@ -44,7 +52,7 @@ TEST SUITE: None
> The general format of the `helm install` command is like: `helm install <RELEASE_NAME> <SOURCE>`. In the above command, the first `fluid` means the release name, and the second `fluid` specified the path to the helm chart, i.e. the directory just unpacked.
### Upgrade Fluid to the latest version(v0.8) with Helm
### Upgrade Fluid to the latest version with Helm
If you have installed an older version of Fluid before, you can use Helm to upgrade it.
Before upgrading, it is recommended to ensure that all components in the AlluxioRuntime resource object have been started completely, which is similar to the following state:
@ -61,7 +69,7 @@ hbase-worker-rznd5 2/2 Running 0 9h
upgrade fluid：
```shell
$ helm upgrade fluid fluid/
$ helm upgrade fluid fluid/fluid
Release "fluid" has been upgraded. Happy Helming!
NAME: fluid
LAST DEPLOYED: Fri Sep 2 18:54:18 2022
@ -73,7 +81,7 @@ TEST SUITE: None
> For Kubernetes version lower than v1.17(included), please use `helm install --set runtime.criticalFusePod=false fluid fluid.tgz`
> We recommend you to update Fluid v0.8 from v0.7. If you have an older version, our suggestion is to reinstall it to ensure everything works fine.
> We recommend you to update Fluid latest version from v0.7. If you have an older version, our suggestion is to reinstall it to ensure everything works fine.
### Check Status of Component
@ -81,26 +89,31 @@ TEST SUITE: None
```shell
$ kubectl get crd | grep data.fluid.io
alluxioruntimes.data.fluid.io 2022-06-28T02:43:52Z
databackups.data.fluid.io 2022-06-28T02:43:52Z
dataloads.data.fluid.io 2022-06-28T02:43:52Z
datasets.data.fluid.io 2022-06-28T02:43:52Z
goosefsruntimes.data.fluid.io 2022-06-28T02:43:52Z
jindoruntimes.data.fluid.io 2022-06-28T02:43:52Z
juicefsruntimes.data.fluid.io 2022-06-28T02:43:52Z
alluxioruntimes.data.fluid.io 2023-05-24T10:14:47Z
databackups.data.fluid.io 2023-05-24T10:14:47Z
dataloads.data.fluid.io 2023-05-24T10:14:47Z
datamigrates.data.fluid.io 2023-05-24T10:28:11Z
datasets.data.fluid.io 2023-05-24T10:14:47Z
efcruntimes.data.fluid.io 2023-05-24T10:28:12Z
goosefsruntimes.data.fluid.io 2023-05-24T10:14:47Z
jindoruntimes.data.fluid.io 2023-05-24T10:14:48Z
juicefsruntimes.data.fluid.io 2023-05-24T10:14:48Z
thinruntimeprofiles.data.fluid.io 2023-05-24T10:28:16Z
thinruntimes.data.fluid.io 2023-05-24T10:28:16Z
```
**Check the status of pods:**
```shell
$ kubectl get pod -n fluid-system
NAME READY STATUS RESTARTS AGE
csi-nodeplugin-fluid-g6ggh 2/2 Running 0 6m53s
csi-nodeplugin-fluid-tnj5r 2/2 Running 0 5m50s
dataset-controller-5f56cc4f97-2lfqt 1/1 Running 0 6m54s
fluid-crds-upgrade-0.8.0-aa7fdca--1-gtpt9 0/1 Completed 0 7m23s
fluid-webhook-7d8c586f59-mxkwz 1/1 Running 0 6m54s
fluidapp-controller-86f5bfc4c5-ct25p 1/1 Running 0 6m54s
NAME READY STATUS RESTARTS AGE
csi-nodeplugin-fluid-2scs9 2/2 Running 0 50s
csi-nodeplugin-fluid-7vflb 2/2 Running 0 20s
csi-nodeplugin-fluid-f9xfv 2/2 Running 0 33s
dataset-controller-686d9d9cd6-gk6m6 1/1 Running 0 50s
fluid-crds-upgrade-0.9.0-37e17c6-fp4mm 0/1 Completed 0 74s
fluid-webhook-5bc9dfb9d8-hdvhk 1/1 Running 0 50s
fluidapp-controller-6d4cbdcd88-z7l4c 1/1 Running 0 50s
```
If the Pod status is as shown above, then Fluid is installed on your Kubernetes cluster successfully!

52
docs/zh/userguide/install.md
View File

@ -28,12 +28,19 @@
$ kubectl create ns fluid-system
```
为您本地Helm仓库添加并且更新“fluid”源到最新版本
```shell
$ helm repo add fluid https://fluid-cloudnative.github.io/charts
$ helm repo update
```
安装Fluid：
```shell
$ helm install fluid fluid.tgz
$ helm install fluid fluid/fluid
NAME: fluid
LAST DEPLOYED: Fri Sep 2 19:03:56 2022
LAST DEPLOYED: Wed May 24 18:17:16 2023
NAMESPACE: default
STATUS: deployed
REVISION: 1
@ -44,7 +51,7 @@ TEST SUITE: None
> `helm install`命令的一般格式是`helm install <RELEASE_NAME> <SOURCE>`，在上面的命令中，第一个`fluid`指定了安装的release名字，这可以自行更改，第二个`fluid.tgz`指定了helm chart所在路径。
### 使用Helm将Fluid更新到最新版本(v0.8)
### 使用Helm将Fluid更新到最新版本
如果您此前已经安装过旧版本的Fluid，可以使用Helm进行更新。
更新前，建议确保各Runtime资源对象中的各个组件已经顺利启动完成，也就是类似以下状态：
@ -61,10 +68,10 @@ hbase-worker-rznd5 2/2 Running 0 9h
更新：
```shell
$ helm upgrade fluid fluid/
$ helm upgrade fluid fluid/fluid
Release "fluid" has been upgraded. Happy Helming!
NAME: fluid
LAST DEPLOYED: Fri Sep 2 18:54:18 2022
LAST DEPLOYED: Wed May 24 18:27:54 2023
NAMESPACE: default
STATUS: deployed
REVISION: 2
@ -73,7 +80,7 @@ TEST SUITE: None
> 对于Kubernetes v1.17及以下环境，请使用`helm upgrade --set runtime.criticalFusePod=false fluid fluid/`
> 建议您从v0.7升级到最新版本v0.8。如果您安装的是更旧版本的Fluid，建议重新进行安装。
> 建议您从v0.7升级到最新版本。如果您安装的是更旧版本的Fluid，建议重新进行安装。
### 检查各组件状态
@ -81,26 +88,31 @@ TEST SUITE: None
```shell
$ kubectl get crd | grep data.fluid.io
alluxioruntimes.data.fluid.io 2022-06-28T02:43:52Z
databackups.data.fluid.io 2022-06-28T02:43:52Z
dataloads.data.fluid.io 2022-06-28T02:43:52Z
datasets.data.fluid.io 2022-06-28T02:43:52Z
goosefsruntimes.data.fluid.io 2022-06-28T02:43:52Z
jindoruntimes.data.fluid.io 2022-06-28T02:43:52Z
juicefsruntimes.data.fluid.io 2022-06-28T02:43:52Z
alluxioruntimes.data.fluid.io 2023-05-24T10:14:47Z
databackups.data.fluid.io 2023-05-24T10:14:47Z
dataloads.data.fluid.io 2023-05-24T10:14:47Z
datamigrates.data.fluid.io 2023-05-24T10:28:11Z
datasets.data.fluid.io 2023-05-24T10:14:47Z
efcruntimes.data.fluid.io 2023-05-24T10:28:12Z
goosefsruntimes.data.fluid.io 2023-05-24T10:14:47Z
jindoruntimes.data.fluid.io 2023-05-24T10:14:48Z
juicefsruntimes.data.fluid.io 2023-05-24T10:14:48Z
thinruntimeprofiles.data.fluid.io 2023-05-24T10:28:16Z
thinruntimes.data.fluid.io 2023-05-24T10:28:16Z
```
**查看各Pod的状态:**
```shell
$ kubectl get pod -n fluid-system
NAME READY STATUS RESTARTS AGE
csi-nodeplugin-fluid-g6ggh 2/2 Running 0 6m53s
csi-nodeplugin-fluid-tnj5r 2/2 Running 0 5m50s
dataset-controller-5f56cc4f97-2lfqt 1/1 Running 0 6m54s
fluid-crds-upgrade-0.8.0-aa7fdca--1-gtpt9 0/1 Completed 0 7m23s
fluid-webhook-7d8c586f59-mxkwz 1/1 Running 0 6m54s
fluidapp-controller-86f5bfc4c5-ct25p 1/1 Running 0 6m54s
NAME READY STATUS RESTARTS AGE
csi-nodeplugin-fluid-2scs9 2/2 Running 0 50s
csi-nodeplugin-fluid-7vflb 2/2 Running 0 20s
csi-nodeplugin-fluid-f9xfv 2/2 Running 0 33s
dataset-controller-686d9d9cd6-gk6m6 1/1 Running 0 50s
fluid-crds-upgrade-0.9.0-37e17c6-fp4mm 0/1 Completed 0 74s
fluid-webhook-5bc9dfb9d8-hdvhk 1/1 Running 0 50s
fluidapp-controller-6d4cbdcd88-z7l4c 1/1 Running 0 50s
```
如果Pod状态如上所示，那么Fluid就可以正常使用了！