This release is a pre-release and may not be stable for production use.
Python client for kubernetes http://kubernetes.io/
Metadata
Release files for kubernetes 4.0.0a1
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 | |
|---|---|---|---|---|
| kubernetes-4.0.0a1.tar.gz | 439.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kubernetes-4.0.0a1-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 1.5 MB
Release files / kubernetes-4.0.0a1.tar.gz
| Download URL | kubernetes-4.0.0a1.tar.gz |
|---|---|
| Size | 439.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3f23c1d526dcbd4229383c685ff4947a0e943aaed0eea03878ef423ceb643078
|
|
BLAKE2b-256 checksum How to use checksums |
cf1d6ee7dd699e3476be2b4393e32f1b16ff4f53bd8463421dbec961c0c2329e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / kubernetes-4.0.0a1-py2.py3-none-any.whl
| Download URL | kubernetes-4.0.0a1-py2.py3-none-any.whl |
|---|---|
| Size | 1.0 MB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
b0c6f2bb3cc68bb46edbab4e7d1ed0338b723263ea6f1fb3c048f0156aa618c2
|
|
BLAKE2b-256 checksum How to use checksums |
66b8566227e0ef0b52b412cb30639b4c96d2768b0dd248c12ba466c1658e8c2a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for kubernetes 4.0.0a1
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.