Eric Chen

[F5 @F5]

Wishing you health, happiness, and prosperity in the #YearOfTheTiger2022!

[F5 DevCentral Community @devcentral]

AWS has recently launched the Amazon EKS Anywhere (EKS-A) service and we've partnered with the Amazon team to help our customers leverage @F5 solutions to make their EKS Anywhere environment highly available and secure. @chen23 explains https://t.co/5RLYhW93Pm

[Eric Chen @chen23]

@darkkavenger @ExploreVM For point 3, and back to 1. For SD-WAN you would typically only focus on network L3 (get from IP address one to IP address two). Volterra can do that, but it can focus on the application issue, L4/L7 (get from App A to App B).

[Eric Chen @chen23]

@ExploreVM @darkkavenger 3. can run on HW, virtual machine, or as container in K8s; ability to orchestrate through SaaS controller

[Eric Chen @chen23]

@ExploreVM @darkkavenger @ExploreVM re: value of Volterra
1. abstract create network mesh with multiple cloud/on-prem networking

[Eric Chen @chen23]

@ExploreVM @darkkavenger 2. consider if need to bridge networks, also (omitted from preso/demo) also able to serve public traffic via Volterra edge (public anycast ips) to apps w/ additional security as needed

[F5 DevCentral Community @devcentral]

ECS Anywhere (currently in Public Preview) extends the reach of Amazon's #ECS service to customer's datacenters. In this article we'll look at how @F5 is helping its customers connect their F5 solutions to ECS Anywhere. @chen23 with the how-to. https://t.co/Cc9xQwfF3S

[Eric Chen @chen23]

@devcentral @F5 ECS Anywhere is now Generally Available (no longer Public Preview) https://t.co/Djo2NhuMjs

[Eric Chen @chen23]

How to Automate Load Balancing #AWS ECS Anywhere (tech preview) https://t.co/UFjppkm8Q0

[Eric Chen @chen23]

Hey ⁦⁦@pcmccarron⁩ can ⁦@HashiCorp⁩ help ⁦@F5⁩ solve day 2.72 (e) changes? (May 25th) https://t.co/Xpik7RLP4v

[Eric Chen @chen23]

The basics of using F5 BIG-IP with AWS Transit Gateway Connect. GRE & BGP? https://t.co/iFyzJlvAbP

[Eric Chen @chen23]

@devcentral @Volterra_ @jasonrahm @JohnWagnon Thanks for having me on the show @JohnWagnon @jasonrahm. It was fun to finish off the show with a demo :)

[Eric Chen @chen23]

@lmacvittie cat > [file] is my editor of choice. And the correct answer is emacs

[F5 DevCentral Community @devcentral]

Pushing Updates to BIG-IP w/ Consul Terraform Sync from @chen23 https://t.co/0awQ9ps4GT

[F5 DevCentral Community @devcentral]

Transparent Load Balancing in Azure from @chen23 shows how to reduce the amount of address translation to make it possible for a backend application to see the original client IP address. https://t.co/Krq1CRxS1o

[Eric Chen @chen23]

Demo of F5 Automation Toolchain w/ Postman/Visual Studio Code/Terraform https://t.co/npZ4F1cIuW @devcentral #BeF5 #CodeConnects

[F5 DevCentral Community @devcentral]

This week on DevCentral Connects! 'The way to control it, is totally automatic, with F5 Tools around!' @jasonrahm & @JohnWagnon welcome Daniel Stokes & @chen23 to talk about the F5 Automation Toolchain. Set your reminder for Thursday Aug 27, 12:30pac. https://t.co/MRKn7euwIP

[Eric Chen @chen23]

Automating Red Hat OpenShift, F5 BIG-IP, NGINX and get your DNS into your OpenShift clusters. https://t.co/QxiRpyDV4r @rsalsa

[HashiCorp, an IBM Company @HashiCorp]

Join our webinar: "Zero Touch Application Delivery with F5 BIG-IP, Terraform, and Consul" to see how @F5 works with HashiCorp for a complete solution with an automated approach. https://t.co/cvnnPPYl0R

[Eric Chen @chen23]

@thockin Or in network terms does 3b scenario B = flow #1 src: 192.168.1.1 (client) dst: 192.0.2.10, flow #2 (via LB) src: 172.0.17.23.23 dst: 172.17.0.23 (use CNI to make next hop to node). LB has a leg on CNI network.

[Eric Chen @chen23]

@thockin In network terms does 3b scenario A = flow #1 src: 192.168.1.1 (client) dst: 192.0.2.10, flow #2 (via LB) src: 192.168.1.1 dst: 192.0.2.10 (use CNI to make next hop to node). flow #3 (node level IPVS) src: 192.168.1.1 dst: 172.17.0.23 (Pod IP).