Changes between Version 3 and Version 4 of K8sFutures2019

Timestamp:

Feb 6, 2019, 3:15:46 PM (5 years ago)

Author:

darkblueb

Comment:

--

K8sFutures2019

@@ -9 +9 @@
 In the past two years, the Kubernetes system [0], originally from Google engineering and implemented in Golang, has moved to the forefront of container-driven workflows in industry. RedHat and others had been involved with Kubernetes, and also other container systems, but K8s as it is called for short, has momentum and with it, engineering resources. It is safe to say that it is a hard problem to accomplish well, and there is little to be gained by re-inventing these kinds of plumbing-level compute mechanisms.
 
-Overview of Current Systems - Creating Containers
+**Overview of Current Systems - Creating Containers**
 
 Three parts to a container system workflow:
@@ -23 +23 @@
 
 
+Industry or others may choose to run one or more of these processes behind firewalls privately. From a security perspective, role-based editing and access to content, and an internal audit-trail give greater control of the process.
+
+Outside of the firewall, an ecosystem can develop "trusted" sources of components and containers, with varying degrees of formality. The Debian project is an example of a well-established trust source. Other dot-orgs can choose their participation level in the trust chain, with an associated responsibility to monitor the operations and results. In the field attacks, particularly in Windows system but also Linux and others, have shown that inserting attack code into a high-profile project is an effective attack vector.
+
+
+
 [0] https://en.wikipedia.org/wiki/Kubernetes