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

Upgrade Kubebuilder dep from 3.4.1 to the commit 800fdeec6e5c #5814

Merged

Conversation

camilamacedo86
Copy link
Contributor

@camilamacedo86 camilamacedo86 commented May 29, 2022

Description

Goal

Only to get the changes from what we currently use in SDK from kubebuilder.

Motivation:

  • Ensure that scaffolds begin to be performed with a restrive Security Context
  • Be able to do specific follow up PR so we can discuss properly how we will consume the new additions on Kubebuilder
  • Make eaiser the process to keep SDK updated, otherwise, it is hard to properly review if we wait to do a big PR with all.
  • Ensure that SDK features can work with the latest changes performed in Kubebuilder

Extra info
You can check the latest changes on Kubebuilder by looking: kubernetes-sigs/kubebuilder@v3.4.1...master

Note that SDK users Kubebuilder as a LIB. So that all that is currently important is updated by default when we bump. However, all that was added to Kubebuilder but still not imported/used in SDK will not be added here. Therefore we can do follow up PRs to get the additions. Why? we have significant changes and additions for example adding the support for the phase 2 plugin, but if we try to do it all in the same PR it will be very hard to get properly reviewed.

@camilamacedo86 camilamacedo86 changed the title Bump Kubebuilder master to catchup with the latest changes (not that we are just updating here what is currently used by SDK and not importing the new additions in Kubebuilder) Bump Kubebuilder master to catchup with the latest changes May 29, 2022
@camilamacedo86 camilamacedo86 changed the title Bump Kubebuilder master to catchup with the latest changes Bump Kubebuilder to catch up with the latest changes May 29, 2022
@camilamacedo86 camilamacedo86 changed the title Bump Kubebuilder to catch up with the latest changes WIP : Bump Kubebuilder to catch up with the latest changes May 29, 2022
@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 May 29, 2022
@camilamacedo86 camilamacedo86 changed the title WIP : Bump Kubebuilder to catch up with the latest changes WIP : Upgrade Kubebuilder dep from 3.4.1 to the commit 800fdeec6e5c May 29, 2022
@camilamacedo86 camilamacedo86 changed the title WIP : Upgrade Kubebuilder dep from 3.4.1 to the commit 800fdeec6e5c Upgrade Kubebuilder dep from 3.4.1 to the commit 800fdeec6e5c May 29, 2022
@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 May 29, 2022
go.mod Show resolved Hide resolved
@jmrodri
Copy link
Member

jmrodri commented Jun 7, 2022

@camilamacedo86 not sure if you want to include java in this PR or not. But v0.5.0 was released: https://github.com/operator-framework/java-operator-plugins/releases/tag/v0.5.0

@camilamacedo86
Copy link
Contributor Author

@jmrodri the https://github.com/operator-framework/java-operator-plugins/releases/tag/v0.5.0 is using k8s 1.24 so I think it goes in the follow up where we will bump all to use these versions.

changelog/fragments/kb-800fdeec6e5c.yaml Outdated Show resolved Hide resolved
changelog/fragments/kb-800fdeec6e5c.yaml Outdated Show resolved Hide resolved
changelog/fragments/kb-800fdeec6e5c.yaml Outdated Show resolved Hide resolved
changelog/fragments/kb-800fdeec6e5c.yaml Outdated Show resolved Hide resolved
changelog/fragments/kb-800fdeec6e5c.yaml Outdated Show resolved Hide resolved
changelog/fragments/kb-800fdeec6e5c.yaml Outdated Show resolved Hide resolved
changelog/fragments/kb-800fdeec6e5c.yaml Outdated Show resolved Hide resolved
changelog/fragments/kb-800fdeec6e5c.yaml Show resolved Hide resolved
Signed-off-by: Camila Macedo <cmacedo@redhat.com>

- For Golang/Ansible/Helm language-based operators (go/v3, ansible/v1 and helm/v1): applying restrictive SCC for all containers scaffolded by the tool (k8s versions < 1.19 will no longer work with).
- For Golang-based language (go/v2) fix the issue introduced by removing the GO111MODULE=on from Dockerfile. ([More info](kubernetes-sigs/kubebuilder#2678))
- For Golang/Ansible/Helm language-based operators (go/v3, ansible/v1 and helm/v1 language (go/v3), add a new comment with the option `leaderElectionReleaseOnCancel` ((More info)[kubernetes-sigs/kubebuilder#2596])

Only to get the changes from what we currently use in SDK from kubebuilder.

- Ensure that scaffolds begin to be performed with a restrive Security Context
- Be able to do specific follow up PR so we can discuss properly how we will consume the new additions on Kubebuilder
- Make eaiser the process to keep SDK updated, otherwise, it is hard to properly review if we wait to do a big PR with all.
- Ensure that SDK features can work with the latest changes performed in Kubebuilder

**Extra info**
You can check the latest changes on Kubebuilder by looking: kubernetes-sigs/kubebuilder@v3.4.1...master

Note that SDK users Kubebuilder as a LIB. So that all that is currently important is updated by default when we bump. However, all that was added to Kubebuilder but still not imported/used in SDK will not be added here. Therefore we can do follow up PRs to get the additions. Why? we have significant changes and additions for example adding the support for the phase 2 plugin, but if we try to do it all in the same PR it will be very hard to get properly reviewed.

Co-authored-by: Varsha <varshaprasad96@gmail.com>
Copy link
Contributor

@everettraven everettraven left a comment

Choose a reason for hiding this comment

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

This looks good to me but I think it would be best to have another set of eyes and approval before merging.

Copy link
Member

@jmrodri jmrodri left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 8, 2022
@camilamacedo86 camilamacedo86 merged commit 65d781f into operator-framework:master Jun 8, 2022
@camilamacedo86 camilamacedo86 deleted the bump-kb-master branch June 8, 2022 13:41
@varshaprasad96 varshaprasad96 added this to the v1.22.0 milestone Jun 8, 2022
VenkatRamaraju pushed a commit to VenkatRamaraju/operator-sdk that referenced this pull request Jun 9, 2022
…or-framework#5814)

* Upgrade Kubebuilder dep from 3.4.1 to the commit 800fdeec6e5c

Signed-off-by: Camila Macedo <cmacedo@redhat.com>

- For Golang/Ansible/Helm language-based operators (go/v3, ansible/v1 and helm/v1): applying restrictive SCC for all containers scaffolded by the tool (k8s versions < 1.19 will no longer work with).
- For Golang-based language (go/v2) fix the issue introduced by removing the GO111MODULE=on from Dockerfile. ([More info](kubernetes-sigs/kubebuilder#2678))
- For Golang/Ansible/Helm language-based operators (go/v3, ansible/v1 and helm/v1 language (go/v3), add a new comment with the option `leaderElectionReleaseOnCancel` ((More info)[kubernetes-sigs/kubebuilder#2596])

Only to get the changes from what we currently use in SDK from kubebuilder.

- Ensure that scaffolds begin to be performed with a restrive Security Context
- Be able to do specific follow up PR so we can discuss properly how we will consume the new additions on Kubebuilder
- Make eaiser the process to keep SDK updated, otherwise, it is hard to properly review if we wait to do a big PR with all.
- Ensure that SDK features can work with the latest changes performed in Kubebuilder

**Extra info**
You can check the latest changes on Kubebuilder by looking: kubernetes-sigs/kubebuilder@v3.4.1...master

Note that SDK users Kubebuilder as a LIB. So that all that is currently important is updated by default when we bump. However, all that was added to Kubebuilder but still not imported/used in SDK will not be added here. Therefore we can do follow up PRs to get the additions. Why? we have significant changes and additions for example adding the support for the phase 2 plugin, but if we try to do it all in the same PR it will be very hard to get properly reviewed.

Co-authored-by: Varsha <varshaprasad96@gmail.com>

* trying to fix ansible lint

Co-authored-by: Varsha <varshaprasad96@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants