Representing Kubernetes ontology in MeshModel

[leecalcote]

As an extension of #21:

Network topologies and graph databases go hand-in-hand. The OpenAPI specifications for Kubernetes provides taxonomy, but augmenting a graph data model with formalized ontologies enables any number of capabilities, one of the more straightforward is the inferencing requisite for natural language processing, and consequently, a human-centric query / response interaction becomes becomes possible. More importantly, more advanced systems can be built when a graph data model of connected systems is upgraded to be a knowledge semantic graph. Deliverables (among other items):

• Model capabilities browser
• Import/export of models and components as OCI images
• augmentation of cuelang-based component generator

[sagar10arya]

@leecalcote Hello sir. I want to apply for this project as an LFX mentee. I am familiar with golang and would love to get familiar with this project.

[mugishasam123]

hey @leecalcote, I am very interested in working on this project as a part of the LFX Mentorship program. I have prior experience working with kubernetes and I believe this project would provide an excellent opportunity for me to enhance my skills and gain more practical experience in this field.

I am excited to learn more about the project and would appreciate any information or resources you can provide to help me prepare for the mentorship. Thank you for considering my application.

[achiverram28]

Hey @leecalcote , I am a very deep Kubernetes enthusiast , I want to really work on this under the LFX Mentorship program

[hamza-mohd]

I've been following along with the work that's been happening here. It's coming along nicely. I've enjoyed working with the team to help to find relationships between Kubernetes resources and deeply explore the behaviors of these the standard and custom resources both managed by built-in Kubernetes controllers and custom operators.

[leecalcote]

This is very nice to hear, @hamza-mohd 🙂 given the progression, thus far, let's close out this issue, and open up a couple new issues to track the next chapter of work.