-
Epic
-
Resolution: Won't Do
-
Undefined
-
None
-
None
-
cnv-ansible-bindings-managedfield
-
Product / Portfolio Work
-
To Do
-
VIRTSTRAT-442 - Lean Ansible bindings
-
-
100% To Do, 0% In Progress, 0% Done
Goal
Ansible bindings of CNV should make use of the managedField annotations supported by Kubernetes (see [1]).
For this the ansible bindings should support patching of resources or the server side apply mode when modifying existing resources on a cluster.
[1] https://kubernetes.io/docs/reference/using-api/server-side-apply/#field-management
User Stories
- As a VM Owner, I want to be notified of fields managed by Ansible when viewing a VM in the UI, so that I know I have to use Ansible to make changes.
- As a VM Owner, I want to be able to modify a subset of fields of an existing VMs, so that I can make changes in a predictable way.
Non-Requirements
- List of things not included in this epic, to alleviate any doubt raised during the grooming process.
Notes
- Any additional details or decisions made/needed
1.
|
upstream roadmap issue |
|
Closed | |
Unassigned |
2.
|
upstream documentation |
|
Closed | |
Unassigned |
3.
|
upgrade consideration |
|
Closed | |
Unassigned |
4.
|
CEE/PX summary presentation |
|
Closed | |
Unassigned |
5.
|
test plans in polarion |
|
Closed | |
Unassigned |
6.
|
automated tests |
|
Closed | |
Unassigned |
7.
|
downstream documentation merged |
|
Closed | |
Unassigned |