Simple script to ping given clusters using a given kube config. Results are save to a yaml file in /tmp
This is a simple script to check if the user defined in a given kube config can ping the given cluster. The result are currently saved to a yaml file in the operating systems temporary directory.
It is recommended to use pipx to manage the installation.
pipx install cluster_ping
The cluster_ping command should then be in the path.
cluster_ping --help
This will list the help and prove the installation was complete.
By running the cluster_ping with the path to a kude config and the name of a cluster a yaml file is created with the results of the ping.
This file is created in the standard temporary directory for the OS.
On Linux this is /tmp/.
cluster_ping <Path/to/kube/confing> <Cluster Name>
The change log is managed by towncrier.
The use of pre-commit is used to set up git hooks.
Use pre-commit install to install the hooks.
To run the hooks outside a commit using pre-commit run -a.
pytest is the test runner.
Run tests with pytest.
towncrier build --draft and review the outpout.bat cluster_ping/__init__.pytowncrier build to update the change logCHANGELOG.mdpoetry publish --buildFAQs
Simple script to ping given clusters using a given kube config. Results are save to a yaml file in /tmp
We found that cluster-ping demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
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
PyPI confirms no security flaws were exploited in the Ultralytics supply chain attack and highlights improvements for safer package publishing.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.