文章目錄
說明
OpenShift Serverless Operator爲無服務器應用提供提供了Knative Serving的運行環境。需要以下兩步就可以在OpenShift上運行Knative應用:安裝所需的Operator和配置Knative Serving運行環境。
客戶端環境
從以下地址下載對應環境的OpenShift Client和Knative Client,然後將oc和kn配置到PATH中。
- https://mirror.openshift.com/pub/openshift-v4/clients/oc/4.3/
- https://mirror.openshift.com/pub/openshift-v4/clients/serverless/latest/
環境配置
我們可以用OpenShift控制檯或OpenShift命令行創建Knative及其所需的運行環境。下面分別介紹這兩種方法。
通過OpenShift Console實現
安裝OpenShift Serverless Operator
注意:通過OpenShift Console安裝OpenShift Serverless Operator時候,OpenShift會自動安裝OpenShift Serverless Operator所依賴的Service Mesh Opeator,因此Operator的安裝過程非常簡單。
- 用集羣管理員登錄OpenShift Console。
- 在Administrator視圖中進入Operators->OperatorHub,然後找到“OpenShift Serverless Operator”,點擊進入,最後在右滑窗口中接受所有缺省配置一直到完成即可。
- 完後上一步後,可以在控制檯中進入任意一個項目(例如default項目),可以在Operators->Installed Operators中看到以下Operators。此時就完成了OpenShift Serverless Operator安裝。
創建Knative Serving應用運行環境
Knative Serving提供了Serverless應用的支撐運行環境。Knative Serving必須運行在knative-serving項目中。
- 創建knative-serving項目。
$ oc new-project knative-serving
- 切換到knative-serving項目,再次進入Operators->Installed Operators,然後進入OpenShift Serverless Operator的配置。
- 在Overview頁面中點擊Knative Serving區域的Create Instance鏈接。
- 在Create KnativeServing界面中接受缺省配置,然後點擊Create。
- 然後進入名爲knative-serving的KnativeServing配置。需要等一段時間,直到下圖中4個狀態全部爲True,此時就成功創建了Knative Serving環境。
- 可以切換到knative-serving項目的Developer視圖,可以以下6個Deployment。
創建Knative Serving應用運行環境
- 創建knative-serving.yaml文件,內容爲以下部分:
apiVersion: v1
kind: Namespace
metadata:
name: knative-serving
---
apiVersion: operator.knative.dev/v1alpha1
kind: KnativeServing
metadata:
name: knative-serving
namespace: knative-serving
- 執行命令創建項目和KnativeServing資源
$oc apply -f knative-serving.yaml
- 查看knative-serving的狀態,成功完成後顯示以下內容。
$ oc get knativeserving.operator.knative.dev/knative-serving -n knative-serving --template='{{range .status.conditions}}{{printf "%s =%s\n" .type .status}}{{end}}'
DependenciesInstalled=True
DeploymentsAvailable=True
InstallSucceeded=True
Ready=True
部署並測試Hello的Serverless應用
- 創建knative-demo項目。
$ oc new-project knative-demo
- 部署Knative的Hello應用。其中“–env TARGET=Knative”是將字符串傳給TARGET環境變量。
$ kn service create hello --image gcr.io/knative-samples/helloworld-go --env TARGET=Knative
Creating service 'hello' in namespace 'knative-demo':
0.296s The Route is still working to reflect the latest desired specification.
0.393s Configuration "hello" is waiting for a Revision to become ready.
33.138s ...
33.369s Ingress has not yet been reconciled.
33.466s Configuration "hello" is waiting for a Revision to become ready.
33.543s Ingress has not yet been reconciled.
74.629s Ready to serve.
Service 'hello' created with latest revision 'hello-nvhqs-1' and URL:
http://hello.knative-demo.apps.cluster-shanghai-3d3e.shanghai-3d3e.example.opentlc.com
- 查看Knative的Service列表。
$ kn service list
NAME URL LATEST AGE CONDITIONS READY REASON
hello http://hello.knative-demo.apps.cluster-shanghai-3d3e.shanghai-3d3e.example.opentlc.com hello-nvhqs-1 2m4s 3 OK / 3 True
- 查看knative-demo項目中的所有資源,其中包括Knative的configuration、service、revision、route對象,還有OpenShift的service、deployment、rs對象。注意:當前項目中還沒有pod資源。
$ oc get all -n knative-demo
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/hello ExternalName <none> cluster-local-gateway.knative-serving-ingress.svc.cluster.local <none> 10m
service/hello-nvhqs-1 ClusterIP 172.30.69.130 <none> 80/TCP 10m
service/hello-nvhqs-1-private ClusterIP 172.30.125.146 <none> 80/TCP,9090/TCP,9091/TCP,8022/TCP 10m
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/hello-nvhqs-1-deployment 0/0 0 0 10m
NAME DESIRED CURRENT READY AGE
replicaset.apps/hello-nvhqs-1-deployment-66db57b95f 0 0 0 10m
NAME CONFIG NAME K8S SERVICE NAME GENERATION READY REASON
revision.serving.knative.dev/hello-nvhqs-1 hello hello-nvhqs-1 1 True
NAME LATESTCREATED LATESTREADY READY REASON
configuration.serving.knative.dev/hello hello-nvhqs-1 hello-nvhqs-1 True
NAME URL READY REASON
route.serving.knative.dev/hello http://hello.knative-demo.apps.cluster-shanghai-3d3e.shanghai-3d3e.example.opentlc.com True
NAME URL LATESTCREATED LATESTREADY READY REASON
service.serving.knative.dev/hello http://hello.knative-demo.apps.cluster-shanghai-3d3e.shanghai-3d3e.example.opentlc.com hello-nvhqs-1 hello-nvhqs-1 True
- 在OpenShift Console中進入knative-demo的Developer視圖,可以看到和hello應用相關的資源。
- 訪問hello應用的地址,確認可以返回“Hello Knative!”,其中“Knative”爲傳進去的環境變量。
$ curl http://hello.knative-demo.apps.cluster-shanghai-3d3e.shanghai-3d3e.example.opentlc.com
Hello Knative!
- 此時立即執行以下命令,確認此時可以查看項目在運行的Pod資源。不過在一分鐘以後會又看不到Pod了。
$ oc get pod
NAME READY STATUS RESTARTS AGE
pod/hello-rfgt4-1-deployment-a0cd0125-cfvny 2/2 Running 0 22s
- 更新名爲hello的service的環境變量內容。
$ kn service update hello --env TARGET=Kn
Updating Service 'hello' in namespace 'knative-demo':
10.760s Traffic is not yet migrated to the latest revision.
10.871s Ingress has not yet been reconciled.
12.231s Ready to serve.
Service 'hello' updated with latest revision 'hello-cfvny-2' and URL:
http://hello.knative-demo.apps.cluster-shanghai-3d3e.shanghai-3d3e.example.opentlc.com
- 訪問hello應用的地址,確認可以返回結果已經變化。
$ curl http://hello.knative-demo.apps.cluster-shanghai-3d3e.shanghai-3d3e.example.opentlc.com
Hello Kn!
- 查看項目所有資源,確認OpenShift的deployment、rs對象和Knative的revision對象都已經有了一個新版的配置。
$ oc get all
NAME READY STATUS RESTARTS AGE
pod/hello-cfvny-2-deployment-d4cd7655-rfgt4 2/2 Running 0 22s
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/hello ExternalName <none> cluster-local-gateway.knative-serving-ingress.svc.cluster.local <none> 5h6m
service/hello-cfvny-2 ClusterIP 172.30.69.131 <none> 80/TCP 6m22s
service/hello-cfvny-2-private ClusterIP 172.30.64.141 <none> 80/TCP,9090/TCP,9091/TCP,8022/TCP 6m22s
service/hello-nvhqs-1 ClusterIP 172.30.69.130 <none> 80/TCP 5h6m
service/hello-nvhqs-1-private ClusterIP 172.30.125.146 <none> 80/TCP,9090/TCP,9091/TCP,8022/TCP 5h6m
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/hello-cfvny-2-deployment 1/1 1 1 6m22s
deployment.apps/hello-nvhqs-1-deployment 0/0 0 0 5h6m
NAME DESIRED CURRENT READY AGE
replicaset.apps/hello-cfvny-2-deployment-d4cd7655 1 1 1 6m22s
replicaset.apps/hello-nvhqs-1-deployment-66db57b95f 0 0 0 5h6m
NAME LATESTCREATED LATESTREADY READY REASON
configuration.serving.knative.dev/hello hello-cfvny-2 hello-cfvny-2 True
NAME CONFIG NAME K8S SERVICE NAME GENERATION READY REASON
revision.serving.knative.dev/hello-cfvny-2 hello hello-cfvny-2 2 True
revision.serving.knative.dev/hello-nvhqs-1 hello hello-nvhqs-1 1 True
NAME URL LATESTCREATED LATESTREADY READY REASON
service.serving.knative.dev/hello http://hello.knative-demo.apps.cluster-shanghai-3d3e.shanghai-3d3e.example.opentlc.com hello-cfvny-2 hello-cfvny-2 True
NAME URL READY REASON
route.serving.knative.dev/hello http://hello.knative-demo.apps.cluster-shanghai-3d3e.shanghai-3d3e.example.opentlc.com True
- 查看名爲hello的service詳細信息。確認最新的revision(hello-cfvny-2)接收了100%的請求。
$ kn service describe hello
Name: hello
Namespace: knative-demo
Age: 5h
URL: http://hello.knative-demo.apps.cluster-shanghai-3d3e.shanghai-3d3e.example.opentlc.com
Revisions:
100% @latest (hello-cfvny-2) [2] (2m)
Image: gcr.io/knative-samples/helloworld-go (pinned to 5ea96b)
Conditions:
OK TYPE AGE REASON
++ Ready 2m
++ ConfigurationsReady 2m
++ RoutesReady 2m
- 查看Knative的revision對象。確認結果和(10)看到的項目包括的revision一樣。
$ kn revision list
NAME SERVICE GENERATION AGE CONDITIONS READY REASON
hello-cfvny-2 hello 2 45m 3 OK / 4 True
hello-nvhqs-1 hello 1 5h46m 3 OK / 4 True
- 執行命令,將請求平均發給以上2個revision。
$ kn service update hello --traffic @latest=50 --traffic hello-nvhqs-1=50
Updating Service 'hello' in namespace 'knative-demo':
0.066s The Route is still working to reflect the latest desired specification.
0.090s Ingress has not yet been reconciled.
1.450s Ready to serve.
Service 'hello' updated with latest revision 'hello-cfvny-2' (unchanged) and URL:
http://hello.knative-demo.apps.cluster-shanghai-3d3e.shanghai-3d3e.example.opentlc.com
- 查看Knative的service對象,確認配置修改爲2個revision各自接收50%的請求。
$ kn service describe hello
Name: hello
Namespace: knative-demo
Age: 5h
URL: http://hello.knative-demo.apps.cluster-shanghai-3d3e.shanghai-3d3e.example.opentlc.com
Revisions:
50% @latest (hello-cfvny-2) [2] (41m)
Image: gcr.io/knative-samples/helloworld-go (pinned to 5ea96b)
50% hello-nvhqs-1 [1] (5h)
Image: gcr.io/knative-samples/helloworld-go (pinned to 5ea96b)
Conditions:
OK TYPE AGE REASON
++ Ready 6m
++ ConfigurationsReady 41m
++ RoutesReady 6m
- 在OpenShift控制檯的Developer視圖中可以上可以看到hello應用的Toplogy。
- 點擊上圖的Set Traffic Distribution按鈕,可以在彈出窗口中可以爲不同的Revision分配流量比例。
- 多次訪問hello應用,確認返回結果部分是“Hello Knative!”、部分是“Hello Kn!”。
$ curl http://hello.knative-demo.apps.cluster-shanghai-3d3e.shanghai-3d3e.example.opentlc.com
Hello Knative!
$ curl http://hello.knative-demo.apps.cluster-shanghai-3d3e.shanghai-3d3e.example.opentlc.com
Hello Kn!