sigs.k8s.io/kpng/server
KPNG converts a number of input sources into backend destinations, and because of this, there need to be a number of separate jobs which KPNG runs depending on user intent.
Typically a user defines:
Then, the KPNG server (or "spine") connects these inputs and outputs. The process which runs this connection is a "job".
For example, the "kube2store" job runs a process which continually watches the
ubernetes APIServer.
The "store2api" job watches the in memory store of the kpng network model and publishes it as an api for others to consume, and so on.
These jobs are invoked from the wrapper programs in the cmd/kpng/ package, for example k2s, f2s, and so on.
FAQs
Unknown package
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Company News
Socket is joining TC54 to help develop standards for software supply chain security, contributing to the evolution of SBOMs, CycloneDX, and Package URL specifications.
Security News
PyPI now allows maintainers to archive projects, improving security and helping users make informed decisions about their dependencies.
Research
Security News
Malicious npm package postcss-optimizer delivers BeaverTail malware, targeting developer systems; similarities to past campaigns suggest a North Korean connection.
