Skip to content

Update the repo structure #6

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.

Sign up for GitHub

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

Open
CsatariGergely wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update the repo structure #6

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
126368a
Update the repo structure
CsatariGergely May 30, 2025
f363a56
Unmentioning the Typescript and Starlak SDKs
CsatariGergely Jun 5, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions profile/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,5 +40,15 @@ We have a kpt users [mailing list](https://groups.google.com/forum/?oldui=1#!for
## Repository structure

- [kpt](https://github.com/kptdev/kpt): The main logic of kpt.
- [krm-function-catalog](https://github.com/kptdev/krm-functions-catalog): A [catalog](https://catalog.kpt.dev/) of
off-the-shelf, tested functions. kpt makes configuration easy to create and transform, via reusable functions. Because
they are expected to be used for in-place transformation, the functions need to be idempotent.
- [krm-function-sdk](https://github.com/kptdev/krm-functions-sdk): Any general-purpose or domain-specific language can
be used to create functions to transform and/or validate the YAML KRM input/output format, but we provide SDKs to
Copy link

@kispaljr kispaljr Jun 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since go will be the only maintained SDK for a while, I suugest:

"Any general-purpose or domain-specific language can be used to create functions to transform and/or validate the YAML KRM input/output format, but in this repository we provide an SDK to simplify the function authoring process specifically in Go

Copy link
Contributor Author

@CsatariGergely CsatariGergely Jun 5, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've modified it to

"Any general-purpose or domain-specific language can be used to create functions to transform and/or validate the YAML KRM input/output format, but in this repository we provide an SDK to simplify the function authoring process in Go"

in f363a56

simplify the function authoring process in [Go](https://kpt.dev/book/05-developing-functions/02-developing-in-Go).
- [kpt-backstage-plugins](https://github.com/kptdev/kpt-backstage-plugins): We've created a proof-of-concept UI in the
Copy link
Member

@ciaranjohnston ciaranjohnston Nov 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This repository is archived, should we mention that? Or, why include it here?

form of a [Backstage UI plugin](https://github.com/kptdev/kpt-backstage-plugins) to demonstrate the WYSIWYG
experience that's possible on top of the package orchestrator. More scenarios can be supported by implementing
form-based editors for additional Kubernetes resource types.
- [governance](https://github.com/kptdev/governance): Governance of the kpt project.
- [.github](https://github.com/kptdev/.github): GitHub organisation level settings (this repo)