Skip to content
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

MGMT-8357: change 'local' deployment method to 'minikube' #4642

Conversation

osherdp
Copy link
Contributor

@osherdp osherdp commented Nov 17, 2022

Since we're gonna (temporarily) have two deployment methods that have different network configuration, we should rename 'local' to 'minikube'. Then assisted-test-infra can pass its value of DEPLOY_TARGET to what assisted-service calls TARGET (seems DEPLOY_TARGET in assisted-service is already used in some other constellation).

List all the issues related to this PR

  • New Feature
  • Enhancement
  • Bug fix
  • Tests
  • Documentation
  • CI/CD

What environments does this code impact?

  • Automation (CI, tools, etc)
  • Cloud
  • Operator Managed Deployments
  • None

How was this code tested?

  • assisted-test-infra environment - I'll check the 'kind' flow locally
  • dev-scripts environment
  • Reviewer's test appreciated
  • Waiting for CI to do a full test run
  • Manual (Elaborate on how it was tested)
  • No tests needed

Checklist

  • Title and description added to both, commit and PR.
  • Relevant issues have been associated (see CONTRIBUTING guide)
  • This change does not require a documentation update (docstring, docs, README, etc)

Reviewers Checklist

  • Are the title and description (in both PR and commit) meaningful and clear?
  • Is there a bug required (and linked) for this change?
  • Should this PR be backported?

Sorry, something went wrong.

Since we're gonna (temporarily) have two deployment methods that have
different network configuration, we should rename 'local' to 'minikube'.
Then assisted-test-infra can pass its value of ``DEPLOY_TARGET`` to what
assisted-service calls ``TARGET`` (seems ``DEPLOY_TARGET`` in
assisted-service is already used in some other constellation).
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 17, 2022
@openshift-ci
Copy link

openshift-ci bot commented Nov 17, 2022

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci openshift-ci bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Nov 17, 2022
@openshift-ci
Copy link

openshift-ci bot commented Nov 17, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: osherdp

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 17, 2022
@osherdp osherdp marked this pull request as ready for review November 17, 2022 15:01
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 17, 2022
@osherdp
Copy link
Contributor Author

osherdp commented Nov 17, 2022

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 17, 2022
@openshift-ci openshift-ci bot requested review from eranco74 and rccrdpccl November 17, 2022 15:01
@rccrdpccl
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 17, 2022
@codecov
Copy link

codecov bot commented Nov 17, 2022

Codecov Report

Merging #4642 (c893c29) into master (007e488) will decrease coverage by 0.06%.
The diff coverage is n/a.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #4642      +/-   ##
==========================================
- Coverage   67.03%   66.96%   -0.07%     
==========================================
  Files         200      200              
  Lines       28194    28241      +47     
==========================================
+ Hits        18899    18912      +13     
- Misses       7594     7615      +21     
- Partials     1701     1714      +13     
Impacted Files Coverage Δ
internal/operators/manager.go 77.23% <0.00%> (-4.64%) ⬇️
internal/operators/cnv/cnv_operator.go 78.48% <0.00%> (-2.26%) ⬇️
internal/operators/odf/odf_operator.go 62.50% <0.00%> (-1.61%) ⬇️
internal/operators/cnv/manifest.go 73.41% <0.00%> (-1.59%) ⬇️
internal/operators/lvm/lvm_operator.go 76.47% <0.00%> (-1.58%) ⬇️
internal/operators/lso/ls_operator.go 10.52% <0.00%> (-0.91%) ⬇️
internal/cluster/validations/validations.go 44.44% <0.00%> (-0.75%) ⬇️
internal/host/hostutil/test_utils.go 11.22% <0.00%> (-0.06%) ⬇️
internal/ignition/ignition.go 58.05% <0.00%> (ø)
internal/operators/lvm/config.go 100.00% <0.00%> (ø)
... and 2 more

@openshift-ci
Copy link

openshift-ci bot commented Nov 17, 2022

@osherdp: 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.

@osherdp
Copy link
Contributor Author

osherdp commented Nov 17, 2022

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 17, 2022
@openshift-merge-robot openshift-merge-robot merged commit 334ca79 into openshift:master Nov 17, 2022
danielerez pushed a commit to danielerez/assisted-service that referenced this pull request Oct 15, 2023
…4642)

Since we're gonna (temporarily) have two deployment methods that have
different network configuration, we should rename 'local' to 'minikube'.
Then assisted-test-infra can pass its value of ``DEPLOY_TARGET`` to what
assisted-service calls ``TARGET`` (seems ``DEPLOY_TARGET`` in
assisted-service is already used in some other constellation).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants