ceposta07

6 ms·

1.
Prevent MCP Tool Poisoning with a Registration Workflow(solo.io)
2 points by ceposta07 1y ago|0 comments
2.
A Gentle Intro to LLMs for Platform Engineers(blog.christianposta.com)
2 points by ceposta07 2y ago|0 comments
3.
by ceposta07 3y ago
lol i’m not quite following how manually injecting envoy, “configuring envoy yourself/by hand” in a pod and “copying istio code for iptables re-direction” and then trying to maintain this yourself is easier than just using istio? insta
4.
by ceposta07 3y ago
I think it does come down to risk and risk mitigation. As someone who works for an “Istio vendor” we see some of the largest deployments of Istio in the world for mission critical/tier-0 workloads… and all the steps it took to get ther
5.
Configuration as Data, GitOps, & Controllers: it’s not simple for multi-cluster(solo.io)
1 points by ceposta07 5y ago|0 comments
6.
Configuring CORS and JWT in Istio for secure, cross-origin requests(solo.io)
1 points by ceposta07 6y ago|0 comments
7.
by ceposta07 6y ago
Yes definitely. Similar to what we already do for KNative https://docs.solo.io/gloo/latest/guides/integrations/knative... RE AWS API Gateway... Gloo is more full featured and self hosted. Even wrt perfor
8.
by ceposta07 6y ago
Disclaimer: I am an employee of Solo.io I'd say a lot of our users are from big enterprises, especially financial services where security is paramount. Gloo has a decoupled control plane so it can be scaled and secured independently fr
9.
by ceposta07 6y ago
Kong is mostly built on OpenResty/Lua I'd say the main reason to use Gloo is it's much simpler, it's based on Envoy which is where most of the innovation around L7 proxies is happening these days (ie, see WebAssembly), a
10.
by ceposta07 6y ago
Contour is not an API Gateway. Disclaimer: I work for Solo.io An API Gateway can do sophisticated edge security challenges (OIDC, Authz based on OPA, web app firewalling/WAF, etc) as well as things like message transformation, swagger&
11.
Guidance for Building a Control Plane for Envoy Part 4 – Build for Extensibility(blog.christianposta.com)
2 points by ceposta07 7y ago|0 comments
12.
Building a Control Plane for Envoy Part 3 – Domain Specific Configuration API(blog.christianposta.com)
1 points by ceposta07 8y ago|0 comments
13.
Guidance for Building a Control Plane for Envoy Part 2 – Identify Components(blog.christianposta.com)
1 points by ceposta07 8y ago|0 comments
14.
Exposing Microservices Running in AWS EKS with a Microservices/API Gateway(medium.com)
1 points by ceposta07 8y ago|0 comments
15.
API Gateways are going through an identity crisis(medium.com)
4 points by ceposta07 8y ago|0 comments
16.
Application Safety / Correctness Can't Be Offloaded to Istio or Any Service Mesh(blog.christianposta.com)
2 points by ceposta07 8y ago|0 comments
17.
Advanced Traffic-Shadowing Patterns for Microservices with Istio Service Mesh(blog.christianposta.com)
2 points by ceposta07 9y ago|0 comments
18.
Traffic Shadowing with Istio: Reducing the Risk of Code Release(blog.christianposta.com)
2 points by ceposta07 9y ago|0 comments
19.
Comparing Envoy and Istio Circuit Breaking with Netflix OSS Hystrix(blog.christianposta.com)
2 points by ceposta07 9y ago|0 comments
20.
Deep dive Envoy and Istio workshop(blog.christianposta.com)
1 points by ceposta07 9y ago|0 comments
21.
Low-Risk Monolith to Microservice Evolution Part II(blog.christianposta.com)
2 points by ceposta07 9y ago|0 comments
22.
About when Not to do microservices(blog.christianposta.com)
1 points by ceposta07 9y ago|0 comments
23.
Application Network Functions with ESBs, API Management, and Now.. Service Mesh?(blog.christianposta.com)
1 points by ceposta07 9y ago|0 comments
24.
Microservices Patterns with Envoy Proxy, Part III: Distributed Tracing(blog.christianposta.com)
1 points by ceposta07 9y ago|0 comments
25.
Microservices Patterns with Envoy Proxy, Part II: Timeouts and Retries(blog.christianposta.com)
1 points by ceposta07 9y ago|0 comments
26.
Microservices Patterns with Envoy Sidecar Proxy(blog.christianposta.com)
1 points by ceposta07 9y ago|0 comments
27.
by ceposta07 9y ago
Um. Yes.
28.
The Hardest Part of Microservices: Calling Your Services(blog.christianposta.com)
1 points by ceposta07 9y ago|0 comments
29.
Excited about a '2.0' tech stack for microservices with Kubernetes, Envoy, gRPC(blog.christianposta.com)
2 points by ceposta07 10y ago|0 comments
30.
The Hardest Part About Microservices: Your Data(blog.christianposta.com)
1 points by ceposta07 10y ago|0 comments

More ›