Cilium Microscope
Cilium microscope allows you to see cilium monitor output from all your cilium nodes. This allows you to have one simple to use command to interact with your cilium nodes within k8s cluster.
Running microscope in your Kubernetes cluster
kubectl create -f docs/microscope.yaml will create a pod in your kube-system namespace to which you can connect to run microscope with kubectl exec -n kube-system microscope sh.
Alternatively, you can use kubectl run -i --tty microscope --image cilium/microscope --restart=Never -- sh.
In any case you will end up with a shell inside microscope pod. microscope -h inside this shell will show microscope help.
Running microscope locally
To run microscope locally, you need to have Python 3.5 or newer installed. Using virtualenv is recommended, but not necessary.
microscope is available as a package in PyPI, so all you need to do is run pip install cilium-microscope. microscope executable should be available in your path.
Alternatively you can run make to build self-contained Python archive which will container all dependencies and requires only Python to run.
The archive will be located in dist/microscope.pyz, and should be executable directly.
2 maintainers
Metadata
2 maintainers
Release files for cilium-microscope 0.1.6
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 | |
|---|---|---|---|---|
| cilium-microscope-0.1.6.tar.gz | 8.5 kB | Without provenance | Details |
Release files / cilium-microscope-0.1.6.tar.gz
| Download URL | cilium-microscope-0.1.6.tar.gz |
|---|---|
| Size | 8.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fbf5f6c29f0b449689c87e68e99ae56f2f9ea854b3848904eebdadf86d5a40cf
|
|
BLAKE2b-256 checksum How to use checksums |
c669e38b510812d637c401ac0c6b59a9a83a97461964b92c805f36b26d693272
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cilium-microscope 0.1.6
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.
