个实例失败 （status发⽣改变），Kubernetes系统就会响应spec和status之间的差异，并进⾏更正——在这本例中，会启动⼀个替 换实例。 有关对象spec，status和metadata的更多信息，详⻅： Kubernetes API Conventions 。 描述Kubernetes对象 在Kubernetes中创建对象时，必须提供对象的spec，spec描述对象所期 Deployment所需的字段和对象spec： apiVersion: apps/v1beta1 kind: Deployment metadata: name: nginx-deployment spec: replicas: 3 template: metadata: labels: app: nginx spec: 06-理解K8s对象 在Kubernetes对象的 .yaml ⽂件中，您需要为以下字段设置值： apiVersion ——指定Kubernetes API的版本 kind ——你想创建什么类型的对象 metadata ——有助于唯⼀标识对象的数据，包括 name 字符串，UID和可选的 namespace 您还需要提供 spec 字段。对于不同的Kubernetes对象来说， spec 的格式都是不同的。

Examples - clickhouse-operator docs ClickHouse operator – начало • Хочу во всем разобраться Get files from github repo: git clone https://github.com/Altinity/clickhouse-operator Install the operator: Single-node “cluster” apiVersion: "clickhouse.altinity.com/v1" kind: "ClickHouseInstallation" metadata: name: "demo-01" spec: configuration: clusters: - name: "demo" Здесь нет storage Еще 1 37s Sharding apiVersion: "clickhouse.altinity.com/v1" kind: "ClickHouseInstallation" metadata: name: "demo-01" spec: configuration: clusters: - name: "demo" layout:

Configuration JVM flags credentials labels environment variables extra files ... github.com/GoogleContainerTools/jib Demo $ git clone https://github.com/coollog/micronaut-jib Dockerfile “script” FROM base container image RUN commands to install dependencies COPY application files over Configure the ENTRYPOINT Run the container Produces some layers Produces some layers github com/GoogleContainerTools/jib Pure Java github.com/GoogleContainerTools/jib A container image is a directory of files github.com/GoogleContainerTools/jib Docker Image Format Tarballs that compose into a single

## IngressRoute apiVersion: apiextensions.k8s.io/v1beta1 kind: CustomResourceDefinition metadata: name: ingressroutes.traefik.containo.us spec: scope: Namespaced group: traefik.containo ## IngressRouteTCP apiVersion: apiextensions.k8s.io/v1beta1 kind: CustomResourceDefinition metadata: name: ingressroutetcps.traefik.containo.us spec: scope: Namespaced group: traefik --- ## Middleware apiVersion: apiextensions.k8s.io/v1beta1 kind: CustomResourceDefinition metadata: name: middlewares.traefik.containo.us spec: scope: Namespaced group: traefik.containo

上创建一个yaml文件 # vi pod-nginx-web1-v1.19.5.yml #内容如下 apiVersion: v1 kind: Pod metadata: name: pod-nginx-web1-v1.19.5 #pod名，这个名称可带小数点 labels: #选择特定node结点去运行此容器 # nodelbxx: lbvaluexxxx --- apiVersion: v1 kind: Service #创建service资源 metadata: name: svc-nginx-web1 #其他pod可直接访问此名称:servicePort，如 curl -kv h�p://svc-nginx-web1:2380/ spec: ★namespace 创建命名空间 # cat > namespace-testxx.yaml <metadata: name: testxx labels: labelnamexx: valuexxx EOF # kubectl apply -f namespace-testxx.yaml

cds/nas 30m sc.yaml 内容如下 1 apiVersion: storage.k8s.io/v1 2 kind: StorageClass 3 metadata: 4 name: wordpress-sc-001 5 provisioner: nas.csi.cds.net 6 parameters: 7 archiveOnDelete: apiVersion: v1 2 kind: Namespace 3 metadata: 4 name: wordpress 5 labels: 6 app: wordpress 7 --- 8 apiVersion: v1 9 kind: PersistentVolumeClaim 10 metadata: 11 name: mysql-pv-claim storageClassName: wordpress-sc-001 22 --- 23 apiVersion: v1 24 kind: PersistentVolumeClaim 25 metadata: 26 name: wp-pv-claim 27 namespace: wordpress 28 labels: 29 app: wordpress 30 spec:

—image=nginx:1.7.9 —replicas=3 apiVersion: apps/v1beta1 kind: Deployment metadata: name: nginx-deployment spec: replicas: 3 template: metadata: labels: app: nginx spec: containers: yaml • kubectl create -f hpa.yaml apiVersion: autoscaling/v2alpha1 kind: HorizontalPodAutoscaler metadata: name: php-apache namespace: default spec: scaleTargetRef: apiVersion: apps/v1beta1 distributed micro-services with container?” Programming Pattern • Sidecar apiVersion: v1 kind: Pod metadata: name: test-app spec: containers: - name: app-container image: gcr.io/google_containers/testapp:v1

直接对接 rustvmm 绕 开 fuse 02 client manger manger metadata data data metadata metadata Data and metadata store in different devices File data/metadata Heartbeat Heartbeat metabata Heartbeat metabata

API复杂：区分使用者/关注点分离 • 能力难上手：模块化封装/统一管理 • 云资源：统一API对接 apiVersion: core.oam.dev/v1alpha1 kind: Component metadata: name: nginx annotations: version: v1.0.0 description: > Sample component schematic that describes Worker × × √ Task × √ × Singleton Task × × × apiVersion: core.oam.dev/v1alpha1 kind: Component metadata: name: nginx annotations: version: v1.0.0 description: > Sample component schematic that describes Trait CronHPA CRD CronHPA Trait apiVersion: core.oam.dev/v1alpha1 kind: ApplicationConfiguration metadata: name: my-awesome-app spec: components: - componentName: frontend instanceName: web-front-end

能力注册与管理 应用 Component Deployment Function apiVersion: core.oam.dev/v1alpha2 kind: Component metadata: name: frontend annotations: description: Container workload spec: workload: apiVersion: apps/v1 访问控制 流量配置 Deployment Function apiVersion: core.oam.dev/v1alpha2 kind: ApplicationConfiguration metadata: name: helloworld spec: components: # 1st component - componentName: frontend traits: - trait: （Application Configuration） 面向应用维度配置运维能力与组件 apiVersion: core.oam.dev/v1alpha2 kind: TraitDefinition metadata: name: virtualservices.networking.istio.io annotations: alias: traffic spec: appliesTo: - apps