Skip to content

KubeFATE v1.3.0
Compare
Choose a tag to compare
@LaynePeng LaynePeng released this 06 Mar 11:50
· 496 commits to master since this release
v1.3.0
0f227ad
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

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.

Assets 5
Loading