--------------------------------------------------------------- {{ range $zone := .Zones }} Kris Nova Over engineering the core of Kubernetes kops Kris Nova About Me Kris Nova “I work in the cloud. ClusterName }}: vpc: vpc/{{ ClusterName }} dhcpOptions: dhcpOptions/{{ ClusterName }} {{ end }} Over Engineering Go in Kubernetes # --------------------------------------------------------------- --------------------------------------------------------------- {{ range $zone := .Zones }} So what did we over engineer? ? ? ? Kubernetes Kops Kubernetes Operations Kubernetes Kops Kubernetes Operations

#IstioCon Taming Istio Configuration with Helm Ryan Michela / @ryanmichela / Salesforce #IstioCon In this talk This is a talk about using Helm with Istio ● Look at helm from a new perspective DEMO #IstioCon Demo - Bookinfo What did we see? ● Single entry point for each service’s configuration ● Install each service with a single command ● Single source of truth for auth and egress policy Everything you need to run a service in the mesh ● Ingress-service ○ Add’s ingress gateway configuration to mesh-service ● Mesh-egress ○ Configures TLS egress and policy ● Auth-policy ○ Configures

Optimal Canary Deployments using Istio and how it scores over Spring Cloud and Kubernetes Presented by Archna Gupta What is a Canary Release or Deployment? • A canary deployment, or canary release

security features sufficiently address the concerns they are designed to provide. Four consultants over a period of five weeks along with the help of multiple shadows (provided at no additional cost) worked Networking controls allowing inbound and outbound access of Istio services. • Istio Envoy Usage: The configuration and implemen- tation of Envoy within Istio (NOTE: Envoy itself was not part of the assessment) did not appear to be possible to secure the control plane either by the controlPlaneSecuri ty configuration directive or other means. This left all default services exposed within the cluster. • The default

Programming considerations for the raw web service . . . . . . . . . . . . . . . 24 3.3.1 Fundamental conventions . . . . . . . . . . . . . . . . . . . . . . . . . 24 3.3.2 Example: A typical web service client the same host where virtual machine is executed Con: Significant overhead due to XML marshalling over the wire for each method call Pro: Relatively low invocation overhead In the following chapters Axis that, again, is called clienttest.java and that imitates a few of the commands of VBoxManage over the wire. Then perform the following steps: 1. Create a working directory somewhere. Under your VirtualBox

Programming considerations for the raw web service . . . . . . . . . . . . . . . 24 3.3.1 Fundamental conventions . . . . . . . . . . . . . . . . . . . . . . . . . 24 3.3.2 Example: A typical web service client the same host where virtual machine is executed Con: Significant overhead due to XML marshalling over the wire for each method call Pro: Relatively low invocation overhead In the following chapters Axis that, again, is called clienttest.java and that imitates a few of the commands of VBoxManage over the wire. Then perform the following steps: 1. Create a working directory somewhere. Under your VirtualBox

the same host where virtual machine is executed Con: Significant overhead due to XML marshalling over the wire for each method call Pro: Relatively low invocation overhead In the following chapters (enums), page 333, due to the limitations of SOAP and WSDL lined out in chapter 2.2.3.1, Fundamental conventions, page 32, please have the following notes in mind: 1. Any COM method call becomes a plain function Axis that, again, is called clienttest.java and that imitates a few of the commands of VBoxManage over the wire. Then perform the following steps: 1. Create a working directory somewhere. Under your VirtualBox

the same host where virtual machine is executed Con: Significant overhead due to XML marshalling over the wire for each method call Pro: Relatively low invocation overhead In the following chapters (enums), page 333, due to the limitations of SOAP and WSDL lined out in chapter 2.2.3.1, Fundamental conventions, page 32, please have the following notes in mind: 1. Any COM method call becomes a plain function Axis that, again, is called clienttest.java and that imitates a few of the commands of VBoxManage over the wire. Then perform the following steps: 1. Create a working directory somewhere. Under your VirtualBox

the same host where virtual machine is executed Con: Significant overhead due to XML marshalling over the wire for each method call Pro: Relatively low invocation overhead In the following chapters (enums), page 368, due to the limitations of SOAP and WSDL lined out in chapter 2.2.3.1, Fundamental conventions, page 34, please have the following notes in mind: 1. Any COM method call becomes a plain function Axis that, again, is called clienttest.java and that imitates a few of the commands of VBoxManage over the wire. Then perform the following steps: 1. Create a working directory somewhere. Under your VirtualBox