Thank you for considering contributing to k8s-stuck-pod-cleaner! This document provides guidelines and instructions for contributing.
By participating in this project, you agree to maintain respectful communication and inclusive behavior.
If you find a bug or have a suggestion for improvement:
- Check if the issue already exists in the GitHub Issues
- If not, create a new issue with:
- A clear title
- A detailed description
- Steps to reproduce (for bugs)
- Expected behavior
- Current behavior
- Any relevant logs or screenshots
- Fork the repository
- Create a new branch for your changes (
git checkout -b feature/your-feature-name
) - Make your changes
- Test your changes:
- Apply the YAML in a test Kubernetes cluster
- Verify the CronJob runs correctly
- Verify pods are properly cleaned up
- Commit your changes with a clear commit message
- Push to your branch
- Submit a Pull Request
- Update the README.md with details of changes if applicable
- Increase version numbers if applicable
- The PR will be merged once it is approved by a maintainer
- Keep the YAML file as a single file for easy deployment
- Use clear comments to document each section
- Follow Kubernetes best practices for resource naming and configuration
- Add clear comments for each section of the script
- Include proper error handling
- Implement verbose logging for debugging
- Use consistent indentation and style
Before submitting a PR, test your changes in a Kubernetes environment:
- Apply the YAML to a test cluster
- Create test pods that will enter a Terminating state
- Verify the CronJob correctly identifies and cleans up stuck pods
- Check the events to ensure proper recording
Your contributions help make Kubernetes administration easier for everyone!