...
- Randy & Will had homework from last call; haven't heard back from them yet
- Reviewing Darien's answers to the messaging framework doc
- He'll add this to the wiki in a bit
- Can't forget to include security in the discussion about service chaining
- Micro-segmentation super helpful for security
- Also has analytics for this segmentation
- Align with SecDevOps
- Zero trust
- TF makes it easy
- Security from Day 1, don't have to add it later
- Dev perspective: TF is a CNI, so you don't need to change what you're doing
- LC: WS & Randy were both questioning the "service chain" term last week
- Too telco-centric and not particularly devops-y?
- DH: Could be, could call it something else if there were another name for it
- Instead lead with SecDevOps for TF Networking instead (just uses service chaining behind the scenes)?
- Lean on app security instead
- Updating the doc according to the discussion on the call
- Visibility…of what?
- Of app health, flow logs, real-time packet analyzer (need to verify works with k8s)
- LC: Still too networky?
- DH: Not really; the devops in his company are pretty comfortable with a lot of this stuff
- CNI: How is TF better than the others?
- What makes TF better than Calico?
- Maybe something more like "multi-site connectivity"? Ability to manage instances across multiple platforms/sites/clouds? True freedom of movement or some such.
- Need most help with documenting the Proof Points
- What are the cool things that TF does that no one else does?
- Can bubble things up from there
- DH will also talk to some of their k8s gurus
- Work with Calico, Flannel, etc all day
- Will probably have some good ideas
- Do we want to meet next week for the next round?
- Lisa will set up a call for Wednesday