-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
rhos-18.0.6
-
None
-
2
-
False
-
-
False
-
?
-
rhos-conplat-observability
-
None
-
-
-
-
Observability Sprint 25
-
1
-
Low
in our default ci env the ctlplane network is routable via the pods on crc by default
but this is not true in general and we cant assume that will be the case in a customer env
in https://issues.redhat.com/browse/OSPRH-11017 the ablity to pass network attachment was intoduced in the teh metricsStroage CRD but it was not defualted to include the ctlplane network even though that is always requried for metics to be scraped form edpm nodes.
in 18 we do not supprot disabling network isolation and require the ctrlplane network to deploy edpm nodes as teh only requried network so its safe to defaullt the CRD to include it
this will remove the need to manually set this in the openstack control plane CR for all deployments.
the fix is simple change
form
// NetworkAttachments is a list of NetworkAttachment resource names to expose the services to the given network
// +kubebuilder:validation:Optional
// +listType=atomic
NetworkAttachments []string `json:"networkAttachments,omitempty"`
to
// NetworkAttachments is a list of NetworkAttachment resource names to expose the services to the given network
// +kubebuilder:validation:Optional
// +listType=atomic
//+kubebuilder:default=["ctlplane"]
NetworkAttachments []string `json:"networkAttachments,omitempty"`
to match the default of DataplaneNetwork
// DataplaneNetwork defines the network that will be used to scrape dataplane node_exporter endpoints
// +kubebuilder:validation:Optional
// +kubebuilder:default=ctlplane
DataplaneNetwork *infranetworkv1.NetNameStr `json:"dataplaneNetwork"`
this remove the need to document overriding the default to have a fucntional deploy in