KubeFATE v1.5.0

By downloading, installing or using the software, you accept and agree to be bound by all of the terms and conditions of the LICENSE and DISCLAIMER.

Kubefate v1.5.0 supports the deployment of FATE 1.5.0 and FATE-Serving 2.0.0 with eggroll or spark as underlying computing back-end. It also includes other improvements, the details are as follow:

Docker Compose deployment

1. Simplifies the copy of deployment file in local machine.
2. Supports the deployment of single node Spark cluster.
3. Provides GUI client based on Jupyter Notebook, which is pre-installed with fate_client and other easy-to-use Python libraries ;
4. Shows more post-deployment information of FATE, including Fate-board and Jupyter Notebook.

K8s deployment

1. Supports Spark as underlying computing engine;
2. Provides GUI client based on Jupyter Notebook, which is pre-installed with fate_client and other easy-to-use Python libraries ;
3. Provides sample deployment YAML for fate, fate-serving, spark, eggroll and etc.

The deliverables include:

1. The KubeFATE Server Images v1.2.0;
2. The Docker Compose v1.5.0;
3. K8s deployment kits v1.5.0 (including KubeFATE CLI, charts and cluster charts examples);
4. The FATE v1.5.0 chart.

Please make sure KubeFATE CLI and Service have been updated to v1.2.0.

Note: If you upgrade the KubeFATE service instead of a new install, make sure to execute the SQL file v1.1.1-to-v1.2.0.sql located in folder ./k8s-deploy/sql/.

KubeFATE v1.4.5

By downloading, installing or using the software, you accept and agree to be bound by all of the terms and conditions of the LICENSE and DISCLAIMER.

1. KubeFATE v1.4.5 supports FATE v1.4.5
2. Add the feature of displaying cluster status
3. Documents for customizing cluster deployments
4. Some bugs fixes

KubeFATE v1.4.4

By downloading, installing or using the software, you accept and agree to be bound by all of the terms and conditions of the LICENSE and DISCLAIMER.

1. KubeFATE v1.4.4 supports FATE v1.4.4 and FATE-Serving v2.0.
2. Optimize the mirror download experience for Chinese users by adding 163 image repository:
   a. For docker-compose user, please refer to: https://github.com/FederatedAI/KubeFATE/tree/master/docker-deploy#set-up-a-local-registry-harbor-optional
   b. For Kubernetes user, please refer to: https://github.com/FederatedAI/KubeFATE/tree/master/docker-deploy#set-up-a-local-registry-harbor-optional
3. Refactor of Kubefate service and switch persistence backend from MongoDB to MySQL.
4. New features and bug fixes:
   a. Sub Job feature.
   b. Creation and checking of namespace.
   c. Log display configuration.
   d. Bugs of one cases where cluster deployment failed to show successful deployment
   e. Bugs of "Rename" problem
   f. Other bugs fixes

KubeFATE v1.4.3

By downloading, installing or using the software, you accept and agree to be bound by all of the terms and conditions of the LICENSE and DISCLAIMER.

KubeFATE v1.4.3 supports FATE v1.4.3, and enhances following features:

1. Upgrade FML_Manager to v0.5.0, which brings new programming experience with build pattern style;
2. Bug fix - sessionProcessorsPerNode setting no effect ;
3. Fix other minor bugs

NOTE
For Kubernetes user, due to KubeFATE has decoupled cluster configuration from KubeFATE service, to upgrade deployed cluster to v1.4.3, only changed the,

...
chartName: fate
chartVersion: v1.4.2
...

to

...
chartName: fate
chartVersion: v1.4.3
...

The fate-serving, KubeFATE CLI and CLI is same as v1.4.0: https://github.com/FederatedAI/KubeFATE/releases/tag/v1.4.0).

KubeFATE v1.4.2

By downloading, installing or using the software, you accept and agree to be bound by all of the terms and conditions of the LICENSE and DISCLAIMER.

KubeFATE v1.4.2 supports FATE v1.4.2, and enhance following features:

1. Update fml_manager to v0.4.0
2. Fix bugs

NOTE
For Kubernetes user, due to KubeFATE has decoupled cluster configuration from KubeFATE service, to upgrade deployed cluster to v1.4.2, only changed the,

...
chartName: fate
chartVersion: v1.4.1
...

to

...
chartName: fate
chartVersion: v1.4.2
...

The fate-serving, KubeFATE CLI and CLI is same as v1.4.0: https://github.com/FederatedAI/KubeFATE/releases/tag/v1.4.0).

KubeFATE v1.4.1

By downloading, installing or using the software, you accept and agree to be bound by all of the terms and conditions of the LICENSE and DISCLAIMER.

KubeFATE v1.4.1 supports FATE v1.4.1, and enhance following features:

1. Update fml_manager to v0.3.0 in client container (Jupyter Notebook), and add more examples;
2. Support updating configmap dynamically;
3. Fix bugs

NOTE
For Kubernetes user, due to KubeFATE has decoupled cluster configuration from KubeFATE service, to upgrade deployed cluster to v1.4.1, only changed the,

...
chartName: fate
chartVersion: v1.4.0
...

to

...
chartName: fate
chartVersion: v1.4.1
...

The KubeFATE CLI and CLI is same as v1.4.0

KubeFATE v1.4.0

By downloading, installing or using the software, you accept and agree to be bound by all of the terms and conditions of the LICENSE and DISCLAIMER.

KubeFATE v1.4.0 supports the deployment and management of below FATE components:

1. FATE v1.4.0;
2. FATE-Serving v1.2.4.

KubeFATE v1.4.0 feature highlights:

1. External MySQL and Redis support;
2. Directory structure refined for docker_deploy;
3. Experimental Jupyter Notebook Client support, which can submit job, manage data and model with Jupyter Notebook. The Client component is enabled by default in the deployment with docker-compose. For Kubernetes user, enable the feature by adding client module in cluster.yaml:

modules:
  - rollsite
  - clustermanager
  - nodemanager
  - mysql
  - python
  - client

The KubeFATE CLI and service version is upgraded to v1.0.3:

1. Enhanced the secure settings;
2. Fixed the token issue.

Helm chart has been upgraded to v1.4.0 supporting FATE v1.4.0. The Helm chart compatible with KubeFATE CLI and service >=v1.0.2. The original user can upgrade your cluster by changing chartVersion to upgrade your cluster:

chartVersion: v1.4.0

KubeFATE v1.3.0-a

By downloading, installing or using the software, you accept and agree to be bound by all of the terms and conditions of the LICENSE and DISCLAIMER.

KubeFATE v1.3.0-a supports the deployment and management of below FATE components:

1. FATE v1.3.0;
2. FATE-Serving v1.2.0

Comparing to v1.3.0, this release fixes minor bugs when deploying FATE to Kubernetes. The deliverables includes:

1. The KubeFATE release pack
2. The Docker Compose package
3. The FATE_1.3.0-a charts

This KubeFATE release includes KubeFATE CLI binary, the samples of config.yaml, kubefate.yaml, rbac-config.yaml and cluster.yaml.

Please use the v1.3.0-a chart for your deployment.

chartVersion: v1.3.0-a

More details, please refer to: FATE cluster configuration. If you are new to KubeFATE, please follow the tutorial

KubeFATE v1.3.0

By downloading, installing or using the software, you accept and agree to be bound by all of the terms and conditions of the LICENSE and DISCLAIMER.

KubeFATE v1.3.0 supports the deployment and management of below FATE components:

1. FATE v1.3.0;
2. FATE-Serving v1.2.0

KubeFATE provides two approaches to deploy FATE :

1 . Using Docker Compose :
This approach is simple and can be used for setting up environments of dev / test purposes. Get started from here: Install FATE by Docker Compose .

2 . Using Kubernetes (K8s) :
a) Since V1.2, Helm charts and shell scripts can be used to deploy FATE. Get started from here: K8s installation by scripts. Note: This method will be deprecated in future release.

b) In this release(V1.3), a new command line (CLI) of KubeFATE is introduced. It is currently a preview version and will be a preferred method to deploy FATE. Its major features are:

1. Provide a single executable binary (CLI) for initiating and managing FATE cluster;
2. Manage full life-cycle of FATE clusters : deploying a new cluster, querying an existing cluster, destroying a cluster and etc.;
3. Support customized deployment;
4. Support one KubeFATE service to manage multiple FATE deployments;
5. Provide cluster management service with RESTful APIs.

For more details, please refer to: KubeFATE Overview and KubeFATE-k8s-deploy .

The deliverables includes:

1. The KubeFATE release pack
2. The Docker Compose package
3. The FATE_1.3.0 charts

This KubeFATE release includes KubeFATE CLI binary, the samples of config.yaml, kubefate.yaml, rbac-config.yaml and cluster.yaml.

KubeFATE v1.2.0

1. Support FATE v1.2.0;
2. Optimize the deployment of Exchange;
3. Refine documents;
4. Some bug fixes