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

Switch to use the new SSP operator #966

Merged
merged 14 commits into from
Jan 7, 2021
Merged

Conversation

zcahana
Copy link
Contributor

@zcahana zcahana commented Nov 26, 2020

This PR updates HCO operator to use the new Golang-based SSP operator, instead of the old Ansible-based SSP operator.

Note 1: This isn't mergeable yet, since the new SSP operator doesn't have a released image yet.
Note 2: I plan to add additional unit tests to cover the upgrade logic (removal of old CRDs, etc).

Switch to use the new SSP operator.

@kubevirt-bot kubevirt-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Nov 26, 2020
@@ -3,289 +3,125 @@ package operands
import (
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Github's diff view of this file is terrible.
In essence, this file has been rewritten from scratch, so it better be viewed as a whole file, and compared to the old file as a whole.

@@ -32,6 +31,7 @@ import (
apiruntime "k8s.io/apimachinery/pkg/runtime"
_ "k8s.io/client-go/plugin/pkg/client/auth/gcp"
cdiv1beta1 "kubevirt.io/containerized-data-importer/pkg/apis/core/v1beta1"
sspv1alpha1 "kubevirt.io/ssp-operator/api/v1alpha1"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I fear we can accept it only if >= v1beta1

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the criteria to move from v1alpha1 to v1beta1? Or this is merely a syntactical requirement?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The criteria is:

Since it is a "beta" suffixed, it should work with subsequent releases. Indeed, the meaning of api versions is as following:

alpha
API versions with ‘alpha’ in their name are early candidates for new functionality coming into Kubernetes. These may contain bugs and are not guaranteed to work in the future.

beta
‘beta’ in the API version name means that testing has progressed past alpha level, and that the feature will eventually be included in Kubernetes. Although the way it works might change, and the way objects are defined may change completely, the feature itself is highly likely to make it into Kubernetes in some form.

stable
These do not contain ‘alpha’ or ‘beta’ in their name. They are safe to use.

an operator is required to have it's CRD at least to v1beta1 to be considered GA as our previous version was.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The API version of ssp-operator is now v1beta1.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@akrejcir thanks, will update this PR to consume v1beta1.

Copy link
Collaborator

@nunnatsa nunnatsa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Starting the review. Currently - two comments.

pkg/controller/operands/ssp.go Outdated Show resolved Hide resolved
pkg/controller/operands/ssp.go Outdated Show resolved Hide resolved
@zcahana
Copy link
Contributor Author

zcahana commented Nov 30, 2020

Rebased + several updates.

@kubevirt-bot kubevirt-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 2, 2020
@kubevirt-bot kubevirt-bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 6, 2020
@zcahana zcahana force-pushed the new_ssp branch 2 times, most recently from 9f12f63 to b581156 Compare December 7, 2020 10:16
@kubevirt-bot kubevirt-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 8, 2020
@kubevirt-bot kubevirt-bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 9, 2020
@zcahana
Copy link
Contributor Author

zcahana commented Dec 10, 2020

/test pull-hyperconverged-cluster-operator-e2e-k8s-1.17

@openshift-ci-robot
Copy link
Collaborator

@zcahana: The specified target(s) for /test were not found.
The following commands are available to trigger jobs:

  • /test ci-index
  • /test hco-e2e-aws
  • /test hco-e2e-azure
  • /test hco-e2e-image-index-aws
  • /test hco-e2e-image-index-azure
  • /test hco-e2e-image-index-gcp
  • /test hco-e2e-upgrade-aws
  • /test hco-e2e-upgrade-azure
  • /test hco-e2e-upgrade-prev-aws
  • /test hco-e2e-upgrade-prev-azure
  • /test images

Use /test all to run all jobs.

In response to this:

/test pull-hyperconverged-cluster-operator-e2e-k8s-1.17

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.

@tiraboschi
Copy link
Member

/retest

@kubevirt-bot kubevirt-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 10, 2020
@kubevirt-bot kubevirt-bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 13, 2020
@zcahana zcahana force-pushed the new_ssp branch 4 times, most recently from 75cccb4 to 4a7d341 Compare December 14, 2020 17:18
@kubevirt-bot kubevirt-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 15, 2020
@kubevirt-bot kubevirt-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 7, 2021
@kubevirt-bot kubevirt-bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 7, 2021
Copy link
Collaborator

@nunnatsa nunnatsa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@kubevirt-bot kubevirt-bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jan 7, 2021
@openshift-ci
Copy link

openshift-ci bot commented Jan 7, 2021

@zcahana: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/hco-e2e-image-index-gcp bb7e141a62ade0f7ce30399b1b7fc9efca742f73 link /test hco-e2e-image-index-gcp
ci/prow/hco-e2e-upgrade-aws 414c3a1 link /test hco-e2e-upgrade-aws
ci/prow/hco-e2e-upgrade-azure 414c3a1 link /test hco-e2e-upgrade-azure

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.

@nunnatsa
Copy link
Collaborator

nunnatsa commented Jan 7, 2021

/override ci/prow/hco-e2e-upgrade-aws
/override ci/prow/hco-e2e-upgrade-azure

Failure is expected

/override ci/prow/hco-e2e-image-index-gcp
hco-e2e-image-index-azure hco-e2e-image-index-aws passed

@kubevirt-bot
Copy link
Contributor

@nunnatsa: Overrode contexts on behalf of nunnatsa: ci/prow/hco-e2e-image-index-gcp, ci/prow/hco-e2e-upgrade-aws, ci/prow/hco-e2e-upgrade-azure

In response to this:

/override ci/prow/hco-e2e-upgrade-aws
/override ci/prow/hco-e2e-upgrade-azure

Failure is expected

/override ci/prow/hco-e2e-image-index-gcp
hco-e2e-image-index-azure hco-e2e-image-index-aws passed

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.

Copy link
Collaborator

@nunnatsa nunnatsa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@tiraboschi
Copy link
Member

/unhold

@kubevirt-bot kubevirt-bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 7, 2021
@kubevirt-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nunnatsa

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

@kubevirt-bot kubevirt-bot merged commit 7fb5927 into kubevirt:master Jan 7, 2021
@zcahana zcahana deleted the new_ssp branch January 7, 2021 18:56
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. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XXL
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants