-
Notifications
You must be signed in to change notification settings - Fork 34
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
[RFE] Additional Tasks #31
Conversation
configs/virt-customize.yaml
Outdated
@@ -0,0 +1,2 @@ | |||
task_name: virt-customize |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe we should name it pvc-virt-customize or disk-virt-customize instead for easier recognition?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmmm, I like both. Probably disk-... is better since it does not work on any PVC, only on VM disks
@@ -39,6 +41,14 @@ spec: | |||
description: Namespace where to create the VM. (defaults to active namespace) | |||
default: "" | |||
type: string | |||
- name: sshAuthorizedKeysSecret |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure if we should be adding the authorized keys to the VM only in execute-in-vm task or in create-vm-from-template / virt-customize tasks as well?
Currently it is added to all 3 tasks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The disadvantage is that the config is quite verbose since we have to specify the users too (possibly propagation policy), but the execute-in-vm task already knows the user.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would vote to add it only to create-vm-from-template - it makes maintenance of the pipelines easier if one thing is only done one way. Adding it to the other tasks would be useful only if I wanted to have a flow where I take an existing VM and add new keys into it and I dont see that as a valid use case.
labels: | ||
task.kubevirt.io/type: virt-customize | ||
task.kubevirt.io/category: virt-customize | ||
name: virt-customize |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the disadvantage of this task is that it cannot be run across different namespaces. So it can change only disks in the same namespace as the pipeline is running.
the advantage is that no serviceAccount is needed.
This could be fixed by implementing a CRD and a controller, although that would be a much larger endeavor than implementing a single task. It might be probably better to include this in a CDI which already does similar things.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I dont really see a reason to run the task in a different namespace than the pvc it modifies...
tasks/clone-pvc/README.md
Outdated
|
||
This task clones PersistentVolumeClaims to target PVC by using CDI DataVolumes. | ||
|
||
## `clone-pvc` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this might be better to include it as a subtask of create-datavolume
task. For example create-datavolume-from-pvc
. Thoughts?
the advantages is that there would be less main tasks and we could reuse serviceAccount and roles of create-datavolume
@suomiy: The following tests failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
21f9956
to
e071527
Compare
Signed-off-by: suomiy <suomiy@gmail.com>
Signed-off-by: suomiy <suomiy@gmail.com>
Signed-off-by: suomiy <suomiy@gmail.com>
Signed-off-by: suomiy <suomiy@gmail.com>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: atiratree 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 |
/retest |
2 similar comments
/retest |
/retest |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
@atiratree: PR needs rebase. 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. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with /lifecycle rotten |
/remove-lifecycle rotten |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
most of these tasks have been already implemented |
Tasks: