Skip to content

[release-2.0] Add commits for v2.0.1 #681

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

Merged

Conversation

qbarrand
Copy link
Contributor

@qbarrand qbarrand commented Jan 3, 2024

This PR adds multiple commits in preparation of the v2.0.1 release.

/cc @yevgeny-shnaidman @ybettan

qbarrand and others added 5 commits January 3, 2024 11:50
This change removes 'kmm.node.kubernetes.io/<module>.ready' labels on
all nodes, as it was deprecated in v1.1 and removed in v2.0.
Fix scheduling data generation for nodes that run an unconfigured
kernel and do not have the kmod loaded yet.
Make the build / sign events reconciler handle any owner for jobs, not
only Module.
…ernetes-sigs#677)

Currently worker only supports remote image mounting (from a repo).
In the future we might want to support also mounting an image from
a local tar file. This Pr lays a foundation for that. The basic idea
is that all the code should stay the same, and only the image mounting
implementation should change, as well as adding additional cobra
commands. The sequence to add a new image mounter option is:
1. Define a new cobra command and mount it under root command
2. the PreRun command in the new command should initialize the worker
   with the new image mounter
3. define a new load/unload cobra commands that should be exact replicas
   of the existing load/unload cobra command. The copy must be done due
   to the fact that in cobra a command cannot be a child of multiple
   commands
Changes in the PR:
1. kmod cobra command now initializes the worker. it will initiaze it
   with remote image mounter implementation. In case we need to add ad
   different mounter, we just define a different kmod cobra command and
   it will initialize the worker with the different image mounter
   implmentation
2. Change ImagePuller interface to ImageMounter interface
3. Move ImageMounter interface definition to a dedicated file
4. Move the implementation of the RemoteImageMounter into the dedicated
   file
5 update unit-tests
In v1.x we had 2 type of Daemonsets: DevicePlugin and ModuleLoader,
which could be distingished by the DaemonsetRole label
In v2.x, there only 1 type of daemonset, DevicePlugin, so the
DaemonsetRole labels was removed.
During DevicePlugin reconciliation, reconcile get all the device plugin
Ds based only on module name label, which means that in case there is a
v1.1 ModuleLoader DS running it will also be chosen. Once reconciler
tries to reconcile ModuleLoader DS, it will fail
This PR, updates the function that chooses the DevicePlugin DS, by
removing old ModuleLoader Ds based on Role label
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qbarrand

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 cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Jan 3, 2024
@qbarrand
Copy link
Contributor Author

qbarrand commented Jan 3, 2024

/override pull-kernel-module-management-check-commits-count

@qbarrand
Copy link
Contributor Author

qbarrand commented Jan 3, 2024

/override check-commits-count

@yevgeny-shnaidman
Copy link
Contributor

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 3, 2024
@ybettan
Copy link
Contributor

ybettan commented Jan 3, 2024

/override pull-kernel-module-management-check-commits-count

@ybettan
Copy link
Contributor

ybettan commented Jan 3, 2024

/?

@qbarrand
Copy link
Contributor Author

qbarrand commented Jan 3, 2024

/override pull-kernel-module-management-check-commits-count

@k8s-ci-robot
Copy link
Contributor

@qbarrand: Overrode contexts on behalf of qbarrand: pull-kernel-module-management-check-commits-count

In response to this:

/override pull-kernel-module-management-check-commits-count

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.

@k8s-ci-robot k8s-ci-robot merged commit 41bbe1a into kubernetes-sigs:release-2.0 Jan 3, 2024
@qbarrand qbarrand deleted the cp-release-2.0-us branch January 3, 2024 15:52
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/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants