#Install KServe

#Prerequisites

Before installing Alauda Build of KServe, you need to ensure the following dependencies are installed:

#Required Dependencies

#Installation Notes

1. Required Dependencies: All required dependencies must be installed before installing Alauda Build of KServe.
2. GIE Integration: GIE is bundled and enabled by default. If your environment already has GIE installed separately, set gie.builtIn to false in the operator configuration to disable the built-in installation.

#Upload Operator

Download the Alauda Build of KServe Operator installation file (e.g., kserve-operator.ALL.xxxx.tgz).

Use the violet command to publish it to the platform repository:

violet push --platform-address=<platform-access-address> --platform-username=<platform-admin> --platform-password=<platform-admin-password> kserve-operator.ALL.xxxx.tgz

#Install Operator

In Administrator view:

1. Click Marketplace / OperatorHub.

2. At the top of the console, from the Cluster dropdown list, select the destination cluster where you want to install the KServe Operator.

3. Search for and select Alauda Build of KServe, then click Install.

   Install Alauda Build of KServe window will pop up.

4. Leave Channel unchanged.

5. Check whether the Version matches the Alauda Build of KServe version you want to install.

6. Leave Installation Location unchanged, it should be kserve-operator by default.

7. Select Manual for Upgrade Strategy.

8. Click Install.

#Verification

Confirm that the Alauda Build of KServe tile shows one of the following states:

• Installing: installation is in progress; wait for this to change to Installed.
• Installed: installation is complete.

#Create KServe Instance

After the operator is installed, create a KServe custom resource to deploy the KServe instance.

Switch to YAML view and apply the following configuration, then adjust the callout fields for your environment:

apiVersion: components.aml.dev/v1alpha1
kind: KServe
metadata:
  name: default-kserve
spec:
  namespace: kserve
  values:
    global:
      clusterName: <cluster-name>
      deployFlavor: single-node
      platformAddress: <platform-address>
      preset:
        GIE:
          enabled: true
        envoy_ai_gateway:
          port: 1063
          service: ai-gateway-controller
        envoy_gateway:
          create_instance: true
          deploy_type: ControllerNamespace
          instance_name: aieg
          sa_namespace: envoy-gateway-system
          service_account: envoy-gateway
        kserve_gateway:
          enabled: true
          gateway_class: ""
          name: kserve-ingress-gateway
          namespace: kserve
          port: 80
      registry:
        address: <registry-address>
    kserve:
      controller:
        deploymentMode: Knative
        gateway:
          domain: <inference-domain>
      storage:
        caBundleConfigMapName: aml-global-ca-bundle

#Verification

Check the status of the KServe resource:

kubectl get kserve default-kserve -n kserve-operator

The instance is ready when the status shows DEPLOYED: True.

#Envoy Gateway Configuration

#Envoy AI Gateway Configuration

#KServe Gateway Configuration

#GIE (gateway-api-inference-extension) Configuration

#Upgrading Alauda Build of KServe

1. Upload the new version of the Alauda Build of KServe operator package using the violet tool.
2. Go to the Administrator -> Marketplace -> OperatorHub page, find Alauda Build of KServe, and click Confirm to apply the new version.

#Verification

After upgrading, confirm that the Alauda Build of KServe tile shows Installed and verify the KServe instance status:

kubectl get kserve default-kserve -n kserve-operator