.svg){kind=small}
Linkerd has been able to do workload-based policy for a very long time—for example, it has long been possible to allow workload A to talk to workload B but not workload C. However, it was still up to application developers to write extra code if, for example, workload A should be allowed to ask workload B to check a message but not to sign it.That all changes in Linkerd 2.12 with route-based policy. Now the mesh can enforce policy based on which workload is talking to which and what it’s trying to say. Join us to learn what this new feature is, how you can use it, and what kind of value it can add.
Wanna give it a try? Here are the workshop slides and the GitHub repo. Happy meshing!
Linkerd has been able to do workload-based policy for a very long time—for example, it has long been possible to allow workload A to talk to workload B but not workload C. However, it was still up to application developers to write extra code if, for example, workload A should be allowed to ask workload B to check a message but not to sign it.That all changes in Linkerd 2.12 with route-based policy. Now the mesh can enforce policy based on which workload is talking to which and what it’s trying to say. Join us to learn what this new feature is, how you can use it, and what kind of value it can add.
Wanna give it a try? Here are the workshop slides and the GitHub repo. Happy meshing!
.svg)