-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Update v2 > v3 migration guide #10728
base: v3.0
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @0anas01, thanks a lot for this first step. We need a few more changes on this section, we will get back to you ASAP once we have the complete plan.
Co-authored-by: Kevin Pollet <pollet.kevin@gmail.com>
Co-authored-by: Kevin Pollet <pollet.kevin@gmail.com>
How about we keep the configuration changes on a separate page and link to it in the migration guide? |
I haven't seen this comment before, but this could simplify the structure of this documentation. I would vote for it. |
Co-authored-by: Emile Vauge <emile@vauge.com>
docs/content/migration/v2-to-v3.md
Outdated
@@ -564,7 +666,7 @@ For this reason, we encourage migrating to the new syntax. | |||
|
|||
By default, the `defaultRuleSyntax` static option is automatically set to `v3`, meaning that the default rule is the new one. | |||
|
|||
#### New V3 Syntax Notable Changes | |||
##### New V3 Syntax Notable Changes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please take into account the following comment #10690 (comment)
What does this PR do?
This PR is documentation fix for Traefik v2 to v3 migration guide.