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
ACM-6435: add pausedUntil create cluster option in CLI #2965
Conversation
Signed-off-by: Roke Jung <roke@redhat.com>
/retitle: ACM-6435: add pausedUntil create cluster option in CLI |
@rokej: This pull request references ACM-6435 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. |
/retitle ACM-6435: add pausedUntil create cluster option in CLI |
/retest |
1 similar comment
/retest |
hypershift-operator/controllers/hostedcluster/hostedcluster_controller.go
Outdated
Show resolved
Hide resolved
Co-authored-by: Bryan Cox <brcox@redhat.com>
✅ Deploy Preview for hypershift-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Signed-off-by: Roke Jung <roke@redhat.com>
Signed-off-by: Roke Jung <roke@redhat.com>
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
hypershift-operator/controllers/hostedcluster/hostedcluster_controller.go
Outdated
Show resolved
Hide resolved
Can you elaborate on the value of creating a paused cluster? how are you planning to cleanup the field? |
@rokej: This pull request references ACM-6435 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. |
@enxebre Please see the updated PR description for the value of creating a paused cluster. The dev CLI was updated as well. |
Signed-off-by: Roke Jung <roke@redhat.com>
/approve |
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
Signed-off-by: Roke Jung <roke@redhat.com>
Signed-off-by: Roke Jung <roke@redhat.com>
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bryan-cox, enxebre, rokej 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 |
/hold Revision 21c0c17 was retested 3 times: holding |
/test e2e-aws |
@rokej: The following tests failed, say
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. |
/test e2e-aws |
/unhold |
What this PR does / why we need it:
This PR is to add
pausedUntil
create cluster option inhcp
CLI to support MCE's cluster create/update Ansible automation template. https://issues.redhat.com/browse/ACM-1368MCE is integrated with Red Hat Ansible Automation Platform so that you can create prehook and posthook Ansible job instances that occur before or after creating or upgrading hive clusters. MCE should provide users same experience with hosted clusters. This requires an ability to pause cluster provisioning so that prehook job can be executed before cluster creation. MCE's cluster curator controller orchestrates this and clears the
spec.pausedUntil
from the HostedCluster and NodePools when the conditions are met.Which issue(s) this PR fixes (optional, use
fixes #<issue_number>(, fixes #<issue_number>, ...)
format, where issue_number might be a GitHub issue, or a Jira story:Fixes #
Checklist