fix(images): make importers work in tainted cluster#1747
Conversation
images/virtualization-artifact/pkg/controller/vd/internal/source/http.go
Outdated
Show resolved
Hide resolved
images/virtualization-artifact/pkg/controller/vd/internal/source/http.go
Outdated
Show resolved
Hide resolved
ca47f3d to
2ab0e13
Compare
|
Workflow has started. The target step completed with status: cancelled. |
|
Workflow has started. The target step completed with status: failure. |
2ab0e13 to
ec01193
Compare
|
Workflow has started. The target step completed with status: cancelled. |
|
Workflow has started. The target step completed with status: failure. |
|
Workflow has started. The target step completed with status: failure. |
|
Workflow has started. |
9bbfeb7 to
a116c28
Compare
|
Workflow has started. The target step completed with status: failure. |
|
Workflow has started. The target step completed with status: failure. |
|
Workflow has started. The target step completed with status: failure. |
|
Workflow has started. The target step completed with status: success. |
- Add toleration to run importers on nodes belong to NodeGroup/system. Signed-off-by: Ivan Mikheykin <ivan.mikheykin@flant.com>
Signed-off-by: Ivan Mikheykin <ivan.mikheykin@flant.com>
…ally exclusive VMs on clusters with 3 nodes Signed-off-by: Ivan Mikheykin <ivan.mikheykin@flant.com>
dbb097a to
4b9568b
Compare
Description
Why do we need it, and what problem does it solve?
It is not possible to create images and disks with datasource in cluster where all nodes have taints.
What is the expected result?
FOCUS=VirtualImageCreation task e2e:runruns on tainted clusterChecklist
Changelog entries