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

🌱 Update with revert of PR #4481 for PATCH release 4.5.1 #4577

Merged
merged 61 commits into from
Feb 21, 2025

Conversation

camilamacedo86
Copy link
Member

No description provided.

migueleliasweb and others added 30 commits January 20, 2025 10:59
Closes 4079 (Make kubebuilder go install-able)

Signed-off-by: Miguel Elias dos Santos <migueleliasweb@gmail.com>
Signed-off-by: Mateus Oliveira <msouzaol@redhat.com>
Bumps [sigs.k8s.io/kubebuilder/v4](https://github.com/kubernetes-sigs/kubebuilder) from 4.4.0 to 4.5.0.
- [Release notes](https://github.com/kubernetes-sigs/kubebuilder/releases)
- [Changelog](https://github.com/kubernetes-sigs/kubebuilder/blob/master/RELEASE.md)
- [Commits](v4.4.0...v4.5.0)

---
updated-dependencies:
- dependency-name: sigs.k8s.io/kubebuilder/v4
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
…-scheme

🐛 (go/v4): Align webhook suite test with controller's suite test
🌱 : Fix Kubernetes version in the goreleaser by upgrading it from 1.31.0 to 1.32.0
…ocs/book/src/simple-external-plugin-tutorial/testdata/sampleexternalplugin/v1/sigs.k8s.io/kubebuilder/v4-4.5.0

📖 Bump sigs.k8s.io/kubebuilder/v4 from 4.4.0 to 4.5.0 in /docs/book/src/simple-external-plugin-tutorial/testdata/sampleexternalplugin/v1
🌱 test: add to commmon.sh the latest k8s release 1.32
🐛 fix: disallow files containing unwanted files when initializing a project
Upgrade controller-runtime from v0.20.0 to v0.20.1
📖 doc: update the Artifacts with the latest changes on the EnvTest Makefile target configurations
Bumps [github.com/spf13/pflag](https://github.com/spf13/pflag) from 1.0.5 to 1.0.6.
- [Release notes](https://github.com/spf13/pflag/releases)
- [Commits](spf13/pflag@v1.0.5...v1.0.6)

---
updated-dependencies:
- dependency-name: github.com/spf13/pflag
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps [github.com/spf13/pflag](https://github.com/spf13/pflag) from 1.0.5 to 1.0.6.
- [Release notes](https://github.com/spf13/pflag/releases)
- [Commits](spf13/pflag@v1.0.5...v1.0.6)

---
updated-dependencies:
- dependency-name: github.com/spf13/pflag
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
…ocs/book/src/simple-external-plugin-tutorial/testdata/sampleexternalplugin/v1/github.com/spf13/pflag-1.0.6

📖 bump github.com/spf13/pflag from 1.0.5 to 1.0.6 in /docs/book/src/simple-external-plugin-tutorial/testdata/sampleexternalplugin/v1
…ithub.com/spf13/pflag-1.0.6

🌱 bump github.com/spf13/pflag from 1.0.5 to 1.0.6
📖 fix: correct minor typos in documentation
🐛 (go/v4): e2e test: Removed Prometheus dependency
🌱 : Add YAML Linting to CI Workflow for Scaffolded Charts
…e CR (#4537)

Remove simplistic advice about multiple controllers reconciling same CR

This advice is simplyfing things and making an "It depends" situation
look like there was a clear good and a clear bad way that is the same in
all situations. Pretty much none of the issues stated will get better if
each controller gets its own CR:
* Race conditions: Conflict errors can always happen and all controllers
  need to be able to deal with them. If a full reconciliation is too
  expensive, they can use something like `retry.OnConflict`
* Concurrency issues with different interpretations of state: This
  example sounds like just buggy software. Copying the state to a new
  CR doesn't eliminate this problem
* Maintenance and support difficulties: This is definitely not going to
  get any better by adding more CRDs into the mix, if anything, it will
  get more complicated
* Status tracking complications: This is why conditions exist and
  Kubernetes api guidelines explicitly state that controllers need to
  ignore unknown conditions: `Objects may report multiple conditions,
  and new types of conditions may be added in the future or by 3rd
  party controllers.`, [ref][0]
* Performance issues: If multiple controllers do the same thing, that is
  a bug regardless of all other considerations and can easily lead to
  correctness and performance issues. The `workqueue` locks items while
  they are reconciled to avoid exactly that, but obviously it doesn't
  work cross-controller

To illustrate the situation, think about the `Pod` object, in the
lifecycle of a pod we usually have at least cluster-autoscaler,
scheduler and kubelet. Making cluster-autoscaler act on a
`PodScaleRequest` and scheduler on a `PodScheduleRequest` would be a
complication, not a simplification.

[0]: https://github.com/kubernetes/community/blob/322066e7dba7c5043071392fec427a57f8660734/contributors/devel/sig-architecture/api-conventions.md#typical-status-properties
…#4538)

ci: fix testdata - issues caused by some merge conflict with go mod
This reverts commit ded393e, reversing
changes made to 543b4a1.
camilamacedo86 and others added 23 commits February 9, 2025 10:37
🌱 Update controller-runtime version used in the common.sh tests
📖 Update Roadmap 2025 with latest status
This commit includes:
- Fix linter issues
- Refactor fetchCronJob in sample controller reconcile func
- Fix getting-started tutorial lint issues
- Fix multiversion tutorial lint issues
- Fix cronjob-tutorial lint issues
- Refactor cronjob controller reconcile to reduce cyclomatic complexity
🌱 : Improve samples linting & fix samples lint issues
Bumps [golang.org/x/tools](https://github.com/golang/tools) from 0.29.0 to 0.30.0.
- [Release notes](https://github.com/golang/tools/releases)
- [Commits](golang/tools@v0.29.0...v0.30.0)

---
updated-dependencies:
- dependency-name: golang.org/x/tools
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
🌱 Revert (kustomize/v2): fix ServiceMonitor with TLS kustomize scaffolding
…olang.org/x/tools-0.30.0

🌱 Bump golang.org/x/tools from 0.29.0 to 0.30.0
Upgrade controller-gen from v0.17.1 to v0.17.2
…LS check

Co-Author: Abhisek Dwivedi <abhishekdwivedi60@gmail.com>
🐛 (go/v4,ksutomize/v2,helm/v1-alpha): Fix prometheus integration with TLS check
…running kubebuilder init to fix issue when not on GOPATH
🐛 Fix kubebuild alpha generate when not in GOPATH
fix testdata generation
Bumps [github.com/spf13/cobra](https://github.com/spf13/cobra) from 1.8.1 to 1.9.1.
- [Release notes](https://github.com/spf13/cobra/releases)
- [Commits](spf13/cobra@v1.8.1...v1.9.1)

---
updated-dependencies:
- dependency-name: github.com/spf13/cobra
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
…ithub.com/spf13/cobra-1.9.1

🌱 Bump github.com/spf13/cobra from 1.8.1 to 1.9.1
Upgrade controller-runtime from v0.20.1 to v0.20.2 and K8s version from v1.32.0 to 1.32.1
…testdata

changes due to running make generate
…e-e2etesting-enhancement

🌱  Added e2e tests for alpha generate command for scaffolded data
…tall-able

🐛 Revert "Make kubebuilder go install-able"
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86

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 approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Feb 21, 2025
@camilamacedo86 camilamacedo86 merged commit 786b38f into release-4.5 Feb 21, 2025
60 of 61 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. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.