This project is a component of the Operator Framework, an open source toolkit
to manage Kubernetes native applications, called Operators, in an effective,
automated, and scalable way. Read more in the introduction blog post.
Operators make it easy to manage complex stateful applications on top of
Kubernetes. However writing an Operator today can be difficult because of
challenges such as using low level APIs, writing boilerplate, and a lack of
modularity which leads to duplication.
The Operator SDK is a framework that uses the controller-runtime library to
make writing operators easier by providing:
* High level APIs and abstractions to write the operational logic more
intuitively
* Tools for scaffolding and code generation to bootstrap a new project fast
* Extensions to cover common Operator use cases
Paths come from the repository package-file index for the observed builds. They describe archive/package associations, not every file that will exist on a running system after maintainer scripts, alternatives, generated state, diversions, or installation choices.
Each row is recorded package-index metadata for one version, architecture, suite, and repository. Names, URLs, and sizes are source-reported; a link is a potentially mutable retrieval location, not an OpenFactory redistribution claim or proof that OpenFactory retained the artifact bytes.