[ICN-350] Seek solution for k8s conformance Bluval failure Created: 29/Apr/20 Updated: 24/Jul/20 Resolved: 12/May/20 |
|
| Status: | Done |
| Project: | Integrated Cloud Native NFV |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Medium |
| Reporter: | Igor Duarte Cardoso | Assignee: | Igor Duarte Cardoso |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | ICN Bluval compliance |
| Sprint: | ICN Sprint 17 |
| Story Points: | 4 |
| Comments |
| Comment by Igor Duarte Cardoso [ 12/May/20 ] |
|
The solution for this was two-fold: disable virtlet, ovn and cmk plugins from ICN and make sure to deploy Kubernetes in multi-node. In a future item, conformance needs to be re-evaluated with all ICN plugins and fixed if the issues can still be reproduced. |