code & dependencies 2. Environment scripts & creation tools 3. DB scripts and reference data 4. Containers 5. Automated tests 6. Project artifacts – documentation, procedures, etc. 7. Application configuration to large batch size ii. TBD enables: 1. Frequent commits 2. Runs of automated tests of the integrated system as a whole 3. Work towards single-piece flow iii. Trunk & state of Deployment Pipeline system iv. Modified Definition of Done – “At the end of each development interval, we must have integrated, tested, working, and potentially shippable code, demonstrated in a production-like environment

#给pod打标签，便于其他资源对它的选择 lbname: lbvalue-nginx-web1 spec: containers: #在spec次级，定义一组容器，-表示数组 - name: nginx-v1-19-5 EOF # kubectl apply -f namespace-testxx.yaml ★镜像获取方式imagePullPolicy 在containers/- name/下面，与image标签同级 spec: containers: #在spec次级，定义一组容器，-表示数组 - name: nginx-v1-19-5 metadata: labels: podlable: nginx-deploy-pod #pod模板标签 spec: containers: #定义一组容器 - name: nginx-v1-19-5 #容器名，小写字母开头，后可接数字-减号，不可带 小数点 image:

and impacts to software applications are understood.  Deploy immutable infrastructure, such as containers. The concept of immutable infrastructure is an IT strategy in which deployed components are replaced service. 2. Container policy enforcement. This includes ensuring container hardening from DCAR containers are preserved and complies with the NIST 800-190 requirements [12]. 3. Runtime Defense, this mutual Transport Layer Security authentication (mTLS), an encrypted communication tunnel between containers, strong identities per Pod using certificates, and whitelisting rather than blacklisting. Services

knowledgeable, not far removed groups. b. Shift away from periodic inspections and approvals; move to integrated peer reviews performed continually as part of daily work c. THE DANGERS OF CHANGE APPROVAL PROCESSES

for confidentiality, integrity, and availability b. Don’t inspect security in at the end, it’s integrated as part of our daily work i. Make security part of everyone’s jobii. Integrate preventative controls

frictionlessly and quickly from requirements to deployment.  The developer uses a powerful integrated development environment (IDE) that centralizes the tools that help him or her do the job. 

IT capabilities as being in a continuous state of transformation, when we see them as tightly integrated into an EA, and when we realize that the costs and risks of custom development have been radically