-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HAProxy router option persist #52922
Comments
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/remove-lifecycle rotten |
/lifecycle frozen |
/reopen |
@thomaswoeckinger: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Our documentation team cannot document this as an option until the code itself is merged. It looks like openshift/router#420 was closed due to some issues getting this through the RFE process. @candita @frobware @Miciah Can you please revisit this and help this through the RFE process? |
@ahardin-rh the issue went rotten, and the code wasn't merged so the docs don't need to be merged. As far as I can tell, this PR can be closed as well. |
Which section(s) is the issue in?
Modules, Network route specific annotations
What needs fixing?
Documentation for option persist added by pull request openshift/router#420
The text was updated successfully, but these errors were encountered: