Open jonathan-innis opened 10 months ago
/kind documentation
@jonathan-innis @sftim, I am interested in working on this issue but need guidance as I haven't gone through the code.
@srijan-shukla and I discussed a bit offline. This one may be tough if you don't already have deep familiarity with the codebase. I'd recommend picking up some issues that fall under good-first-issues first to get better familiarity and then come back to this one after you've gotten your feet wet a bit.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
Thanks for the opportunity. I will be working on the architecture diagram
/assign @sanjeevrg89
/lifecycle fresh
/remove-lifecycle rotten
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
Description
There have been a few requests from users to better understand how Karpenter runs under the hood and how the different controllers interact with each other. It might be nice to have a high-level architecture diagram that we could point users to when they ask how Karpenter works.