Use ECI in Knative services

Method 1: Directly create an ECI for a Knative service

• If the virtual:kubelet label is not added to a namespace, you can create an Elastic Container Instance (ECI) by setting the following configurations when you create resource objects for Knative services.
  • Specify the ECI specification in an annotation.
  • Specify virtual-kubelet in the nodeAffinity parameter.
  • Specify virtual-kubelet.io/provider in the tolerations parameter.
  Set the parameters based on the following template:

  apiVersion: serving.knative.dev/v1
  kind: Service
  metadata:
    name: helloworld-go
    namespace: vk
  spec:
    template:
      metadata:
        annotations:
          k8s.aliyun.com/eci-use-specs: "2-4Gi"
      spec:
        affinity:
          nodeAffinity:
            requiredDuringSchedulingIgnoredDuringExecution:
              nodeSelectorTerms:
              - matchExpressions:
                - key: type
                  operator: In
                  values: 
                  - virtual-kubelet   
        tolerations:
        - key: virtual-kubelet.io/provider
          operator: Exists                
        containers:
        - env:
          - name: TARGET
            value: "Knative"
          image: registry.cn-hangzhou.aliyuncs.com/knative-sample/helloworld-go:73fbdd56

• If the virtual-kubelet label is added to the namespace, you only need to specify the ECI specification in the annotation to directly create an ECI.

  kubectl label namespace vk virtual-node-affinity-injection=enabled

  Set the parameters based on the following template:

  apiVersion: serving.knative.dev/v1
  kind: Service
  metadata:
    name: helloworld-go
    namespace: vk
  spec:
    template:
      metadata:
        annotations:
          k8s.aliyun.com/eci-use-specs: "2-4Gi"
      spec:         
        containers:
        - env:
          - name: TARGET
            value: "Knative"
          image: registry.cn-hangzhou.aliyuncs.com/knative-sample/helloworld-go:73fbdd56

Method 2: Specify an ECS instance to automatically create an ECI for a Knative service

You can specify a labelled ECS instance in the nodeAffinity parameter to automatically create an ECI for a Knative service. This way, the pod is deployed in both the ECS instance and ECI.

1. Attach a label to the ECS instance. For more information, see Manage labels.
   The resource-role:ecs label is attached to the ECS instance in this example.
2. In the resource object template, set the nodeAffinity parameter.
   Specify the labelled ECS instance and virtual-kubelet in the nodeAffinity parameter.

   Set the parameters based on the following template:

   apiVersion: serving.knative.dev/v1
   kind: Service
   metadata:
     name: helloworld-go
   spec:
     template:
       metadata:
         annotations:
           k8s.aliyun.com/eci-use-specs: "2-4Gi"
      spec:
         containerConcurrency: 10
         affinity:
           nodeAffinity:
             requiredDuringSchedulingIgnoredDuringExecution:
               nodeSelectorTerms:
               - matchExpressions:
                 - key: resource-role
                   operator: In
                   values:
                   - ecs
               - matchExpressions:
                 - key: type
                   operator: In
                   values: 
                   - virtual-kubelet
         tolerations:
         - key: virtual-kubelet.io/provider
           operator: Exists                 
         containers:
         - env:
           - name: TARGET
             value: "Knative"
           image: registry.cn-hangzhou.aliyuncs.com/knative-sample/helloworld-go:73fbdd56