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
AGENT-557: Split register into registerCluster and registerInfraEnv #5376
Conversation
@rwsu: This pull request references AGENT-557 which is a valid jira 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. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rwsu 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 |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #5376 +/- ##
==========================================
+ Coverage 67.59% 67.90% +0.31%
==========================================
Files 226 226
Lines 33304 34044 +740
==========================================
+ Hits 22513 23119 +606
- Misses 8758 8876 +118
- Partials 2033 2049 +16
|
The split is desired to enable the interactive flow. Users will register the cluster through the GUI instead of including the cluster information in the ignition/agent ISO. registerCluster is able to detect if a cluster has already been registered with the REST-API and exits with status 0, skipping cluster registration from manifest files. registerInfraEnv requires and checks that a cluster has been registered with the REST-API. It also skips infraenv registration if it detects one has already been created. Signed-off-by: Richard Su <rwsu@redhat.com>
The service has been removed and split into agent-register-cluster.service agent-register-infraenv.service Both services continuously retries until their respective resource has been registered with the assisted-service REST-API or if the client sees that a resource as already been registered. Requires: openshift/assisted-service#5376 Signed-off-by: Richard Su <rwsu@redhat.com>
/retest-required |
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.
/lgtm
/test edge-subsystem-kubeapi-aws |
@rwsu: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
The service has been removed and split into agent-register-cluster.service agent-register-infraenv.service Both services continuously retries until their respective resource has been registered with the assisted-service REST-API or if the client sees that a resource as already been registered. Requires: openshift/assisted-service#5376 Signed-off-by: Richard Su <rwsu@redhat.com>
…penshift#5376) The split is desired to enable the interactive flow. Users will register the cluster through the GUI instead of including the cluster information in the ignition/agent ISO. registerCluster is able to detect if a cluster has already been registered with the REST-API and exits with status 0, skipping cluster registration from manifest files. registerInfraEnv requires and checks that a cluster has been registered with the REST-API. It also skips infraenv registration if it detects one has already been created. Signed-off-by: Richard Su <rwsu@redhat.com>
The service has been removed and split into agent-register-cluster.service agent-register-infraenv.service Both services continuously retries until their respective resource has been registered with the assisted-service REST-API or if the client sees that a resource as already been registered. Requires: openshift/assisted-service#5376 Signed-off-by: Richard Su <rwsu@redhat.com>
…penshift#5376) The split is desired to enable the interactive flow. Users will register the cluster through the GUI instead of including the cluster information in the ignition/agent ISO. registerCluster is able to detect if a cluster has already been registered with the REST-API and exits with status 0, skipping cluster registration from manifest files. registerInfraEnv requires and checks that a cluster has been registered with the REST-API. It also skips infraenv registration if it detects one has already been created. Signed-off-by: Richard Su <rwsu@redhat.com>
The service has been removed and split into agent-register-cluster.service agent-register-infraenv.service Both services continuously retries until their respective resource has been registered with the assisted-service REST-API or if the client sees that a resource as already been registered. Requires: openshift/assisted-service#5376 Signed-off-by: Richard Su <rwsu@redhat.com>
The service has been removed and split into agent-register-cluster.service agent-register-infraenv.service Both services continuously retries until their respective resource has been registered with the assisted-service REST-API or if the client sees that a resource as already been registered. Requires: openshift/assisted-service#5376 Signed-off-by: Richard Su <rwsu@redhat.com>
The split is desired to enable the interactive flow. Users will register the cluster through the GUI instead of including the cluster information in the ignition/agent ISO.
registerCluster is able to detect if a cluster has already been registered with the REST-API and exits with status 0, skipping cluster registration from manifest files.
registerInfraEnv requires and checks that a cluster has been registered with the REST-API. It also skips infraenv registration if it detects one has already been created.
List all the issues related to this PR
What environments does this code impact?
How was this code tested?
Checklist
docs
, README, etc)Reviewers Checklist