OpenWhisk • Technical details • Demo What is serverless ? What is serverless ? Serverless＝ Backend as a Service Functions as a Service • Zero server ops – No provisioning, updating, and managing search Helm chart repositories. Apache OpenWhisk Source event Trigger Rule Action Result A serverless, open source cloud platform that executes functions in response to events at any

"dev" , "environment" : "qa" , "environment" : "production" "tier" : "frontend" , "tier" : "backend" , "tier" : "cache" "partition" : "customerA" , "partition" : "customerB" "track" : "daily" (production, qa) tier notin (frontend, backend) partition !partition 第⼀个示例选择Key等于 environment ，Value等于 production 或 qa 的所有资源。 第⼆个示例选择Key等于 tier ，Value不等于 frontend 或 backend ，以及所有Key不等于 tier 的所有资源。 第三个示例选择Key包含 时）。尽管每个 Pod 有⾃⼰的IP，但这些IP可能是会变化的。这 导致⼀个问题：如果⼀些 Pod （称为backend）为Kubernetes群集中的其他 Pod （称为frontend）提供功能，那么 frontend如何找到，并⼀直能找到backend呢？ 译者注：下⾯将backend译为后端，frontend译为前端。 可⽤ Services 来解决该问题。 Kubernetes

51~53）使用haproxy做反向代理 frontend k8s_api_tcp_6443 bind *:6443 mode tcp default_backend my_k8s_cluster_6443 backend my_k8s_cluster_6443 mode tcp balance roundrobin server s1 10.99 "web.xxx.com" h�p: paths: - path: / #若不指定url，则默认就是/根路径，全部转发 backend: serviceName: mynginx-svc servicePort: 1380 - host: "web2.xxx.com" h�p: - path: /apixx #转发到后端时也是带这个url的 backend: serviceName: mynginx-svc2 servicePort: 2390 - path: /sta�cxx backend: serviceName: mynginx-svc

Kubernetes Service�Endpoints Label Selector Label: app=backend IP: 172.17.10.1 Port: 80 Label: app=MyApp Container Container Label: app=backend IP: 172.17.10.2 Port: 80 Label: app=MyApp Container Container Controller Label: app=MyApp Replicas: 2 Service <10.0.0.11>:<9376> Label: app=MyApp Endpoints: track backend pod changes <172.17.10.1>:<80> <172.17.10.2>:<80> ... Cluster DNS record: pod1.clusterdomain pod2

Ingress properties: - name: path value: "/" applicationScopes: - my-vpc-network - componentName: backend instanceName: database applicationScopes: - my-vpc-network vpc-3a1p8n container- 8q93re slb-7yt83n Application Configuration：组装与自包含 OAM 加持下的 Kubernetes PaaS K8s 团队 运维 研发 监控报警 灰度发布 日志 扩缩容 负载均衡 web backend Trait Promethus Operator Elasticsearch Operator database Component OpenKruise RDS operator ……

落地效果 读写 QPS > 1w • 背景介绍 • 设计思路 • 性能优化 • 落地效果 • 未来演进 影响力构建 集成进入 Kubernetes 作为新型 Storage Backend 已经开源，以 TiKV 作为存储引擎 持续优化和完善系统 架构演进 • 目前所有消息严格要求有序 • 消息不重不丢、严格有序，所以写必须单点 • Kubernetes 本质是一个最终一致性的系统

KMS plugin for Kubernetes ● Secrets are in etcd, with root of trust in Vault Kubernetes auth backend for HashiCorp Vault ● Authenticate to Vault using a K8s service account Kubernetes secrets: requirements

search Virtual Applications vRealize Ops, Log Insight For Comprehensive Visibility 32 UI and API Backend Advanced Analytics Engine Metrics Collection and Storage Iterate & Troubleshoot Issues Trend

com/GoogleContainerTools/jib Me Java Developer Building website for pet clinic Wants to containerize the backend Wants container on registry ilovejava.io/petclinic-app github.com/GoogleContainerTools/jib github

getApps() { var result = ""; var applist = Object.keys(apps); for (var i=0; i < applist.length; i++) { if(i == 0) result = applist[i]; else result += "," + applist[i]; } return result; } license.pem: | -----BEGIN LICENSE KEY----- L/+DAwEBB2xpY2Vuc2UB/4QAAQIBB1BheWxvYW