Inspiration
as LENS user monitoring Kubernetes cluster, I notice that current access to some components such as Traefik ingress routes, middlewares can be enhanced and should not be limited only to textual yaml content.
What it does
We propose a LENS extension to enable direct access and view about Traefik Ingress Routes, Middlewares.
How we built it
I have read and followed the LENS Extension guides, such as this link : LENS extension guide
Lookup of Some example was helpful for auto training. Hence we need to develop a LENS extension as React package
Challenges we ran into
After Installation of the LENS extension, The activation does not make appear the extension menu on the LENS interface. Fortunately, the usage of Developer Tools option enables to get interactive logs and debug the display problem. The dist directory was not included in the npm package.
Removing dist from the .gitignore enables to solve the LENS extension not appearing in Cluster menu problem.
Accomplishments that we're proud of
The custom LENS extension can be developed locally, installed on the LENS cluster and (de)activated on demand.
Please find hereafter the LENS extension package from LENS version 5 : LENS Lorcie Utils Extension Package
What we learned
Development, Debug of LENS extension
What's next for CombExt
Add more utilities
Log in or sign up for Devpost to join the conversation.