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

Pivoting to new operator implementation #232

Conversation

yevgeny-shnaidman
Copy link
Contributor

Starting from this commit, operator will use the new controller implementation. The old implementation code will be deleted in the subsequent PRs

Starting from this commit, operator will use the new controller
implementation. The old implementation code will be deleted in the
subsequent PRs
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label May 15, 2024
@k8s-ci-robot k8s-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label May 15, 2024
@yevgeny-shnaidman
Copy link
Contributor Author

/assign @marquiz

@marquiz
Copy link
Contributor

marquiz commented May 15, 2024

Thanks @yevgeny-shnaidman for the PR. I'll check it in detail a bit later. First question (after a 30s skim-through): are the logger changes related/dependent on this (or could they be a separate PR)?

@yevgeny-shnaidman
Copy link
Contributor Author

Thanks @yevgeny-shnaidman for the PR. I'll check it in detail a bit later. First question (after a 30s skim-through): are the logger changes related/dependent on this (or could they be a separate PR)?

They are dependent on switching to the new controller. Unless we do them, we will see some warnings in the manager log

@marquiz
Copy link
Contributor

marquiz commented May 16, 2024

They are dependent on switching to the new controller. Unless we do them, we will see some warnings in the manager log

Kinda useless nitting, but where do we get warnings? Looking at the PR now we only change logger in main.go which shouldn't affect any other parts of the codebase 🧐 So it looks to me like the logger changes could/should be just a separate PR.

@yevgeny-shnaidman
Copy link
Contributor Author

They are dependent on switching to the new controller. Unless we do them, we will see some warnings in the manager log

Kinda useless nitting, but where do we get warnings? Looking at the PR now we only change logger in main.go which shouldn't affect any other parts of the codebase 🧐 So it looks to me like the logger changes could/should be just a separate PR.

We get the warning in the manager log, but those warnings are coming from the controller-runtime code. I can split this PR into 2 ( first the actual pivot and then the logging PR), but i wanted to keep it altogether so that after this PR the operator can be seen deployed and running with logs.

Copy link
Contributor

@marquiz marquiz left a comment

Choose a reason for hiding this comment

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

Thanks @yevgeny-shnaidman. I'm good to merge this as is

/assign @ArangoGutierrez

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: marquiz, yevgeny-shnaidman

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 16, 2024
@yevgeny-shnaidman
Copy link
Contributor Author

ping @ArangoGutierrez

@ArangoGutierrez
Copy link
Contributor

ping @ArangoGutierrez

Sorry I was traveling last week, will review this one this week

@yevgeny-shnaidman
Copy link
Contributor Author

/ping @ArangoGutierrez

@yevgeny-shnaidman
Copy link
Contributor Author

ping @ArangoGutierrez

@marquiz
Copy link
Contributor

marquiz commented May 29, 2024

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 29, 2024
@k8s-ci-robot k8s-ci-robot merged commit 7654a84 into kubernetes-sigs:master May 29, 2024
7 checks passed
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. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants