You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// `deploymentModel` defines the desired type of deployment for flow processing. Possible values are:<br>
74
-
// - `Service-TLS` (default) to make the flow processor listen as a Kubernetes Service, backed by a scalable Deployment.<br>
75
-
// - `Service-NoTLS` to make the flow processor listen as a Kubernetes Service, backed by a scalable Deployment. Version without TLS.<br>
73
+
// - `Service` (default) to make the flow processor listen as a Kubernetes Service, backed by a scalable Deployment.<br>
76
74
// - `Kafka` to make flows sent to a Kafka pipeline before consumption by the processor.<br>
77
75
// - `Direct` to make the flow processor listen directly from the agents using the host network, backed by a DaemonSet. Only recommended on small clusters, below 15 nodes.<br>
78
76
// Kafka can provide better scalability, resiliency, and high availability (for more details, see https://www.redhat.com/en/topics/integration/what-is-apache-kafka).<br>
79
77
// `Direct` is not recommended on large clusters as it is less memory efficient.
// Kafka configuration, allowing to use Kafka as a broker as part of the flow collection pipeline. Available when the `spec.deploymentModel` is `Kafka`.
Copy file name to clipboardExpand all lines: api/flowcollector/v1beta2/flowcollector_validation_webhook.go
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -276,7 +276,7 @@ func (v *validator) validateFLPLogTypes() {
276
276
if!v.fc.UseLoki() {
277
277
v.errors=append(v.errors, errors.New("enabling conversation tracking without Loki is not allowed, as it generates extra processing for no benefit"))
278
278
}
279
-
ifv.fc.UseServiceNetwork() {
279
+
ifv.fc.DeploymentModel==DeploymentModelService {
280
280
v.errors=append(v.errors, errors.New("cannot enable conversation tracking when spec.deploymentModel is Service: you must disable it, or change the deployment model"))
Copy file name to clipboardExpand all lines: bundle/manifests/flows.netobserv.io_flowcollectors.yaml
+3-5Lines changed: 3 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -3217,18 +3217,16 @@ spec:
3217
3217
type: boolean
3218
3218
type: object
3219
3219
deploymentModel:
3220
-
default: Service-TLS
3220
+
default: Service
3221
3221
description: |-
3222
3222
`deploymentModel` defines the desired type of deployment for flow processing. Possible values are:<br>
3223
-
- `Service-TLS` (default) to make the flow processor listen as a Kubernetes Service, backed by a scalable Deployment.<br>
3224
-
- `Service-NoTLS` to make the flow processor listen as a Kubernetes Service, backed by a scalable Deployment. Version without TLS.<br>
3223
+
- `Service` (default) to make the flow processor listen as a Kubernetes Service, backed by a scalable Deployment.<br>
3225
3224
- `Kafka` to make flows sent to a Kafka pipeline before consumption by the processor.<br>
3226
3225
- `Direct` to make the flow processor listen directly from the agents using the host network, backed by a DaemonSet. Only recommended on small clusters, below 15 nodes.<br>
3227
3226
Kafka can provide better scalability, resiliency, and high availability (for more details, see https://www.redhat.com/en/topics/integration/what-is-apache-kafka).<br>
3228
3227
`Direct` is not recommended on large clusters as it is less memory efficient.
Copy file name to clipboardExpand all lines: config/crd/bases/flows.netobserv.io_flowcollectors.yaml
+3-5Lines changed: 3 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -3011,18 +3011,16 @@ spec:
3011
3011
type: boolean
3012
3012
type: object
3013
3013
deploymentModel:
3014
-
default: Service-TLS
3014
+
default: Service
3015
3015
description: |-
3016
3016
`deploymentModel` defines the desired type of deployment for flow processing. Possible values are:<br>
3017
-
- `Service-TLS` (default) to make the flow processor listen as a Kubernetes Service, backed by a scalable Deployment.<br>
3018
-
- `Service-NoTLS` to make the flow processor listen as a Kubernetes Service, backed by a scalable Deployment. Version without TLS.<br>
3017
+
- `Service` (default) to make the flow processor listen as a Kubernetes Service, backed by a scalable Deployment.<br>
3019
3018
- `Kafka` to make flows sent to a Kafka pipeline before consumption by the processor.<br>
3020
3019
- `Direct` to make the flow processor listen directly from the agents using the host network, backed by a DaemonSet. Only recommended on small clusters, below 15 nodes.<br>
3021
3020
Kafka can provide better scalability, resiliency, and high availability (for more details, see https://www.redhat.com/en/topics/integration/what-is-apache-kafka).<br>
3022
3021
`Direct` is not recommended on large clusters as it is less memory efficient.
Copy file name to clipboardExpand all lines: docs/FlowCollector.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -112,15 +112,14 @@ for these features as a best effort only.
112
112
<td>enum</td>
113
113
<td>
114
114
`deploymentModel` defines the desired type of deployment for flow processing. Possible values are:<br>
115
-
-`Service-TLS` (default) to make the flow processor listen as a Kubernetes Service, backed by a scalable Deployment.<br>
116
-
-`Service-NoTLS` to make the flow processor listen as a Kubernetes Service, backed by a scalable Deployment. Version without TLS.<br>
115
+
-`Service` (default) to make the flow processor listen as a Kubernetes Service, backed by a scalable Deployment.<br>
117
116
-`Kafka` to make flows sent to a Kafka pipeline before consumption by the processor.<br>
118
117
-`Direct` to make the flow processor listen directly from the agents using the host network, backed by a DaemonSet. Only recommended on small clusters, below 15 nodes.<br>
119
118
Kafka can provide better scalability, resiliency, and high availability (for more details, see https://www.redhat.com/en/topics/integration/what-is-apache-kafka).<br>
120
119
`Direct` is not recommended on large clusters as it is less memory efficient.<br/>
Copy file name to clipboardExpand all lines: helm/crds/flows.netobserv.io_flowcollectors.yaml
+3-5Lines changed: 3 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -3015,18 +3015,16 @@ spec:
3015
3015
type: boolean
3016
3016
type: object
3017
3017
deploymentModel:
3018
-
default: Service-TLS
3018
+
default: Service
3019
3019
description: |-
3020
3020
`deploymentModel` defines the desired type of deployment for flow processing. Possible values are:<br>
3021
-
- `Service-TLS` (default) to make the flow processor listen as a Kubernetes Service, backed by a scalable Deployment.<br>
3022
-
- `Service-NoTLS` to make the flow processor listen as a Kubernetes Service, backed by a scalable Deployment. Version without TLS.<br>
3021
+
- `Service` (default) to make the flow processor listen as a Kubernetes Service, backed by a scalable Deployment.<br>
3023
3022
- `Kafka` to make flows sent to a Kafka pipeline before consumption by the processor.<br>
3024
3023
- `Direct` to make the flow processor listen directly from the agents using the host network, backed by a DaemonSet. Only recommended on small clusters, below 15 nodes.<br>
3025
3024
Kafka can provide better scalability, resiliency, and high availability (for more details, see https://www.redhat.com/en/topics/integration/what-is-apache-kafka).<br>
3026
3025
`Direct` is not recommended on large clusters as it is less memory efficient.
0 commit comments