-
Notifications
You must be signed in to change notification settings - Fork 153
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
Consume operator-sdk 1.1.0 #898
Conversation
All tests passed |
1 similar comment
All tests passed |
/hold |
All tests passed |
hco-e2e-image-index-gcp, hco-e2e-image-index-aws lanes succeeded. |
@hco-bot: Overrode contexts on behalf of hco-bot: ci/prow/hco-e2e-image-index-azure 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. |
All tests passed |
8 similar comments
All tests passed |
All tests passed |
All tests passed |
All tests passed |
All tests passed |
All tests passed |
All tests passed |
All tests passed |
/retest |
All tests passed |
/retest |
1 similar comment
/retest |
/retest |
1 similar comment
/retest |
All tests passed |
2 similar comments
All tests passed |
All tests passed |
I'd expect openshift/release#13355 to fix the issues with hco-e2e-image-index-* lanes |
hco-e2e-image-index-* got indeed fixed by openshift/release#13355 for instance, we ended up with the old version of the operator and the new one running at the same time: hco-operator-5d9547f8b-rhd7k 1/1 Running 0 13m With the new version not really able to start due to:
|
All tests passed |
2 similar comments
All tests passed |
All tests passed |
/unhold |
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.
Two small comments/questions
@@ -73,15 +59,16 @@ func main() { | |||
// implementing the logr.Logger interface. This logger will | |||
// be propagated through the whole operator, generating | |||
// uniform and structured logs. | |||
logf.SetLogger(zap.Logger()) | |||
development_mode_logger := false // use a production logger |
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.
Why do we need this variable? what about using an environment variable (default = false) for that?
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.
sigs.k8s.io/controller-runtime/pkg/log already provides CLI options, using them instead of an hardcoded value
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.
But why use a boolean parameter just in order to use it as a value in the next line?
Why not just
logf.SetLogger(zap.New(zap.UseDevMode(false)))
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.
sorry, I commented before pushing.
the last version is just logf.SetLogger(zap.New(zap.UseFlagOptions(zopts)))
to consume the CLI flags parsed on zopts
operator-sdk >= v1.0.0 introduces various not backward compatible changes. Aligning with that. See: https://v1-1-x.sdk.operatorframework.io/docs/upgrading-sdk-version/v1.0.0/ https://v1-1-x.sdk.operatorframework.io/docs/upgrading-sdk-version/v1.1.0/ for the migrations guides. Relevant changes in the operator sdk: - Removed package pkg/k8sutil - Removed packages pkg/kube-metrics and pkg/metrics - Removed package pkg/ready - Package version is no longer public - pkg/log/zap is no longer a public API Moving from Leader-for-life to Leader-with-lease from controller runtime to avoid a deadlock on rolling upgrades. Signed-off-by: Simone Tiraboschi <[email protected]>
All tests passed |
@tiraboschi: 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. |
/override-bot |
hco-e2e-azure lane succeeded. |
@hco-bot: Overrode contexts on behalf of hco-bot: ci/prow/hco-e2e-aws, ci/prow/hco-e2e-image-index-azure, ci/prow/hco-e2e-upgrade-azure, ci/prow/hco-e2e-upgrade-prev-azure 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. |
/lgtm |
[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 |
Remove a small hack introduced only to be able to easily test #898 on CI Signed-off-by: Simone Tiraboschi <[email protected]>
operator-sdk >= v1.0.0 introduces various not backward
compatible changes.
Aligning with that.
See:
https://v1-1-x.sdk.operatorframework.io/docs/upgrading-sdk-version/v1.0.0/
https://v1-1-x.sdk.operatorframework.io/docs/upgrading-sdk-version/v1.1.0/
for the migrations guides.
Relevant changes in the operator sdk:
Moving from Leader-for-life to Leader-with-lease from
controller runtime to avoid a deadlock on rolling upgrades.
Signed-off-by: Simone Tiraboschi [email protected]
Release note: