Skip to content

Update README with additional PR links #71

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
guettli merged 2 commits into from
Nov 3, 2025
Merged

Update README with additional PR links #71

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2621a1a
Update README with additional PR links
guettli Nov 3, 2025
af14bef
Revise README with PRs for upstream integration
guettli Nov 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,7 @@ Instead we plan to create PRs in upstream, so that our fork is no longer needed.

Features/PRs which are different in our fork. We should create PRs in upstream for these:

* [Hot Reload for secrets](https://github.com/syself/hetzner-cloud-controller-manager/pull/49)
* [separate user agent from HCCM](https://github.com/syself/hetzner-cloud-controller-manager/pull/42): Make this configurable in upstream.
* [ROBOT_DEBUG, show stacktrace on api-calls](https://github.com/syself/hetzner-cloud-controller-manager/pull/41>) Via ROBOT_DEBUG show every stack-trace which uses the robot-API (to debug why rate-limiting was reached)
* [PR add version information to the controller binary](https://github.com/syself/hetzner-cloud-controller-manager/pull/28): Build process is different in upstream.
Expand Down