Admin Kubernetes & PKS $kubectl create –f App.yaml The “App” Kubernetes Cluster Deploys and Operates the Kubernetes Clusters Desired state of Application The difference between PKS and Kubernetes VMware PKS Value Proposition 22 A turnkey solution for enterprises and service providers to provision, operate and manage production grade Kubernetes clusters Fully supported Kubernetes PKS uses the Operations PKS simplifies Day 2 operations with built-in network security—powered by NSX, high availability, logging, monitoring, analytics, and automated health checks. On-Demand Provisioning PKS deploys

Kubernetes安全求生指南 ©2019 VMware, Inc. 2  您的Kubernetes環境夠安全嗎?  Kubernetes安全最佳實務  VMware Enterprise PKS平台如何實踐K8s與容器的安全強化  最困難的部分其實是....  總結 本日議程 3 ©2019 VMware, Inc. 您的Kubernetes環境夠安全嗎? ©2019 VMware, Inc. VMware Enterprise PKS平台 如何實踐K8s與容器的安全強化 How PKS Enterprise PKS Implement Kubernetes & Container Security ©2019 VMware, Inc. 12 VMware Enterprise PKS對於NIST容器安全指南有完整的實作 White Paper: Enterprise PKS Secures Containers and Kubernetes, Feb, 2019 https://assets.contentstack.io/v3/assets/blt58b49a8a0e43b5ff/blt2218fac49ab28d5f/5c742622670387985f9fd09d/vmware-enterprise-pks-security-white-paper

and Consume Consume Private Cloud Public Cloud Public Cloud VMware Cloud Native Apps Portfolio PKS VKE VIC Beta 5 ©2018 VMware, Inc. vSphere Integrated Containers (VIC) 6 ©2018 VMware, Inc. vSphere support Docker API Resource Pool 75 Ghz, 768GB 8 ©2018 VMware, Inc. Pivotal Container Service (PKS) 9 ©2018 VMware, Inc. Kubernetes Is Only One Layer of the Container Service Stack Image Registry Suite NSX-T BOSH (K8s LCM) BOSH (cluster LCM) Kubernetes Harbor P K S 10 ©2018 VMware, Inc. PKS on VMware SDDC Rapidly deliver and operationalize next-generation apps Physical Infrastructure

e.g. com.example.something • timeout=[millis]: timeout in milliseconds • create-pks: create primary keys • drop-pks: drop primary keys • create-constraints: create indexes and foreign keys after loading

e.g. com.example.something • timeout=[millis]: timeout in milliseconds • create-pks: create primary keys • drop-pks: drop primary keys • create-constraints: create indexes and foreign keys after loading

only pass events for pks 1 to 10 T3: select * from t1 where pk > 10 limit 10 GTID: 112, Last PK 20 send rows to target Another gotcha!: Note that at T3 when we selected the pks from 11 to 20 the gtid from T3 we would still have an inconsistent state, if transactions 111 and 112 affected the rows from pks 1 to 10. This leads us to the following flow: T1: select * from t1 where pk > 0 limit 10. GTID: 100 only pass events for pks 1 to 10 T3: select * from t1 where pk > 10 limit 10 GTID: 112, Last PK 20 T4: replicate from 111 to 112 only pass events for pks 1 to 10 T5: Send rows for pks 11 to 20 to target

only pass events for pks 1 to 10 T3: select * from t1 where pk > 10 limit 10 GTID: 112, Last PK 20 send rows to target Another gotcha!: Note that at T3 when we selected the pks from 11 to 20 the gtid from T3 we would still have an inconsistent state, if transactions 111 and 112 affected the rows from pks 1 to 10. This leads us to the following flow: T1: select * from t1 where pk > 0 limit 10. GTID: 100 only pass events for pks 1 to 10 T3: select * from t1 where pk > 10 limit 10 GTID: 112, Last PK 20 T4: replicate from 111 to 112 only pass events for pks 1 to 10 T5: Send rows for pks 11 to 20 to target

only pass events for pks 1 to 10 T3: select * from t1 where pk > 10 limit 10 GTID: 112, Last PK 20 send rows to target Another gotcha!: Note that at T3 when we selected the pks from 11 to 20 the gtid from T3 we would still have an inconsistent state, if transactions 111 and 112 affected the rows from pks 1 to 10. This leads us to the following flow: T1: select * from t1 where pk > 0 limit 10. GTID: 100 only pass events for pks 1 to 10 T3: select * from t1 where pk > 10 limit 10 GTID: 112, Last PK 20 T4: replicate from 111 to 112 only pass events for pks 1 to 10 T5: Send rows for pks 11 to 20 to target

only pass events for pks 1 to 10 T3: select * from t1 where pk > 10 limit 10 GTID: 112, Last PK 20 send rows to target Another gotcha!: Note that at T3 when we selected the pks from 11 to 20 the gtid from T3 we would still have an inconsistent state, if transactions 111 and 112 affected the rows from pks 1 to 10. This leads us to the following flow: T1: select * from t1 where pk > 0 limit 10. GTID: 100 only pass events for pks 1 to 10 T3: select * from t1 where pk > 10 limit 10 GTID: 112, Last PK 20 T4: replicate from 111 to 112 only pass events for pks 1 to 10 T5: Send rows for pks 11 to 20 to target

only pass events for pks 1 to 10 T3: select * from t1 where pk > 10 limit 10 GTID: 112, Last PK 20 send rows to target Another gotcha!: Note that at T3 when we selected the pks from 11 to 20 the gtid from T3 we would still have an inconsistent state, if transactions 111 and 112 affected the rows from pks 1 to 10. This leads us to the following flow: T1: select * from t1 where pk > 0 limit 10. GTID: 100 only pass events for pks 1 to 10 T3: select * from t1 where pk > 10 limit 10 GTID: 112, Last PK 20 T4: replicate from 111 to 112 only pass events for pks 1 to 10 T5: Send rows for pks 11 to 20 to target