-
Notifications
You must be signed in to change notification settings - Fork 23
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
Recover lost broker-info.subm #467
Conversation
🤖 Created branch: z_pr467/Jaanki/broker_cluster_info |
c1ec8e1
to
87bea21
Compare
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.
The PR description mentions that this simplifies code in a number of places, the PR should demonstrate this.
722270c
to
14f9a7d
Compare
14f9a7d
to
73ebe68
Compare
73ebe68
to
d12c8ad
Compare
d12c8ad
to
1345c16
Compare
1345c16
to
a9b6afb
Compare
98e607a
to
58ffa3b
Compare
58ffa3b
to
d350bb0
Compare
9a001b9
to
9338667
Compare
9338667
to
7f0de1e
Compare
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.
Some comments
metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" | ||
) | ||
|
||
func RecoverData( |
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.
You missed the point, if you use a single function and feed it the necessary parameters, should the broker info change then both callers will be either doing the same thing or would both need to be updated.
If you use seperate functions, the changes need to be remembered to be made in both by devs (which i can guarantee wont happen)
I have reused data.writeToFile that broker.WriteInfoToFile also uses to write the collected data to broker-info.subm
That just outputs the info to file, nothing fancy
6523425
to
89f061e
Compare
The commit message doesn't make much sense right now:
|
This PR does the following: 1. Adds a `subctl recover-broker-info` command to recover broker-info.subm file from an existing cluster setup 2. Adds logic to collect necessary information from Broker and Submariner clusters to populate broker-info.subm file 3. Add system tests for various scenarios Epic: submariner-io/enhancements#143 Signed-off-by: Janki Chhatbar <[email protected]>
89f061e
to
c314237
Compare
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.
Please make sure to update design and remove the --broker
flags
🤖 Updating dependent PRs: #588 |
🤖 Closed branches: [z_pr467/Jaanki/broker_cluster_info] |
Release notes are here: #630 |
Since there are multiple places where a broker installation check on a cluster is needed in multiple places (show brokers, uninstall and recover-brokerinfo (soon)), add broker field as part of the clusterinfo and a function that checks if the cluster has Broker installed.
This simplies code at multiple places.
Depends on: submariner-io/submariner-operator#2432
Signed-off-by: Janki Chhatbar [email protected]