Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[LFX Fall '23 Mentorship]: Extend use-case of detecting deprecated Kubernetes API usage #251

Closed
jwmatthews opened this issue Jul 21, 2023 · 14 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@jwmatthews
Copy link
Member

jwmatthews commented Jul 21, 2023

This is a LFX mentorship project intended to run in Fall 2023

Description

We are looking for help on extending a use-case of detecting usage of deprecated and removed Kubernetes APIs in applications. We need help in creating analysis rules that work with our static code analyzer, help to create automated tests to ensure this functionality is working as expected, and documentation to share with the community on how to leverage Konveyor for this scenario.

This work will involve

  • determining what API resources have been deprecated or removed in each version of Kubernetes
  • building Analyzer LSP Rules to be contributed to our Rulesets repository
  • curation or development of sample applications in Golang, Java, and YAML to aid test scenarios
  • creation of a new test to be integrated into Konveyor's CI
  • documentation to show a guided walkthrough of this capability

You can see the beginning of this use-case being addressed with a sample rule in this demo of analyzer-lsp.

The development environment is based on Golang and Kubernetes. A minikube instance will work well for local development on Linux or Mac systems.

Related Links:

Projects to consider for inspiration/collaboration/integration:

@jwmatthews
Copy link
Member Author

Note: https://github.com/rikatz/kubepug may help for seeing how they determine what APIs are deprecated

@jwmatthews
Copy link
Member Author

Related to: cncf/mentoring#1035

@punithnayak
Copy link

Hey this project looks cool will defiantly apply when form come up

@satyampsoni
Copy link

Hello Konveyor team.
This project aligns with my interest and my skills and I would love to contribute to this project and during LFX Fall 2023.
Pls let me know if there is any slack community to join for further communication.
Help will be highly appreciated.

@kaovilai
Copy link
Member

You can join us on kubernetes slack

Need an invitation?
Visit https://slack.k8s.io/ for an invitation.

@tanayvaswani
Copy link

The idea looks great! If I got the opportunity, I would feel happy to work with the team!

@AdiAkhileshSingh15
Copy link

Hey,
I'm really interested in this project and I plan to apply as a Mentee once LFX Fall applications are open.
Also, I'm curious to know if there are any beginner-friendly issues available for me to start contributing and get to know more about Konveyor.
Any help would be highly appreciated.
Thanks!

@jwmatthews
Copy link
Member Author

Link to this project from LFX site: https://mentorship.lfx.linuxfoundation.org/project/989d0ad3-976a-4514-b2fc-34e9e6081567

@vishalrajofficial
Copy link
Contributor

I am Vishal Raj, a final year CSE student. The CNCF - Konveyor project to extend the use-case of detecting deprecated Kubernetes API usage excites me. I'm eager to contribute to this mentorship project by creating analysis rules, developing automated tests, and providing documentation for leveraging Konveyor to detect deprecated and removed Kubernetes APIs. Building Analyzer LSP Rules and curating sample applications will be my focus. Let's collaborate to enhance Konveyor and support the Kubernetes community with valuable tools and resources!

@jwmatthews
Copy link
Member Author

Note: https://github.com/devtron-labs/silver-surfer may help or at least knowing how they approach problem could be useful.

Thank you @savitharaghunathan for this suggestion

@jwmatthews
Copy link
Member Author

@github-project-automation github-project-automation bot moved this to 🆕 New in Planning Sep 18, 2023
@djzager
Copy link
Member

djzager commented Feb 14, 2024

@jwmatthews What's the status of this issue? Is it done? Should it be moved to another repo?

@jwmatthews
Copy link
Member Author

Closed via konveyor/analyzer-lsp#441

@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in Planning Feb 14, 2024
@djzager djzager added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 15, 2024
@konveyor-ci-bot konveyor-ci-bot bot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Feb 15, 2024
@konveyor-ci-bot
Copy link

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

@konveyor-ci-bot konveyor-ci-bot bot added the needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. label Feb 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
Status: ✅ Done
Development

No branches or pull requests

8 participants