Closed mgfritch closed 3 months ago
I think it LGTM, but out of curiosity, for my own understanding: do we need to adds the OvsNetorks CRD anyway?
Yes, it's needed because the sriov-network-operator
will attempt to index the OVSNetwork
and fail during start-up if the api-resource is not present:
unable to create index field for cache {"error": "no matches for kind \"OVSNetwork\" in version \"sriovnetwork.openshift.io/v1\""}
Yes, it's needed because the
sriov-network-operator
will attempt to index theOVSNetwork
and fail during start-up if the api-resource is not present:
Thank you for the explanation! I'll approve once we address the other comment.
Updates to the latest sriov and nfd chart releases:
v1.3.0
v0.15.6
This also modifies the chart version scheme to use the upstream chart's semver instead of the prior scheme (
<version>+up<upstream_version>
). For example, the prior chart version was1.2.4+up0.1.0
whereas the next published chart version will be1.3.0
Open vSwitch networks are currently unsupported. The
OvsNetwork
CRD has been added, but any reference to theovs-cni
image has been removed.