use them for certain actions. Replication Controller Replication Controllers (RC) are an abstraction used to manage pod lifecycles. One of key uses of replication controllers is to maintain a certain certain number of pods for scaling, or ensure that at least one pod. It is a best practice to use replication controllers to define pod lifecycles, rather than to create pods directly. Replica Sets Replica number of pods are running, replacing pods that die. Replica Sets can act as replacements for Replication Controllers. Service A service is an abstraction on top of pods which provides a single IP

& access control • RBAC: admin, developer, guest • AD/LDAP integration • Policy based image replication • Web UI ( 中文 and English) • Audit and logs • Restful API for integration • Lightweight and easy Replication Service 15 Remote Harbor instance Image Replication between Registry Instances 16 Project Images Policy Image Project Images Initial replication Image Incremental Incremental replication (including image deletion) Image Replication Use Case(1) • Image distribution for large cluster • Load balancing 17 Master – Slave Docker Client push Docker host Docker

本⽂概述了Kubernetes集群中所需的各种组件。 Master组件 Master组件提供K8s集群的控制⾯板。Master对集群进⾏全局决策（例如调度），以及检测和响应集群事件（例如：当 replication controller所设置的 replicas 不够时，启动⼀个新的Pod）。 Master可在集群中的任意节点上运⾏。然⽽，简单起⻅，设置脚本通常在同⼀个VM上启动所有Master组件，并且不会 个单独的进程，但为了降低复杂性，它们都被编译成独⽴的⼆进制⽂件并运⾏在⼀个进程中。 这些控制器包括： Node Controller：当节点挂掉时，负责响应。 Replication Controller：负责维护系统中每个replication controller对象具有正确数量的Pod。 Endpoints Controller：填充Endpoint对象（即：连接Service＆Pod）。 Service 译者按：FQDN是fully qualified domain name的缩写，即：完全限定域名 并⾮所有对象都在Namespace中 ⼤多数Kubernetes资源（例如：Pod、Service、Replication Controllers等）都在某些Namespace中。但Namespace资 源本身并不在Namespace中。低级资源（例如： nodes 和persistentVolumes）也不在任何Namespace中。事件是⼀个

background recovery as “Offline Recovery”. ➢ This is very critical background task similar re-replication on node/disk failures. Offline Recovery How the missing containers are detected in EC? ➢ over replicated. ➢ RM creates the reconstruction command if it finds the container is in under replication ➢ The first DN from the target will be chosen as coordinator to reconstruct all the lost containers recover Block for all Block Close the containers in target DNs Target DNs sending ICR EC Replication Config ➢ Format: CODEC-DATA-PARITY-CHUNKSIZE ○ RS-3-2-1024K ○ RS-6-3-1024K ○ RS-10-4-1024K

Balancer 10.2. Balancer in action 11. HTTP Session Replication 11.1. Enable Cluster HTTP Session Replication 11.2. Web Application Session Replication 12. DOSGi and Transport 13. Discovery Services "runtime clustering" by providing dedicated feature like: * HTTP load balancing * HTTP sessions replication * log centralization Please, see the sections dedicated to those features. 1.2. Cross topology randomly chooses one endpoint providing the HTTP endpoint. 11. HTTP Session Replication Apache Karaf Cellar supports replication of the HTTP sessions on the cluster. It means that the same web application

& access control – RBAC: admin, developer, guest – AD/LDAP integration • Policy based image replication • Vulnerability Scanning • Notary • Web UI • Audit and logs • Restful API for integration Replication Job Services Notary client Remote Harbor Instance Notary Registry V2 Vulnerability Scanning Admin Service Harbor users and partners (selected) 12 Image replication (synchronization) (synchronization) 13 Project Images Policy Image Project Images Initial replication Image incremental replication (including image deletion) Agenda 1 Container Image Basics 2 Project Harbor Introduction

Identity integration and role-based access control − Security and vulnerability analysis − Image replication between instances − Internationalization (currently English and Chinese) Operational experience jar Dockerfile Challenges Image replication (synchronization) 17 Project Images Policy Image Project Images Initial replication Image Incremental replication (including image deletion) Shipping synchronized between environments by using Harbor registry. Production Registry images Global Image Replication 19 • Identical images across multiple sites • Image backup • Local access Agenda 1 Containers

reinvent the wheel • RAFT replication – http://raft.github.io ● Open source Java implementation of RAFT - Apache Ratis Library. • Storage Containers – Unit of replication (collection of blocks) ● RocksDB backup ○ Bucket Granularity ● Replication and DR ○ Stable source image for replication ○ Efficient way to find changes since last replication ○ Near continuous replication ● Compliance ● Easy Rollbacks Identify changes ● Some of the Use cases ○ It can be used for incremental backup ○ Incremental Replication for DR ○ Efficient virus scans ○ Incremental analytics - 45 © 2022 Cloudera, Inc. All rights

Confidential � ©2018 VMware, Inc. • Isolation • Access Control • Vulnerability • Content Trust • Replication • Control Policy SECURITY DISTRIBUTION RELIABILITY DEPLOYMENT OVERVIEW • HA Supporting • Helm VMware, Inc. Replication Policy DISTRIBUTION ���� • �������� • ������� • ������� • ���� ���� Image Replication • ���� • ���� • ���� • ����� • ������ ���� Initial Replication Incremental Docker Distribution Helm Chart Repository Asynchronization Signature Vulnerability Scanning Replication Service Level Agreement (Authorization) SLA: Tenant Mapping (Project) SLA: Flow Control Log

Confidential � ©2018 VMware, Inc. • Isolation • Access Control • Vulnerability • Content Trust • Replication • Control Policy SECURITY DISTRIBUTION RELIABILITY DEPLOYMENT OVERVIEW • HA Supporting • Helm VMware, Inc. Replication Policy DISTRIBUTION ���� • �������� • ������� • ������� • ���� ���� Image Replication • ���� • ���� • ���� • ����� • ������ ���� Initial Replication Incremental Docker Distribution Helm Chart Repository Asynchronization Signature Vulnerability Scanning Replication Service Level Agreement (Authorization) SLA: Tenant Mapping (Project) SLA: Flow Control Log