Welcome to kploy, an opinionated Kubernetes deployment system for appops. We use convention over configuration in order to enable you to run microservices-style applications with Kubernetes as simple and fast as possible.
Usage
See kubernetes.sh/kploy for installation and usage.
Dependencies
All of the following are included in the setup:
Releases
[x] In v0.10: adds experimental push and pull command via KAR
[x] In v0.9: adds scale command (autoscale yet TBD)
[x] In v0.8: adds debug command, some refactoring
[x] In v0.7: adds support for environment data: automagic handling of Kubernetes Secrets on run
[x] In v0.6: export command creates snapshot of app; can be imported when doing init
[x] In v0.5: simple support for helm charts via remotes (*.url)
[x] In v0.4: support for namespaces (via namespace field in Kployfile)
[x] In v0.3: moved to Kubernauts org, new location is https://github.com/kubernauts/kploy
[x] In v0.2: init command and app management: resources via list and runtime statistics via stats
[x] In v0.1: dryrun and run commands
Roadmap
kploy is now considered beta. This means the goal is now to stabilize the API, gather usage experience and community feedback. See the issue list for further planned features.
Metadata
Release files for kploy 0.10.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| kploy-0.10.1.tar.gz | 11.5 kB | Without provenance | Details |
Release files / kploy-0.10.1.tar.gz
| Download URL | kploy-0.10.1.tar.gz |
|---|---|
| Size | 11.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ebedb5fc914e023b714c914845744d7321f48d29522921272183174ef86a5a91
|
|
BLAKE2b-256 checksum How to use checksums |
30a8dd4a3c71b6c0df2ad1b73d86735da7141dd6e87ecf9d1d041590aedc4a18
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for kploy 0.10.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.