-
Notifications
You must be signed in to change notification settings - Fork 200
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
refactor porter #132
refactor porter #132
Conversation
1. Eip Address Management via CRD 2. refactor Porter High Availability 3. Changes to the BgpConf/BgpPeer API to be compatible with the gobgp API and to support viewing status. 4. Some other changes Signed-off-by: Duan Jiong <[email protected]>
/assign @zheng1 |
metadata: | ||
#The porter only recognizes configurations with default names; | ||
#configurations with other names are ignored. | ||
name: default |
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.
How about set the name to porter
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.
This is fine, but the name default
is used both in the code and in the documentation, so I don't want to change it, and it's not really perceptible to the user when it's configured through the UI.
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: duanjiong, zheng1 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Here is some error
|
There was an indentation error, the keyboard mishandled when I submitted it. |
@Patrick-LuoYu @duanjiong @zheng1 Do we have the relevant guides for these two features in v0.4.0? How to test them from the end user side? |
End-users look at the documentation on the line, unclear we improve the documentation, there are problems with the issue we fix on the line, with the use of documentation is also a test, why do we have to get a separate set of test cases. |
Signed-off-by: Duan Jiong [email protected]