For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

When cloud-native meets monolithic

According to CNCF’s Cloud Native Survey 2020 published on 17 Nov 2020, containers in production jump 300% from the first survey in 2016. Year 2020 itself increased to 92% from 84% in 2019. (https://w...
Published Jan 21, 2021
Version 1.0
BIG-IP
cloud
cloud-native
container
devops
istio
LTM
Microservices
spk
Foo-Bang_Chan's avatar
Icon for Employee rankEmployee
Foo-Bang has 24+ years of experience in the IT industry ranging from application security, modern application architecture, devsecops, gitops and automation. He is passionate with emerging technologies such as cloud native architecture, AI, 5G SBA, service meshes, security and technologies that solve real world challenges and bring value to business.
View Profile
Foo-Bang_Chan's avatar
Icon for Employee rankEmployee
Foo-Bang has 24+ years of experience in the IT industry ranging from application security, modern application architecture, devsecops, gitops and automation. He is passionate with emerging technologies such as cloud native architecture, AI, 5G SBA, service meshes, security and technologies that solve real world challenges and bring value to business.
View Profile
Foo-Bang_Chan's avatar
Foo-Bang_Chan
Icon for Employee rankEmployee
Jan 27, 2021

Thanks. Preparing for the ingress episode. The service mesh doesn't need to be Aspen Mesh. Any Istio based service mesh will works. Technically, it is a mTLS between pod and F5. Hence, in theory (I hasn't test it), other service mesh (non istio) technology should works as well.