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 dependencies including project Go version #23

Merged
merged 3 commits into from
Feb 21, 2024

Conversation

iamjoemccormick
Copy link
Member

@iamjoemccormick iamjoemccormick commented Feb 20, 2024

Checklist before merging:

  • Documentation: Has documentation been added for new functionality? Does any existing documentation need to be updated or removed?
  • Tests: Is there adequate test coverage for new functionality? Do any existing tests need to be updated?
  • Dependencies: Does this PR rely on any changes to dependencies? If so has the go.mod or equivalent been updated to point at a version that contains the related changes?
  • Git Hygiene: Is the commit history squashed down reasonably?

Which issue(s) does this PR address?

None (prompted by Dependabot Alerts).

Does this PR depend on any other PRs to be merged first?

None

What does this PR do / why do we need it?

Update various test dependencies to address various security vulnerabilities.

Notable changes:

  • Updated to Go 1.22.
  • K8s e2e tests now use a context from Ginkgo (kubernetes/kubernetes@2f6c4f5). Added TODO contexts where needed for now.
  • Various "Expect" functions were removed from the e2e framework. Replaced with equivalent conditionals and calls to Failf as suggested by (https://www.kubernetes.dev/blog/2023/04/12/e2e-testing-best-practices-reloaded/).
  • Fixed operator tests broken by the need to upgrade the controller-runtime pkg to work with the latest k8s.io/client-go pkg.
  • Updated the version of controller-gen used to generate code for the operator (the old version panicked with the new dependencies).

Rationale on fixes to e2e tests:
Despite not currently running e2e tests, it is better not to leave these broken as it will be harder to fix them in the future without the immediate context of what dependencies changed.

Where should the reviewer(s) start reviewing this?

Changes in go.mod and then the miscellaneous changes under test/e2e and operator/.

Are there any specific topics we should discuss before merging?

None

What are the next steps after this PR?

Update e2e-tests matrix to support new K8s and BeeGFS versions ahead of the next release.

@iamjoemccormick iamjoemccormick added dependencies Updates to dependency versions testing This issue improves tests or test tools. labels Feb 20, 2024
@iamjoemccormick iamjoemccormick self-assigned this Feb 20, 2024
@iamjoemccormick iamjoemccormick force-pushed the iamjoemccormick/dependency-updates branch 2 times, most recently from 0b1789e to 48647f6 Compare February 21, 2024 17:05
@iamjoemccormick iamjoemccormick force-pushed the iamjoemccormick/dependency-updates branch 3 times, most recently from 69cf137 to 8ae1515 Compare February 21, 2024 21:24
Notable changes:
- Updated to Go 1.22.
- K8s e2e tests now use a context from Ginkgo (kubernetes/kubernetes@2f6c4f5). Added TODO contexts where needed for now.
- Various "Expect" functions were removed from the e2e framework. Replaced with equivalent conditionals and calls to Failf as suggested by (https://www.kubernetes.dev/blog/2023/04/12/e2e-testing-best-practices-reloaded/).
- Fixed operator tests broken by the need to upgrade the controller-runtime pkg to work with the latest k8s.io/client-go pkg.

Rationale on fixes to e2e tests:
Despite not currently running e2e tests, it is better not to leave these broken as it will be harder to fix them in the future without the immediate context of what dependencies changed.
 - Ensure Git doesn't ever ignore anything under vendor/.
Due to the previous dependency updates, the old version was no longer compatible and would panic when trying to generate code containing DeepCopy, DeepCopyInto, and DeepCopyObject method implementations.
@iamjoemccormick iamjoemccormick force-pushed the iamjoemccormick/dependency-updates branch from 8ae1515 to beb5199 Compare February 21, 2024 21:45
@iamjoemccormick iamjoemccormick marked this pull request as ready for review February 21, 2024 22:12
@iamjoemccormick iamjoemccormick added this to the 1.6.0 milestone Feb 21, 2024
@iamjoemccormick iamjoemccormick merged commit 4418dfe into master Feb 21, 2024
25 checks passed
@iamjoemccormick iamjoemccormick deleted the iamjoemccormick/dependency-updates branch February 21, 2024 22:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Updates to dependency versions testing This issue improves tests or test tools.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant