layer5 VS apiclarity

There’s no better way to test-drive Layer5 than by diving in and playing with it. The purpose of the blog is to create awareness about a service mesh like Layer5. To learn further it is recommended to go through the official documentations of Layer5.

From My PR being merged, working on UI, Upgrading Gatsby v2 to v3 for which I had to learn a bit about GraphQL, how Gatsby Plugins work (PR) to me shifting to CI/CD Issues, writing blogs, learning golang(for mesheryctl issues) to having the most amazing as well as exciting 1-1 call with Lee Calcote, Founder & CEO of Layer5 to discuss about my interests/aims and some future ideas/goals of the projects, the journey has been amazing and I hope it will be the same or much more exciting in the future 💯 Also, I have to thank Nikhil Ladha as well as other members of the community for constantly guiding and mentoring me 🍻

We'll install APIClarity into a Kubernetes cluster to test our API documentation. We're using a Kind cluster for demonstration purposes. Of course, if you have another Kubernetes cluster up and running elsewhere, all steps also work there.

If you go to APIClarity, the first thing you’ll see is the source code (Figure 1), followed by some documentation at the bottom.

This feature is available in the open-source tool APIClarity, as part of the OpenClarity initiative.

Hi, I would also like to add another tool I'm contributing to at work (cisco) called APIClarity [1]. It aims at reconstructing swagger specifications of REST microservices running in K8S, but can also be run locally.

This is a challenging task and we don't support OpenAPI v3 specs yet (we are working on it).

Feel free to have a look, and get ideas from it :)

We'll also be presenting it at next Kubecon 2022.

[1]: https://github.com/openclarity/apiclarity

For example, APIClarity is a tool that observes all of the API traffic within your Kubernetes environment. Based on traffic observation, APIClarity infers an OpenAPI description for those APIs. This is especially helpful if the API creator never defined or provided such a description. It also surfaces potential problems with existing APIs, such as requests made to undocumented, shadow APIs or continued use of deprecated, zombie APIs. If you’re getting started on the path toward OAS compliance, then tools like APIClarity can be a great source of insight and observability.

The fundamental first step to solving this problem is to create an API spec and use it to audit and document the APIs your apps use. Ideally, we would create an API spec simply by observing API traffic in real-world applications. In the past, there was no simple, scalable, and open-source tooling capable of doing this. Now, we have APIClarity—an open-source API traffic visibility tool for Kubernetes (K8s) clusters. It’s purpose-built to address the gap and enable API reconstruction through observation.