![]() There was a critical security compromise of the bash script that was being downloaded as part of the coverage build: https://about.codecov.io/security-update/ beginning January 31, 2021, there were periodic, unauthorized alterations of our Bash Uploader script by a third party, which enabled them to potentially export information stored in our users' continuous integration (CI) environments. This information was then sent to a third-party server outside of Codecov’s infrastructure. The Bash Uploader is also used in these related uploaders: Codecov-actions uploader for Github, the Codecov CircleCl Orb, and the Codecov Bitrise Step (together, the “Bash Uploaders”). Therefore, these related uploaders were also impacted by this event. The altered version of the Bash Uploader script could potentially affect: Any credentials, tokens, or keys that our customers were passing through their CI runner that would be accessible when the Bash Uploader script was executed. Any services, datastores, and application code that could be accessed with these credentials, tokens, or keys. The git remote information (URL of the origin repository) of repositories using the Bash Uploaders to upload coverage to Codecov in CI. |
||
---|---|---|
.github | ||
build | ||
charts/ingress-nginx | ||
cmd | ||
deploy | ||
docs | ||
hack | ||
images | ||
internal | ||
rootfs | ||
test | ||
version | ||
.codecov.yml | ||
.gitignore | ||
.luacheckrc | ||
Changelog.md | ||
cloudbuild.yaml | ||
code-of-conduct.md | ||
CONTRIBUTING.md | ||
go.mod | ||
go.sum | ||
LICENSE | ||
Makefile | ||
mkdocs.yml | ||
OWNERS | ||
OWNERS_ALIASES | ||
README.md | ||
SECURITY.md | ||
SECURITY_CONTACTS | ||
TAG |
Help us to improve the NGINX Ingress controller completing the survey
NGINX Ingress Controller
Overview
ingress-nginx is an Ingress controller for Kubernetes using NGINX as a reverse proxy and load balancer.
Learn more about Ingress on the main Kubernetes documentation site.
Get started
See the Getting Started document.
Troubleshooting
If you encounter issues, review the troubleshooting docs, file an issue, or talk to us on the #ingress-nginx channel on the Kubernetes Slack server.
Contributing
Thanks for taking the time to join our community and start contributing!
- This project adheres to the Kubernetes Community Code of Conduct. By participating in this project, you agree to abide by its terms.
- See CONTRIBUTING.md for information about setting up your environment, the workflow that we expect, and instructions on the developer certificate of origin that we require.
- Check out the open issues.
- Join our Kubernetes Slack channel: #ingress-nginx.
Changelog
See the list of releases to find out about feature changes.
For detailed changes for each release; please check the Changelog.md file.
For detailed changes on the ingress-nginx
helm chart, please check the following CHANGELOG.md file.
Get Involved
- Contributing: Pull requests are welcome!
- Read
CONTRIBUTING.md
and check out help-wanted issues. - Submit github issues for any feature enhancements, bugs or documentation problems.
- Read
- Support: Join to Kubernetes Slack in the #ingress-nginx channel to ask questions to get support from the maintainers and other users.
- The github issues in the repository are exclusively for bug reports and feature requests.
- Discuss: Tweet using the
#IngressNginx
hashtag.
Issues
Please make sure to read the Issue Reporting Checklist before opening an issue. Issues not conforming to the guidelines may be closed immediately.