kube-merge allows merging other Kubernetes configurations into the current configuration.
Installation
pip install kube-mergeUsage
In order to merge other configs first dump the configuration to a file. For example if using the microk8s snap from Ubuntu, just dump the configuration to a file:
microk8s.kubectl config view --raw > microk8s.ymlthen simply add it:
kube-merge microk8s.ymlThis will change the default configuration, adding the clusters and users.
From there you’ll just switch the context using the regular:
kubectl config use-context ...1 maintainer
Metadata
1 maintainer
Release files for kube_merge 1.0.2
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 | |
|---|---|---|---|---|
| kube_merge-1.0.2.tar.gz | 2.4 kB | Without provenance | Details |
Release files / kube_merge-1.0.2.tar.gz
| Download URL | kube_merge-1.0.2.tar.gz |
|---|---|
| Size | 2.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5896305848c92989dac96003466d5a6943ec3c29894d8eedad06c88746201a10
|
|
BLAKE2b-256 checksum How to use checksums |
66224480af61ee2e1771b551c5752e4143c2fbdf22ed93f73025aff8364184d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/3.7
|
Security for kube_merge 1.0.2
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.
