diff --git a/.mk/development.mk b/.mk/development.mk index cae09ab16e..bce1a4c433 100644 --- a/.mk/development.mk +++ b/.mk/development.mk @@ -188,7 +188,7 @@ endif .PHONY: pprof pprof: - @echo -e "\n==> Enabling pprof... Check https://github.com/netobserv/network-observability-operator/blob/main/DEVELOPMENT.md#profiling for help." + @echo -e "\n==> Enabling pprof... Check https://github.com/netobserv/netobserv-operator/blob/main/DEVELOPMENT.md#profiling for help." kubectl -n $(NAMESPACE) set env deployment netobserv-controller-manager -c "manager" PROFILING_BIND_ADDRESS=:6060 @echo -e "\n==> Redeploying..." kubectl rollout status -n $(NAMESPACE) --timeout=60s deployment netobserv-controller-manager diff --git a/.tekton/network-observability-operator-bundle-ystream-pull-request.yaml b/.tekton/network-observability-operator-bundle-ystream-pull-request.yaml index 0d76651af5..0c949dfc14 100644 --- a/.tekton/network-observability-operator-bundle-ystream-pull-request.yaml +++ b/.tekton/network-observability-operator-bundle-ystream-pull-request.yaml @@ -2,7 +2,7 @@ apiVersion: tekton.dev/v1 kind: PipelineRun metadata: annotations: - build.appstudio.openshift.io/repo: https://github.com/netobserv/network-observability-operator?rev={{revision}} + build.appstudio.openshift.io/repo: https://github.com/netobserv/netobserv-operator?rev={{revision}} build.appstudio.redhat.com/commit_sha: '{{revision}}' build.appstudio.redhat.com/pull_request_number: '{{pull_request_number}}' build.appstudio.redhat.com/target_branch: '{{target_branch}}' diff --git a/.tekton/network-observability-operator-bundle-ystream-push.yaml b/.tekton/network-observability-operator-bundle-ystream-push.yaml index bc4ae3341e..86a3787bd3 100644 --- a/.tekton/network-observability-operator-bundle-ystream-push.yaml +++ b/.tekton/network-observability-operator-bundle-ystream-push.yaml @@ -2,7 +2,7 @@ apiVersion: tekton.dev/v1 kind: PipelineRun metadata: annotations: - build.appstudio.openshift.io/repo: https://github.com/netobserv/network-observability-operator?rev={{revision}} + build.appstudio.openshift.io/repo: https://github.com/netobserv/netobserv-operator?rev={{revision}} build.appstudio.redhat.com/commit_sha: '{{revision}}' build.appstudio.redhat.com/target_branch: '{{target_branch}}' pipelinesascode.tekton.dev/max-keep-runs: "3" diff --git a/.tekton/network-observability-operator-ystream-pull-request.yaml b/.tekton/network-observability-operator-ystream-pull-request.yaml index 31977d066d..acd3105f9b 100644 --- a/.tekton/network-observability-operator-ystream-pull-request.yaml +++ b/.tekton/network-observability-operator-ystream-pull-request.yaml @@ -2,7 +2,7 @@ apiVersion: tekton.dev/v1 kind: PipelineRun metadata: annotations: - build.appstudio.openshift.io/repo: https://github.com/netobserv/network-observability-operator?rev={{revision}} + build.appstudio.openshift.io/repo: https://github.com/netobserv/netobserv-operator?rev={{revision}} build.appstudio.redhat.com/commit_sha: '{{revision}}' build.appstudio.redhat.com/pull_request_number: '{{pull_request_number}}' build.appstudio.redhat.com/target_branch: '{{target_branch}}' diff --git a/.tekton/network-observability-operator-ystream-push.yaml b/.tekton/network-observability-operator-ystream-push.yaml index bb39ecd083..c772bb11eb 100644 --- a/.tekton/network-observability-operator-ystream-push.yaml +++ b/.tekton/network-observability-operator-ystream-push.yaml @@ -3,7 +3,7 @@ kind: PipelineRun metadata: annotations: build.appstudio.openshift.io/build-nudge-files: hack/nudging/container_digest.sh - build.appstudio.openshift.io/repo: https://github.com/netobserv/network-observability-operator?rev={{revision}} + build.appstudio.openshift.io/repo: https://github.com/netobserv/netobserv-operator?rev={{revision}} build.appstudio.redhat.com/commit_sha: '{{revision}}' build.appstudio.redhat.com/target_branch: '{{target_branch}}' pipelinesascode.tekton.dev/max-keep-runs: "3" diff --git a/AGENTS.md b/AGENTS.md index 4ba9d3e0ed..dadafac278 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -14,7 +14,7 @@ Best practices for AI coding agents on NetObserv Operator. flow generation from packets (DaemonSet) - **[flowlogs-pipeline](https://github.com/netobserv/flowlogs-pipeline)**: Flow collection, enrichment, export (Deployment/StatefulSet) - - **[Console Plugin](https://github.com/netobserv/network-observability-console-plugin)**: + **[Console Plugin](https://github.com/netobserv/netobserv-web-console)**: OpenShift visualization (optional) - **CRD**: `FlowCollector` v1beta2 - **single cluster-wide resource named `cluster`** diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md index a27c463322..145df46919 100644 --- a/DEVELOPMENT.md +++ b/DEVELOPMENT.md @@ -344,7 +344,7 @@ This workflow is triggered when something is merged into `main`, to push new ima git push upstream HEAD:workflow-test -f ``` -Then, open the [action page](https://github.com/netobserv/network-observability-operator/actions/workflows/push_image.yml) in Github to monitor the jobs triggered. Make sure on Quay that you get the expected images for the [Operator](https://quay.io/repository/netobserv/network-observability-operator?tab=tags), the [bundle](https://quay.io/repository/netobserv/network-observability-operator-bundle?tab=tags) and the [catalog](https://quay.io/repository/netobserv/network-observability-operator-catalog?tab=tags). +Then, open the [action page](https://github.com/netobserv/netobserv-operator/actions/workflows/push_image.yml) in Github to monitor the jobs triggered. Make sure on Quay that you get the expected images for the [Operator](https://quay.io/repository/netobserv/network-observability-operator?tab=tags), the [bundle](https://quay.io/repository/netobserv/network-observability-operator-bundle?tab=tags) and the [catalog](https://quay.io/repository/netobserv/network-observability-operator-catalog?tab=tags). Expected images: - Operator's tagged "workflow-test" manifest + every support archs @@ -364,7 +364,7 @@ git push origin HEAD:dummy Then, open a PR in github, making sure to select `workflow-test` as the base branch and not `main`. On the PR, add the `ok-to-test` label. -This will trigger the corresponding `push_image_pr.yml` workflow ([view on github](https://github.com/netobserv/network-observability-operator/actions/workflows/push_image_pr.yml)). As above, you should check that the images are well created in Quay: +This will trigger the corresponding `push_image_pr.yml` workflow ([view on github](https://github.com/netobserv/netobserv-operator/actions/workflows/push_image_pr.yml)). As above, you should check that the images are well created in Quay: Expected images: - Operator's tagged with SHA manifest + single arch amd64 (make sure they expire) @@ -379,7 +379,7 @@ git tag -a "0.0.0-rc0" -m "0.0.0-rc0" git push upstream --tags ``` -When the tag is pushed, it will trigger the corresponding workflow ([view on github](https://github.com/netobserv/network-observability-operator/actions/workflows/release.yml)). As above, you should check that the images are well created in Quay. It's fine if you tag from the `workflow-test` branch (or any branch). +When the tag is pushed, it will trigger the corresponding workflow ([view on github](https://github.com/netobserv/netobserv-operator/actions/workflows/release.yml)). As above, you should check that the images are well created in Quay. It's fine if you tag from the `workflow-test` branch (or any branch). Expected images: - Operator's tagged 0.0.0-rc0 manifest + every support archs diff --git a/FAQ.md b/FAQ.md index 67683df1c2..07be63bbd4 100644 --- a/FAQ.md +++ b/FAQ.md @@ -1,6 +1,6 @@ # F.A.Q / Troubleshooting -If you can't find help here, don't hesitate to open [an issue](https://github.com/netobserv/network-observability-operator/issues) or a [Q&A](https://github.com/netobserv/network-observability-operator/discussions/categories/q-a). There are several repositories under _netobserv_ github org, but it is fine to centralize these in _network-observability-operator_. +If you can't find help here, don't hesitate to open [an issue](https://github.com/netobserv/netobserv-operator/issues) or a [Q&A](https://github.com/netobserv/netobserv-operator/discussions/categories/q-a). There are several repositories under _netobserv_ github org, but it is fine to centralize these in _network-observability-operator_. ## Table of Contents @@ -20,34 +20,6 @@ If you can't find help here, don't hesitate to open [an issue](https://github.co ## Q&A -### Is it for OpenShift only? - -No! While some features are developed primarily for OpenShift, we want to keep it on track with other / "vanilla" Kubes. For instance, there has been some work to make the console plugin [run as a standalone](https://github.com/netobserv/network-observability-console-plugin/pull/163), or the operator to manage upstream (non-OpenShift) [ovn-kubernetes](https://github.com/netobserv/network-observability-operator/pull/97). - -And if something is not working as hoped with your setup, you are welcome to contribute to the project ;-) - -### Which version of Kubernetes / OpenShift is supported? - -All versions of Kubernetes since 1.22 should work, although there is no official support (best effort). - -All versions of OpenShift currently supported by Red Hat are supported. Older version, greater than 4.10, should also work although not being officially supported (best effort). - -Some features depend on the Linux kernel version in use. It should be at least 4.18 (earlier versions have never been tested). More recent kernels (> 5.14) are better, for agent feature completeness and improved performances. - -### How do I visualize flows and metrics? - -For OpenShift users, a visualization tool is integrated in the OpenShift console. Just open the console in your browser, and you will see new menu items (such as Network Traffic under Observe) once NetObserv is installed and configured. - -Non-OpenShift users can deploy the standalone console, as explained in the Getting Started section from the readme. - -Alternatively, you can still access the data (Loki logs, Prometheus metrics) in different ways: - -- Querying Loki (or Prometheus) directly -- Using the Prometheus console -- Using and configuring Grafana - -All these options depend on how you installed these components. - ### How can I make sure everything is correctly deployed? Make sure all pods are up and running: @@ -109,7 +81,7 @@ If using IPFIX (ie. `spec.agent.type` is `IPFIX` in FlowCollector), wait 10 minu Else, check for any suspicious error in logs, especially in the `flowlogs-pipeline` pods and the eBPF agent pods. You may also take a look at prometheus metrics prefixed with `netobserv_`: they can give you clues if flows are processed, if errors are reported, etc. -Finally, don't hesitate to [open an issue](https://github.com/netobserv/network-observability-operator/issues). +Finally, don't hesitate to [open an issue](https://github.com/netobserv/netobserv-operator/issues). ### There is no Network Traffic menu entry in OpenShift Console @@ -182,7 +154,7 @@ With Loki queries, a first thing to understand is that, while Loki allows to que Depending on what you are trying to get, you may as well **consider querying Prometheus rather than Loki**. Queries on Prometheus are much faster than on Loki, it should not struggle with large time ranges, hence should be favored whenever possible. But Prometheus metrics do not contain as much information as flow logs in Loki, so whether or not you can do that really depends on the use case. When you use the NetObserv console plugin, it will try automatically to favor Prometheus over Loki if the query is compatible; else it falls back to Loki. If your query does't run against Prometheus, changing some filters or aggregations can make the switch. In the console plugin, you can force the use of Prometheus. Incompatible queries will fail, and the error message displayed should help you figure out which labels you can try to change to make the query compatible (for instance, changing a filter or an aggregation from Resource/Pods to Owner). -If the data that you need isn't available as a Prometheus metric, you may also **consider using the [FlowMetrics API](https://github.com/netobserv/network-observability-operator/blob/main/docs/Metrics.md#custom-metrics-using-the-flowmetrics-api)** to create your own metric. You need to be careful about the metrics cardinality, as explained in this link. +If the data that you need isn't available as a Prometheus metric, you may also **consider using the [FlowMetrics API](https://github.com/netobserv/netobserv-operator/blob/main/docs/Metrics.md#custom-metrics-using-the-flowmetrics-api)** to create your own metric. You need to be careful about the metrics cardinality, as explained in this link. If the problem persists, there are ways to **configure Loki to improve the query performance**. Some options depend on the installation mode you used for Loki (using the Operator and `LokiStack`, or `Monolithic` mode, or `Microservices` mode): diff --git a/PROJECT b/PROJECT index 36cbab34c8..bff828f7b6 100644 --- a/PROJECT +++ b/PROJECT @@ -8,7 +8,7 @@ layout: plugins: manifests.sdk.operatorframework.io/v2: {} projectName: netobserv-operator -repo: github.com/netobserv/network-observability-operator +repo: github.com/netobserv/netobserv-operator resources: - api: crdVersion: v1 @@ -16,7 +16,7 @@ resources: domain: netobserv.io group: flows kind: FlowCollector - path: github.com/netobserv/network-observability-operator/api/flowcollector/v1beta2 + path: github.com/netobserv/netobserv-operator/api/flowcollector/v1beta2 version: v1beta2 webhooks: conversion: false @@ -33,7 +33,7 @@ resources: domain: netobserv.io group: flows kind: FlowMetric - path: github.com/netobserv/network-observability-operator/api/flowmetrics/v1alpha1 + path: github.com/netobserv/netobserv-operator/api/flowmetrics/v1alpha1 version: v1alpha1 webhooks: validation: true @@ -44,6 +44,6 @@ resources: domain: netobserv.io group: flows kind: FlowCollectorSlice - path: github.com/netobserv/network-observability-operator/api/flowcollectorslice/v1alpha1 + path: github.com/netobserv/netobserv-operator/api/flowcollectorslice/v1alpha1 version: v1alpha1 version: "3" diff --git a/README.md b/README.md index 738bca8ca3..05078277fe 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ ![GitHub release (latest by date)](https://img.shields.io/github/v/release/netobserv/network-observability-operator) [![Artifact HUB](https://img.shields.io/endpoint?url=https://artifacthub.io/badge/repository/NetObserv)](https://artifacthub.io/packages/helm/netobserv/netobserv-operator) -[![Go Report Card](https://goreportcard.com/badge/github.com/netobserv/network-observability-operator)](https://goreportcard.com/report/github.com/netobserv/network-observability-operator) +[![Go Report Card](https://goreportcard.com/badge/github.com/netobserv/netobserv-operator)](https://goreportcard.com/report/github.com/netobserv/netobserv-operator) NetObserv Operator is a Kubernetes operator for network observability. It deploys a monitoring pipeline that consists in: - An eBPF agent, that generates network flows from captured packets. @@ -91,7 +91,7 @@ EOF ``` A few remarks: -- You can change the Prometheus and Loki URLs depending on your installation. This example works if you use the "standalone" installation described above, with `install.loki=true` and `install.prom-stack=true`. Check more configuration options for [Prometheus](https://github.com/netobserv/network-observability-operator/blob/main/docs/FlowCollector.md#flowcollectorspecprometheus-1) and [Loki](https://github.com/netobserv/network-observability-operator/blob/main/docs/FlowCollector.md#flowcollectorspecloki-1). +- You can change the Prometheus and Loki URLs depending on your installation. This example works if you use the "standalone" installation described above, with `install.loki=true` and `install.prom-stack=true`. Check more configuration options for [Prometheus](https://github.com/netobserv/netobserv-operator/blob/main/docs/FlowCollector.md#flowcollectorspecprometheus-1) and [Loki](https://github.com/netobserv/netobserv-operator/blob/main/docs/FlowCollector.md#flowcollectorspecloki-1). - Depending on the Kubernetes distribution and CNI, NetObserv may come secured by default with a built-in network policy. You can force installing it or not by setting `spec.networkPolicy.enable` in `FlowCollector`. If the built-in policy does not work as intended, it is recommended to turn it off and create your own instead. NetObserv runs some highly privileged workloads, thus it is important to keep it as much isolated as possible. See [NetworkPolicy.md](./docs/NetworkPolicy.md) for more details on how to create a policy. - The processor env `SERVER_NOTLS` means that the communication between eBPF agents and Flowlogs-pipeline won't be encrypted. To enable TLS, you need to supply the TLS certificates to Flowlogs-pipeline (a Secret named `flowlogs-pipeline-cert`), and the CA to the eBPF agents (a ConfigMap named `flowlogs-pipeline-ca` in the privileged namespace). @@ -108,7 +108,7 @@ Then open http://localhost:9001/ in your browser. A couple of `make` targets are provided in this repository to allow installing without OLM: ```bash -git clone https://github.com/netobserv/network-observability-operator.git && cd network-observability-operator +git clone https://github.com/netobserv/netobserv-operator.git && cd network-observability-operator USER=netobserv make deploy deploy-loki deploy-grafana ``` diff --git a/RELEASE.md b/RELEASE.md index 4a5b46c04a..b28e635496 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -4,7 +4,7 @@ All components deployed by this operator can be released separatly, at their own pace. -To release them, a tag in the format "v1.6.0-community" or "v1.6.0-crc0" must be set on the desired clean HEAD state (generally, up-to-date `main` branch; "crc" stands for "community release candidate"), then pushed. It applies to [the console plugin](https://github.com/netobserv/network-observability-console-plugin/), [flowlogs-pipeline](https://github.com/netobserv/flowlogs-pipeline) and [netobserv-ebpf-agent](https://github.com/netobserv/netobserv-ebpf-agent). +To release them, a tag in the format "v1.6.0-community" or "v1.6.0-crc0" must be set on the desired clean HEAD state (generally, up-to-date `main` branch; "crc" stands for "community release candidate"), then pushed. It applies to [the console plugin](https://github.com/netobserv/netobserv-web-console/), [flowlogs-pipeline](https://github.com/netobserv/flowlogs-pipeline) and [netobserv-ebpf-agent](https://github.com/netobserv/netobserv-ebpf-agent). E.g: @@ -35,7 +35,7 @@ git tag -a "$version" -m "$version" git push upstream --tags ``` -The release script should be triggered ([check github actions](https://github.com/netobserv/network-observability-operator/actions)). +The release script should be triggered ([check github actions](https://github.com/netobserv/netobserv-operator/actions)). ### Testing @@ -105,7 +105,7 @@ git push upstream :$test_branch ### Publish releases - related components Use the github interface to accept the releases, via: -- [console plugin](https://github.com/netobserv/network-observability-console-plugin/releases) +- [console plugin](https://github.com/netobserv/netobserv-web-console/releases) - [flowlogs-pipeline](https://github.com/netobserv/flowlogs-pipeline/releases) - [netobserv-ebpf-agent](https://github.com/netobserv/netobserv-ebpf-agent/releases) @@ -125,7 +125,7 @@ If you think the "Dependencies" section is too long, you can surround it in a `< ### Publish releases - operator Use the github interface to accept the release, via: -- [operator](https://github.com/netobserv/network-observability-operator/releases) +- [operator](https://github.com/netobserv/netobserv-operator/releases) Edit the draft, set the previous tag then click the "Generate release notes" button. Like previously, don't hesitate to surround Dependencies in a `
` block. diff --git a/api/flowcollector/v1beta2/flowcollector_alert_types.go b/api/flowcollector/v1beta2/flowcollector_alert_types.go index 9bd10ef80e..91c2243304 100644 --- a/api/flowcollector/v1beta2/flowcollector_alert_types.go +++ b/api/flowcollector/v1beta2/flowcollector_alert_types.go @@ -49,7 +49,7 @@ type FLPHealthRule struct { // Possible values are: `PacketDropsByKernel`, `PacketDropsByDevice`, `IPsecErrors`, `NetpolDenied`, // `LatencyHighTrend`, `DNSErrors`, `DNSNxDomain`, `ExternalEgressHighTrend`, `ExternalIngressHighTrend`, `Ingress5xxErrors`, `IngressHTTPLatencyTrend`. // Note: `NetObservNoFlows` and `NetObservLokiError` are alert-only and cannot be used as health rules. - // More information on health rules: https://github.com/netobserv/network-observability-operator/blob/main/docs/HealthRules.md + // More information on health rules: https://github.com/netobserv/netobserv-operator/blob/main/docs/HealthRules.md // +kubebuilder:validation:Enum:="PacketDropsByKernel";"PacketDropsByDevice";"IPsecErrors";"NetpolDenied";"LatencyHighTrend";"DNSErrors";"DNSNxDomain";"ExternalEgressHighTrend";"ExternalIngressHighTrend";"Ingress5xxErrors";"IngressHTTPLatencyTrend" // +required Template HealthRuleTemplate `json:"template,omitempty"` diff --git a/api/flowcollector/v1beta2/flowcollector_types.go b/api/flowcollector/v1beta2/flowcollector_types.go index 388efd04be..75c62ceec7 100644 --- a/api/flowcollector/v1beta2/flowcollector_types.go +++ b/api/flowcollector/v1beta2/flowcollector_types.go @@ -102,7 +102,7 @@ type NetworkPolicy struct { // Because it cannot be tested with all CNIs, this option is only enabled by default when NetObserv runs in a known // supported environment, and it is disabled by default otherwise. // When disabled, it is highly recommended to create network policies manually, to prevent undesired accesses. - // More information: https://github.com/netobserv/network-observability-operator/blob/main/docs/NetworkPolicy.md. + // More information: https://github.com/netobserv/netobserv-operator/blob/main/docs/NetworkPolicy.md. // +optional Enable *bool `json:"enable,omitempty"` @@ -568,7 +568,7 @@ type MetricsServerConfig struct { TLS ServerTLS `json:"tls"` } -// Metric name. More information in https://github.com/netobserv/network-observability-operator/blob/main/docs/Metrics.md. +// Metric name. More information in https://github.com/netobserv/netobserv-operator/blob/main/docs/Metrics.md. // +kubebuilder:validation:Enum:="namespace_egress_bytes_total";"namespace_egress_packets_total";"namespace_ingress_bytes_total";"namespace_ingress_packets_total";"namespace_flows_total";"node_egress_bytes_total";"node_egress_packets_total";"node_ingress_bytes_total";"node_ingress_packets_total";"node_flows_total";"workload_egress_bytes_total";"workload_egress_packets_total";"workload_ingress_bytes_total";"workload_ingress_packets_total";"workload_flows_total";"namespace_drop_bytes_total";"namespace_drop_packets_total";"node_drop_bytes_total";"node_drop_packets_total";"workload_drop_bytes_total";"workload_drop_packets_total";"namespace_rtt_seconds";"node_rtt_seconds";"workload_rtt_seconds";"namespace_dns_latency_seconds";"node_dns_latency_seconds";"workload_dns_latency_seconds";"node_network_policy_events_total";"namespace_network_policy_events_total";"workload_network_policy_events_total";"node_ipsec_flows_total";"node_to_node_ingress_flows_total" type FLPMetric string @@ -587,20 +587,20 @@ type FLPMetrics struct { // `workload_egress_bytes_total`, `namespace_drop_packets_total` (when `PacketDrop` feature is enabled), // `namespace_rtt_seconds` (when `FlowRTT` feature is enabled), `namespace_dns_latency_seconds` (when `DNSTracking` feature is enabled), // `namespace_network_policy_events_total` (when `NetworkEvents` feature is enabled). - // More information, with full list of available metrics: https://github.com/netobserv/network-observability-operator/blob/main/docs/Metrics.md + // More information, with full list of available metrics: https://github.com/netobserv/netobserv-operator/blob/main/docs/Metrics.md // +optional IncludeList *[]FLPMetric `json:"includeList,omitempty"` // `disableAlerts` is a list of alert groups that should be disabled from the default set of alerts. // Possible values are: `NetObservNoFlows`, `NetObservLokiError`, `PacketDropsByKernel`, `PacketDropsByDevice`, `IPsecErrors`, `NetpolDenied`, // `LatencyHighTrend`, `DNSErrors`, `DNSNxDomain`, `ExternalEgressHighTrend`, `ExternalIngressHighTrend`, `Ingress5xxErrors`, `IngressHTTPLatencyTrend`. - // More information on alerts: https://github.com/netobserv/network-observability-operator/blob/main/docs/HealthRules.md + // More information on alerts: https://github.com/netobserv/netobserv-operator/blob/main/docs/HealthRules.md // +optional DisableAlerts []HealthRuleTemplate `json:"disableAlerts"` // `healthRules` is a list of health rules to be created for Prometheus, organized by templates and variants. // Each health rule can be configured to generate either alerts or recording rules based on the mode field. - // More information on health rules: https://github.com/netobserv/network-observability-operator/blob/main/docs/HealthRules.md + // More information on health rules: https://github.com/netobserv/netobserv-operator/blob/main/docs/HealthRules.md // +optional HealthRules *[]FLPHealthRule `json:"healthRules"` } diff --git a/api/flowcollector/v1beta2/helper.go b/api/flowcollector/v1beta2/helper.go index f5b6f0d706..0763c762d7 100644 --- a/api/flowcollector/v1beta2/helper.go +++ b/api/flowcollector/v1beta2/helper.go @@ -3,7 +3,7 @@ package v1beta2 import ( "strconv" - "github.com/netobserv/network-observability-operator/internal/controller/constants" + "github.com/netobserv/netobserv-operator/internal/controller/constants" ) func (spec *FlowCollectorSpec) GetNamespace() string { diff --git a/api/flowmetrics/v1alpha1/flowmetric_webhook.go b/api/flowmetrics/v1alpha1/flowmetric_webhook.go index 0dd1fdac95..55d99d91c7 100644 --- a/api/flowmetrics/v1alpha1/flowmetric_webhook.go +++ b/api/flowmetrics/v1alpha1/flowmetric_webhook.go @@ -5,8 +5,8 @@ import ( "fmt" "strconv" - "github.com/netobserv/network-observability-operator/internal/pkg/helper" - "github.com/netobserv/network-observability-operator/internal/pkg/helper/cardinality" + "github.com/netobserv/netobserv-operator/internal/pkg/helper" + "github.com/netobserv/netobserv-operator/internal/pkg/helper/cardinality" apierrors "k8s.io/apimachinery/pkg/api/errors" "k8s.io/apimachinery/pkg/runtime/schema" diff --git a/bundle.Dockerfile.downstream b/bundle.Dockerfile.downstream index 7b5ce242ec..99b38e2e13 100644 --- a/bundle.Dockerfile.downstream +++ b/bundle.Dockerfile.downstream @@ -45,5 +45,5 @@ LABEL description="Network Observability operator for OpenShift." LABEL distribution-scope=public LABEL release=$BUILDVERSION LABEL version=$BUILDVERSION -LABEL url="https://github.com/netobserv/network-observability-operator" +LABEL url="https://github.com/netobserv/netobserv-operator" LABEL vendor="Red Hat, Inc." diff --git a/bundle/manifests/flows.netobserv.io_flowcollectors.yaml b/bundle/manifests/flows.netobserv.io_flowcollectors.yaml index 9635293b0a..54d7575468 100644 --- a/bundle/manifests/flows.netobserv.io_flowcollectors.yaml +++ b/bundle/manifests/flows.netobserv.io_flowcollectors.yaml @@ -4317,7 +4317,7 @@ spec: Because it cannot be tested with all CNIs, this option is only enabled by default when NetObserv runs in a known supported environment, and it is disabled by default otherwise. When disabled, it is highly recommended to create network policies manually, to prevent undesired accesses. - More information: https://github.com/netobserv/network-observability-operator/blob/main/docs/NetworkPolicy.md. + More information: https://github.com/netobserv/netobserv-operator/blob/main/docs/NetworkPolicy.md. type: boolean type: object processor: @@ -5856,7 +5856,7 @@ spec: `disableAlerts` is a list of alert groups that should be disabled from the default set of alerts. Possible values are: `NetObservNoFlows`, `NetObservLokiError`, `PacketDropsByKernel`, `PacketDropsByDevice`, `IPsecErrors`, `NetpolDenied`, `LatencyHighTrend`, `DNSErrors`, `DNSNxDomain`, `ExternalEgressHighTrend`, `ExternalIngressHighTrend`, `Ingress5xxErrors`, `IngressHTTPLatencyTrend`. - More information on alerts: https://github.com/netobserv/network-observability-operator/blob/main/docs/HealthRules.md + More information on alerts: https://github.com/netobserv/netobserv-operator/blob/main/docs/HealthRules.md items: type: string type: array @@ -5864,7 +5864,7 @@ spec: description: |- `healthRules` is a list of health rules to be created for Prometheus, organized by templates and variants. Each health rule can be configured to generate either alerts or recording rules based on the mode field. - More information on health rules: https://github.com/netobserv/network-observability-operator/blob/main/docs/HealthRules.md + More information on health rules: https://github.com/netobserv/netobserv-operator/blob/main/docs/HealthRules.md items: properties: mode: @@ -5885,7 +5885,7 @@ spec: Possible values are: `PacketDropsByKernel`, `PacketDropsByDevice`, `IPsecErrors`, `NetpolDenied`, `LatencyHighTrend`, `DNSErrors`, `DNSNxDomain`, `ExternalEgressHighTrend`, `ExternalIngressHighTrend`, `Ingress5xxErrors`, `IngressHTTPLatencyTrend`. Note: `NetObservNoFlows` and `NetObservLokiError` are alert-only and cannot be used as health rules. - More information on health rules: https://github.com/netobserv/network-observability-operator/blob/main/docs/HealthRules.md + More information on health rules: https://github.com/netobserv/netobserv-operator/blob/main/docs/HealthRules.md enum: - PacketDropsByKernel - PacketDropsByDevice @@ -5978,9 +5978,9 @@ spec: `workload_egress_bytes_total`, `namespace_drop_packets_total` (when `PacketDrop` feature is enabled), `namespace_rtt_seconds` (when `FlowRTT` feature is enabled), `namespace_dns_latency_seconds` (when `DNSTracking` feature is enabled), `namespace_network_policy_events_total` (when `NetworkEvents` feature is enabled). - More information, with full list of available metrics: https://github.com/netobserv/network-observability-operator/blob/main/docs/Metrics.md + More information, with full list of available metrics: https://github.com/netobserv/netobserv-operator/blob/main/docs/Metrics.md items: - description: Metric name. More information in https://github.com/netobserv/network-observability-operator/blob/main/docs/Metrics.md. + description: Metric name. More information in https://github.com/netobserv/netobserv-operator/blob/main/docs/Metrics.md. enum: - namespace_egress_bytes_total - namespace_egress_packets_total diff --git a/bundle/manifests/netobserv-operator.clusterserviceversion.yaml b/bundle/manifests/netobserv-operator.clusterserviceversion.yaml index 078924a940..ce8b3b5083 100644 --- a/bundle/manifests/netobserv-operator.clusterserviceversion.yaml +++ b/bundle/manifests/netobserv-operator.clusterserviceversion.yaml @@ -98,7 +98,7 @@ metadata: operatorframework.io/suggested-namespace: openshift-netobserv-operator operators.operatorframework.io/builder: operator-sdk-v1.42.0 operators.operatorframework.io/project_layout: go.kubebuilder.io/v4 - repository: https://github.com/netobserv/network-observability-operator + repository: https://github.com/netobserv/netobserv-operator support: NetObserv team labels: operatorframework.io/arch.amd64: supported @@ -528,7 +528,7 @@ spec: name: flowcollectorslices.flows.netobserv.io version: v1alpha1 - description: '`FlowMetric` is the schema for the custom metrics API, which allows - to generate more metrics out of flow logs. You can find examples here: https://github.com/netobserv/network-observability-operator/tree/main/config/samples/flowmetrics' + to generate more metrics out of flow logs. You can find examples here: https://github.com/netobserv/netobserv-operator/tree/main/config/samples/flowmetrics' displayName: Flow Metric kind: FlowMetric name: flowmetrics.flows.netobserv.io @@ -582,7 +582,7 @@ spec: ## Configuration - The `FlowCollector` resource is used to configure the operator and its managed components. A comprehensive documentation is [available here](https://github.com/netobserv/network-observability-operator/blob/1.11.1-community/docs/FlowCollector.md), and a full sample file [there](https://github.com/netobserv/network-observability-operator/blob/1.11.1-community/config/samples/flows_v1beta2_flowcollector.yaml). + The `FlowCollector` resource is used to configure the operator and its managed components. A comprehensive documentation is [available here](https://github.com/netobserv/netobserv-operator/blob/1.11.1-community/docs/FlowCollector.md), and a full sample file [there](https://github.com/netobserv/netobserv-operator/blob/1.11.1-community/config/samples/flows_v1beta2_flowcollector.yaml). To edit configuration in cluster, run: @@ -634,11 +634,11 @@ spec: This documentation includes: - - An [overview](https://github.com/netobserv/network-observability-operator#openshift-console) of the features, with screenshots - - More information on [configuring metrics](https://github.com/netobserv/network-observability-operator/blob/1.11.1-community/docs/Metrics.md). - - A [performance](https://github.com/netobserv/network-observability-operator#performance-fine-tuning) section, for fine-tuning - - A [security](https://github.com/netobserv/network-observability-operator#securing-data-and-communications) section - - An [F.A.Q.](https://github.com/netobserv/network-observability-operator#faq--troubleshooting) section + - An [overview](https://github.com/netobserv/netobserv-operator#openshift-console) of the features, with screenshots + - More information on [configuring metrics](https://github.com/netobserv/netobserv-operator/blob/1.11.1-community/docs/Metrics.md). + - A [performance](https://github.com/netobserv/netobserv-operator#performance-fine-tuning) section, for fine-tuning + - A [security](https://github.com/netobserv/netobserv-operator#securing-data-and-communications) section + - An [F.A.Q.](https://github.com/netobserv/netobserv-operator#faq--troubleshooting) section displayName: NetObserv Operator icon: - base64data: PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4KPCEtLSBHZW5lcmF0b3I6IEFkb2JlIElsbHVzdHJhdG9yIDI2LjAuMiwgU1ZHIEV4cG9ydCBQbHVnLUluIC4gU1ZHIFZlcnNpb246IDYuMDAgQnVpbGQgMCkgIC0tPgo8c3ZnIHZlcnNpb249IjEuMSIgaWQ9IkxheWVyXzEiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgeG1sbnM6eGxpbms9Imh0dHA6Ly93d3cudzMub3JnLzE5OTkveGxpbmsiIHg9IjBweCIgeT0iMHB4IgoJIHZpZXdCb3g9IjAgMCAxMDAgMTAwIiBzdHlsZT0iZW5hYmxlLWJhY2tncm91bmQ6bmV3IDAgMCAxMDAgMTAwOyIgeG1sOnNwYWNlPSJwcmVzZXJ2ZSI+CjxzdHlsZSB0eXBlPSJ0ZXh0L2NzcyI+Cgkuc3Qwe2ZpbGw6dXJsKCNTVkdJRF8xXyk7fQoJLnN0MXtmaWxsOiNGRkZGRkY7fQoJLnN0MntvcGFjaXR5OjAuNjt9Cgkuc3Qze29wYWNpdHk6MC41O30KCS5zdDR7b3BhY2l0eTowLjQ7fQo8L3N0eWxlPgo8Zz4KCTxnPgoJCTxnPgoJCQk8cmFkaWFsR3JhZGllbnQgaWQ9IlNWR0lEXzFfIiBjeD0iMTQuNzc1OCIgY3k9Ii0yLjk3NzEiIHI9IjkxLjYyNyIgZ3JhZGllbnRVbml0cz0idXNlclNwYWNlT25Vc2UiPgoJCQkJPHN0b3AgIG9mZnNldD0iMCIgc3R5bGU9InN0b3AtY29sb3I6IzNDM0ZBNiIvPgoJCQkJPHN0b3AgIG9mZnNldD0iMSIgc3R5bGU9InN0b3AtY29sb3I6IzNCMDM0MCIvPgoJCQk8L3JhZGlhbEdyYWRpZW50PgoJCQk8cGF0aCBjbGFzcz0ic3QwIiBkPSJNNTAsOTljLTEzLjMsMC0yNS40LTUuMy0zNC4yLTEzLjlDNi43LDc2LjIsMSw2My43LDEsNTBDMSwyMi45LDIyLjksMSw1MCwxYzEzLjcsMCwyNi4yLDUuNywzNS4xLDE0LjgKCQkJCUM5My43LDI0LjYsOTksMzYuNyw5OSw1MEM5OSw3Ny4xLDc3LjEsOTksNTAsOTl6Ii8+CgkJPC9nPgoJCTxnPgoJCQk8Y2lyY2xlIGNsYXNzPSJzdDEiIGN4PSIzNy41IiBjeT0iODEuOSIgcj0iNSIvPgoJCTwvZz4KCQk8cGF0aCBjbGFzcz0ic3QxIiBkPSJNNDguNiw5MS45bDE4LjgtNDMuM2MtMi41LTAuMS01LTAuNy03LjItMkwzMy4yLDY4LjJsMS40LTEuOGwyMC0yNS4xYy0xLjUtMi40LTIuMy01LjEtMi4zLTcuOUw5LDUyLjIKCQkJbDQ3LjYtMjkuOWwwLDBjMC4xLTAuMSwwLjItMC4yLDAuMi0wLjJjNi4xLTYuMSwxNS45LTYuMSwyMiwwbDAuMSwwLjFjNiw2LjEsNiwxNS45LTAuMSwyMS45Yy0wLjEsMC4xLTAuMiwwLjItMC4yLDAuMmwwLDAKCQkJTDQ4LjYsOTEuOXoiLz4KCQk8ZyBjbGFzcz0ic3QyIj4KCQkJPGNpcmNsZSBjbGFzcz0ic3QxIiBjeD0iNTAuMyIgY3k9IjE0LjciIHI9IjMuMSIvPgoJCTwvZz4KCQk8ZyBjbGFzcz0ic3QzIj4KCQkJPGNpcmNsZSBjbGFzcz0ic3QxIiBjeD0iMjcuNyIgY3k9IjU4IiByPSIxLjciLz4KCQk8L2c+CgkJPGc+CgkJCTxjaXJjbGUgY2xhc3M9InN0MSIgY3g9Ijc3LjQiIGN5PSI2OS4zIiByPSIxLjciLz4KCQk8L2c+CgkJPGc+CgkJCTxjaXJjbGUgY2xhc3M9InN0MSIgY3g9IjE2LjMiIGN5PSIzNi42IiByPSIxLjciLz4KCQk8L2c+CgkJPGcgY2xhc3M9InN0NCI+CgkJCTxjaXJjbGUgY2xhc3M9InN0MSIgY3g9IjYzLjciIGN5PSI4NS45IiByPSIyLjIiLz4KCQk8L2c+CgkJPGc+CgkJCTxjaXJjbGUgY2xhc3M9InN0MSIgY3g9IjI5LjQiIGN5PSIxOS42IiByPSI0LjgiLz4KCQk8L2c+CgkJPGcgY2xhc3M9InN0MyI+CgkJCTxjaXJjbGUgY2xhc3M9InN0MSIgY3g9Ijg4IiBjeT0iNTAiIHI9IjQuOCIvPgoJCTwvZz4KCTwvZz4KPC9nPgo8L3N2Zz4K @@ -1084,11 +1084,11 @@ spec: - observability links: - name: Project page - url: https://github.com/netobserv/network-observability-operator + url: https://github.com/netobserv/netobserv-operator - name: Issue tracker - url: https://github.com/netobserv/network-observability-operator/issues + url: https://github.com/netobserv/netobserv-operator/issues - name: Discussion board - url: https://github.com/netobserv/network-observability-operator/discussions + url: https://github.com/netobserv/netobserv-operator/discussions maintainers: - email: jpinsonn@redhat.com name: Julien Pinsonneau diff --git a/config/crd/bases/flows.netobserv.io_flowcollectors.yaml b/config/crd/bases/flows.netobserv.io_flowcollectors.yaml index 0c13af6541..743e8d82cf 100644 --- a/config/crd/bases/flows.netobserv.io_flowcollectors.yaml +++ b/config/crd/bases/flows.netobserv.io_flowcollectors.yaml @@ -3965,7 +3965,7 @@ spec: Because it cannot be tested with all CNIs, this option is only enabled by default when NetObserv runs in a known supported environment, and it is disabled by default otherwise. When disabled, it is highly recommended to create network policies manually, to prevent undesired accesses. - More information: https://github.com/netobserv/network-observability-operator/blob/main/docs/NetworkPolicy.md. + More information: https://github.com/netobserv/netobserv-operator/blob/main/docs/NetworkPolicy.md. type: boolean type: object processor: @@ -5417,7 +5417,7 @@ spec: `disableAlerts` is a list of alert groups that should be disabled from the default set of alerts. Possible values are: `NetObservNoFlows`, `NetObservLokiError`, `PacketDropsByKernel`, `PacketDropsByDevice`, `IPsecErrors`, `NetpolDenied`, `LatencyHighTrend`, `DNSErrors`, `DNSNxDomain`, `ExternalEgressHighTrend`, `ExternalIngressHighTrend`, `Ingress5xxErrors`, `IngressHTTPLatencyTrend`. - More information on alerts: https://github.com/netobserv/network-observability-operator/blob/main/docs/HealthRules.md + More information on alerts: https://github.com/netobserv/netobserv-operator/blob/main/docs/HealthRules.md items: type: string type: array @@ -5425,7 +5425,7 @@ spec: description: |- `healthRules` is a list of health rules to be created for Prometheus, organized by templates and variants. Each health rule can be configured to generate either alerts or recording rules based on the mode field. - More information on health rules: https://github.com/netobserv/network-observability-operator/blob/main/docs/HealthRules.md + More information on health rules: https://github.com/netobserv/netobserv-operator/blob/main/docs/HealthRules.md items: properties: mode: @@ -5446,7 +5446,7 @@ spec: Possible values are: `PacketDropsByKernel`, `PacketDropsByDevice`, `IPsecErrors`, `NetpolDenied`, `LatencyHighTrend`, `DNSErrors`, `DNSNxDomain`, `ExternalEgressHighTrend`, `ExternalIngressHighTrend`, `Ingress5xxErrors`, `IngressHTTPLatencyTrend`. Note: `NetObservNoFlows` and `NetObservLokiError` are alert-only and cannot be used as health rules. - More information on health rules: https://github.com/netobserv/network-observability-operator/blob/main/docs/HealthRules.md + More information on health rules: https://github.com/netobserv/netobserv-operator/blob/main/docs/HealthRules.md enum: - PacketDropsByKernel - PacketDropsByDevice @@ -5529,9 +5529,9 @@ spec: `workload_egress_bytes_total`, `namespace_drop_packets_total` (when `PacketDrop` feature is enabled), `namespace_rtt_seconds` (when `FlowRTT` feature is enabled), `namespace_dns_latency_seconds` (when `DNSTracking` feature is enabled), `namespace_network_policy_events_total` (when `NetworkEvents` feature is enabled). - More information, with full list of available metrics: https://github.com/netobserv/network-observability-operator/blob/main/docs/Metrics.md + More information, with full list of available metrics: https://github.com/netobserv/netobserv-operator/blob/main/docs/Metrics.md items: - description: Metric name. More information in https://github.com/netobserv/network-observability-operator/blob/main/docs/Metrics.md. + description: Metric name. More information in https://github.com/netobserv/netobserv-operator/blob/main/docs/Metrics.md. enum: - namespace_egress_bytes_total - namespace_egress_packets_total diff --git a/config/csv/bases/netobserv-operator.clusterserviceversion.yaml b/config/csv/bases/netobserv-operator.clusterserviceversion.yaml index 56768a1339..56c25e12fd 100644 --- a/config/csv/bases/netobserv-operator.clusterserviceversion.yaml +++ b/config/csv/bases/netobserv-operator.clusterserviceversion.yaml @@ -13,7 +13,7 @@ metadata: operatorframework.io/suggested-namespace: openshift-netobserv-operator operatorframework.io/initialization-resource: '{"apiVersion":"flows.netobserv.io/v1beta2", "kind":"FlowCollector","metadata":{"name":"cluster"},"spec": {}}' - repository: https://github.com/netobserv/network-observability-operator + repository: https://github.com/netobserv/netobserv-operator labels: operatorframework.io/arch.amd64: supported operatorframework.io/arch.arm64: supported @@ -292,7 +292,7 @@ spec: - urn:alm:descriptor:io.kubernetes.conditions - description: '`FlowMetric` is the schema for the custom metrics API, which allows to generate more metrics out of flow logs. - You can find examples here: https://github.com/netobserv/network-observability-operator/tree/main/config/samples/flowmetrics' + You can find examples here: https://github.com/netobserv/netobserv-operator/tree/main/config/samples/flowmetrics' displayName: Flow Metric kind: FlowMetric name: flowmetrics.flows.netobserv.io @@ -331,11 +331,11 @@ spec: - observability links: - name: Project page - url: https://github.com/netobserv/network-observability-operator + url: https://github.com/netobserv/netobserv-operator - name: Issue tracker - url: https://github.com/netobserv/network-observability-operator/issues + url: https://github.com/netobserv/netobserv-operator/issues - name: Discussion board - url: https://github.com/netobserv/network-observability-operator/discussions + url: https://github.com/netobserv/netobserv-operator/discussions maintainers: - email: jpinsonn@redhat.com name: Julien Pinsonneau diff --git a/config/descriptions/ocp.md b/config/descriptions/ocp.md index 7e6316d97c..593c23dd2d 100644 --- a/config/descriptions/ocp.md +++ b/config/descriptions/ocp.md @@ -42,7 +42,7 @@ In that case, you still get the Prometheus metrics or export raw flows to a cust ## Configuration -The `FlowCollector` resource is used to configure the operator and its managed components. A comprehensive documentation is [available here](https://github.com/netobserv/network-observability-operator/blob/1.11.1-community/docs/FlowCollector.md), and a full sample file [there](https://github.com/netobserv/network-observability-operator/blob/1.11.1-community/config/samples/flows_v1beta2_flowcollector.yaml). +The `FlowCollector` resource is used to configure the operator and its managed components. A comprehensive documentation is [available here](https://github.com/netobserv/netobserv-operator/blob/1.11.1-community/docs/FlowCollector.md), and a full sample file [there](https://github.com/netobserv/netobserv-operator/blob/1.11.1-community/config/samples/flows_v1beta2_flowcollector.yaml). To edit configuration in cluster, run: @@ -94,8 +94,8 @@ Please refer to the documentation on GitHub for more information. This documentation includes: -- An [overview](https://github.com/netobserv/network-observability-operator#openshift-console) of the features, with screenshots -- More information on [configuring metrics](https://github.com/netobserv/network-observability-operator/blob/1.11.1-community/docs/Metrics.md). -- A [performance](https://github.com/netobserv/network-observability-operator#performance-fine-tuning) section, for fine-tuning -- A [security](https://github.com/netobserv/network-observability-operator#securing-data-and-communications) section -- An [F.A.Q.](https://github.com/netobserv/network-observability-operator#faq--troubleshooting) section +- An [overview](https://github.com/netobserv/netobserv-operator#openshift-console) of the features, with screenshots +- More information on [configuring metrics](https://github.com/netobserv/netobserv-operator/blob/1.11.1-community/docs/Metrics.md). +- A [performance](https://github.com/netobserv/netobserv-operator#performance-fine-tuning) section, for fine-tuning +- A [security](https://github.com/netobserv/netobserv-operator#securing-data-and-communications) section +- An [F.A.Q.](https://github.com/netobserv/netobserv-operator#faq--troubleshooting) section diff --git a/config/descriptions/upstream.md b/config/descriptions/upstream.md index fd58f0677d..589037ef20 100644 --- a/config/descriptions/upstream.md +++ b/config/descriptions/upstream.md @@ -46,7 +46,7 @@ In that case, you still get the Prometheus metrics or export raw flows to a cust ## Configuration -The `FlowCollector` resource is used to configure the operator and its managed components. A comprehensive documentation is [available here](https://github.com/netobserv/network-observability-operator/blob/1.11.1-community/docs/FlowCollector.md), and a full sample file [there](https://github.com/netobserv/network-observability-operator/blob/1.11.1-community/config/samples/flows_v1beta2_flowcollector.yaml). +The `FlowCollector` resource is used to configure the operator and its managed components. A comprehensive documentation is [available here](https://github.com/netobserv/netobserv-operator/blob/1.11.1-community/docs/FlowCollector.md), and a full sample file [there](https://github.com/netobserv/netobserv-operator/blob/1.11.1-community/config/samples/flows_v1beta2_flowcollector.yaml). To edit configuration in cluster, run: @@ -98,8 +98,8 @@ Please refer to the documentation on GitHub for more information. This documentation includes: -- An [overview](https://github.com/netobserv/network-observability-operator#openshift-console) of the features, with screenshots -- More information on [configuring metrics](https://github.com/netobserv/network-observability-operator/blob/1.11.1-community/docs/Metrics.md). -- A [performance](https://github.com/netobserv/network-observability-operator#performance-fine-tuning) section, for fine-tuning -- A [security](https://github.com/netobserv/network-observability-operator#securing-data-and-communications) section -- An [F.A.Q.](https://github.com/netobserv/network-observability-operator#faq--troubleshooting) section +- An [overview](https://github.com/netobserv/netobserv-operator#openshift-console) of the features, with screenshots +- More information on [configuring metrics](https://github.com/netobserv/netobserv-operator/blob/1.11.1-community/docs/Metrics.md). +- A [performance](https://github.com/netobserv/netobserv-operator#performance-fine-tuning) section, for fine-tuning +- A [security](https://github.com/netobserv/netobserv-operator#securing-data-and-communications) section +- An [F.A.Q.](https://github.com/netobserv/netobserv-operator#faq--troubleshooting) section diff --git a/config/samples/flowmetrics/az_aware_worloads_traffic.yaml b/config/samples/flowmetrics/az_aware_worloads_traffic.yaml index 009b72d810..afc943bf23 100644 --- a/config/samples/flowmetrics/az_aware_worloads_traffic.yaml +++ b/config/samples/flowmetrics/az_aware_worloads_traffic.yaml @@ -1,6 +1,6 @@ # This metric provides byte-rate ingress traffic per source and destination workload, with availability zones # The processor feature "addZone" must be enabled. -# More examples in https://github.com/netobserv/network-observability-operator/tree/main/config/samples/flowmetrics +# More examples in https://github.com/netobserv/netobserv-operator/tree/main/config/samples/flowmetrics apiVersion: flows.netobserv.io/v1alpha1 kind: FlowMetric metadata: diff --git a/config/samples/flowmetrics/cluster_external_egress_rtt_seconds.yaml b/config/samples/flowmetrics/cluster_external_egress_rtt_seconds.yaml index a41aa1bc89..de1d48f4f8 100644 --- a/config/samples/flowmetrics/cluster_external_egress_rtt_seconds.yaml +++ b/config/samples/flowmetrics/cluster_external_egress_rtt_seconds.yaml @@ -1,6 +1,6 @@ # This metric provides egress cluster-external TCP latency (sRTT) per host and workload. It also provides dashboard charts. # The eBPF Agent feature "FlowRTT" must be enabled. -# More examples in https://github.com/netobserv/network-observability-operator/tree/main/config/samples/flowmetrics +# More examples in https://github.com/netobserv/netobserv-operator/tree/main/config/samples/flowmetrics apiVersion: flows.netobserv.io/v1alpha1 kind: FlowMetric metadata: diff --git a/config/samples/flowmetrics/cluster_external_egress_traffic.yaml b/config/samples/flowmetrics/cluster_external_egress_traffic.yaml index 15f3080230..19ca2abcb1 100644 --- a/config/samples/flowmetrics/cluster_external_egress_traffic.yaml +++ b/config/samples/flowmetrics/cluster_external_egress_traffic.yaml @@ -1,5 +1,5 @@ # This metric provides egress cluster-external byte-rate per host and workload. It also provides dashboard charts. -# More examples in https://github.com/netobserv/network-observability-operator/tree/main/config/samples/flowmetrics +# More examples in https://github.com/netobserv/netobserv-operator/tree/main/config/samples/flowmetrics apiVersion: flows.netobserv.io/v1alpha1 kind: FlowMetric metadata: diff --git a/config/samples/flowmetrics/cluster_external_ingress_rtt_seconds.yaml b/config/samples/flowmetrics/cluster_external_ingress_rtt_seconds.yaml index 1a6aaad615..e5dec048b3 100644 --- a/config/samples/flowmetrics/cluster_external_ingress_rtt_seconds.yaml +++ b/config/samples/flowmetrics/cluster_external_ingress_rtt_seconds.yaml @@ -1,6 +1,6 @@ # This metric provides ingress cluster-external TCP latency (sRTT) per host and workload. It also provides dashboard charts. # The eBPF Agent feature "FlowRTT" must be enabled. -# More examples in https://github.com/netobserv/network-observability-operator/tree/main/config/samples/flowmetrics +# More examples in https://github.com/netobserv/netobserv-operator/tree/main/config/samples/flowmetrics apiVersion: flows.netobserv.io/v1alpha1 kind: FlowMetric metadata: diff --git a/config/samples/flowmetrics/cluster_external_ingress_traffic.yaml b/config/samples/flowmetrics/cluster_external_ingress_traffic.yaml index e9b64ab3a2..5687bc7a89 100644 --- a/config/samples/flowmetrics/cluster_external_ingress_traffic.yaml +++ b/config/samples/flowmetrics/cluster_external_ingress_traffic.yaml @@ -1,5 +1,5 @@ # This metric provides ingress cluster-external byte-rate per host and workload. It also provides dashboard charts. -# More examples in https://github.com/netobserv/network-observability-operator/tree/main/config/samples/flowmetrics +# More examples in https://github.com/netobserv/netobserv-operator/tree/main/config/samples/flowmetrics apiVersion: flows.netobserv.io/v1alpha1 kind: FlowMetric metadata: diff --git a/config/samples/flowmetrics/dns_requests.yaml b/config/samples/flowmetrics/dns_requests.yaml index 227b2b29fe..8b4f76cf0f 100644 --- a/config/samples/flowmetrics/dns_requests.yaml +++ b/config/samples/flowmetrics/dns_requests.yaml @@ -1,5 +1,5 @@ # Metric tracking DNS requests -# More examples in https://github.com/netobserv/network-observability-operator/tree/main/config/samples/flowmetrics +# More examples in https://github.com/netobserv/netobserv-operator/tree/main/config/samples/flowmetrics apiVersion: flows.netobserv.io/v1alpha1 kind: FlowMetric metadata: diff --git a/config/samples/flowmetrics/dns_responses.yaml b/config/samples/flowmetrics/dns_responses.yaml index ff31ff3626..1867fc3d6c 100644 --- a/config/samples/flowmetrics/dns_responses.yaml +++ b/config/samples/flowmetrics/dns_responses.yaml @@ -1,5 +1,5 @@ # Metric tracking DNS responses -# More examples in https://github.com/netobserv/network-observability-operator/tree/main/config/samples/flowmetrics +# More examples in https://github.com/netobserv/netobserv-operator/tree/main/config/samples/flowmetrics apiVersion: flows.netobserv.io/v1alpha1 kind: FlowMetric metadata: diff --git a/config/samples/flowmetrics/flows_with_flags_per_destination.yaml b/config/samples/flowmetrics/flows_with_flags_per_destination.yaml index 5a4865d71d..57715b3bd6 100644 --- a/config/samples/flowmetrics/flows_with_flags_per_destination.yaml +++ b/config/samples/flowmetrics/flows_with_flags_per_destination.yaml @@ -1,6 +1,6 @@ # This metric counts flows per destination host and resource, with TCP flags. Combined with alerts, it can be used to detect # undesired behaviours such as SYN-flood attacks targetting workloads in cluster. -# More examples in https://github.com/netobserv/network-observability-operator/tree/main/config/samples/flowmetrics +# More examples in https://github.com/netobserv/netobserv-operator/tree/main/config/samples/flowmetrics apiVersion: flows.netobserv.io/v1alpha1 kind: FlowMetric metadata: diff --git a/config/samples/flowmetrics/flows_with_flags_per_source.yaml b/config/samples/flowmetrics/flows_with_flags_per_source.yaml index 5b74e6d240..a3cc4a3334 100644 --- a/config/samples/flowmetrics/flows_with_flags_per_source.yaml +++ b/config/samples/flowmetrics/flows_with_flags_per_source.yaml @@ -1,6 +1,6 @@ # This metric counts flows per source host and resource, with TCP flags. Combined with alerts, it can be used to detect # undesired behaviours such as SYN-flood attacks originating from the cluster. -# More examples in https://github.com/netobserv/network-observability-operator/tree/main/config/samples/flowmetrics +# More examples in https://github.com/netobserv/netobserv-operator/tree/main/config/samples/flowmetrics apiVersion: flows.netobserv.io/v1alpha1 kind: FlowMetric metadata: diff --git a/config/samples/flowmetrics/network-policies.yaml b/config/samples/flowmetrics/network-policies.yaml index c2d1b347db..a3d8a6c613 100644 --- a/config/samples/flowmetrics/network-policies.yaml +++ b/config/samples/flowmetrics/network-policies.yaml @@ -1,5 +1,5 @@ # Count network policy events -# More examples in https://github.com/netobserv/network-observability-operator/tree/main/config/samples/flowmetrics +# More examples in https://github.com/netobserv/netobserv-operator/tree/main/config/samples/flowmetrics apiVersion: flows.netobserv.io/v1alpha1 kind: FlowMetric metadata: diff --git a/config/samples/flowmetrics/per-interface.yaml b/config/samples/flowmetrics/per-interface.yaml index ec6b9be510..93ef6050d8 100644 --- a/config/samples/flowmetrics/per-interface.yaml +++ b/config/samples/flowmetrics/per-interface.yaml @@ -1,5 +1,5 @@ # Count flows per network interface -# More examples in https://github.com/netobserv/network-observability-operator/tree/main/config/samples/flowmetrics +# More examples in https://github.com/netobserv/netobserv-operator/tree/main/config/samples/flowmetrics apiVersion: flows.netobserv.io/v1alpha1 kind: FlowMetric metadata: diff --git a/config/samples/flowmetrics/pods_egress_rtt_seconds.yaml b/config/samples/flowmetrics/pods_egress_rtt_seconds.yaml index 6eeee8537d..688a4e5704 100644 --- a/config/samples/flowmetrics/pods_egress_rtt_seconds.yaml +++ b/config/samples/flowmetrics/pods_egress_rtt_seconds.yaml @@ -1,6 +1,6 @@ # This metric provides egress (Tx) TCP latency (sRTT) per pod. It also provides dashboard charts. # The eBPF Agent feature "FlowRTT" must be enabled. -# More examples in https://github.com/netobserv/network-observability-operator/tree/main/config/samples/flowmetrics +# More examples in https://github.com/netobserv/netobserv-operator/tree/main/config/samples/flowmetrics apiVersion: flows.netobserv.io/v1alpha1 kind: FlowMetric metadata: diff --git a/config/samples/flowmetrics/pods_egress_traffic.yaml b/config/samples/flowmetrics/pods_egress_traffic.yaml index b9541d61e5..b1bf973c62 100644 --- a/config/samples/flowmetrics/pods_egress_traffic.yaml +++ b/config/samples/flowmetrics/pods_egress_traffic.yaml @@ -1,5 +1,5 @@ # This metric provides egress (Tx) byte-rate per pod. It also provides a dashboard chart. -# More examples in https://github.com/netobserv/network-observability-operator/tree/main/config/samples/flowmetrics +# More examples in https://github.com/netobserv/netobserv-operator/tree/main/config/samples/flowmetrics apiVersion: flows.netobserv.io/v1alpha1 kind: FlowMetric metadata: diff --git a/config/samples/flowmetrics/pods_ingress_rtt_seconds.yaml b/config/samples/flowmetrics/pods_ingress_rtt_seconds.yaml index 9d7a6507fc..665aee94b8 100644 --- a/config/samples/flowmetrics/pods_ingress_rtt_seconds.yaml +++ b/config/samples/flowmetrics/pods_ingress_rtt_seconds.yaml @@ -1,6 +1,6 @@ # This metric provides ingress (Rx) TCP latency (sRTT) per pod. It also provides dashboard charts. # The eBPF Agent feature "FlowRTT" must be enabled. -# More examples in https://github.com/netobserv/network-observability-operator/tree/main/config/samples/flowmetrics +# More examples in https://github.com/netobserv/netobserv-operator/tree/main/config/samples/flowmetrics apiVersion: flows.netobserv.io/v1alpha1 kind: FlowMetric metadata: diff --git a/config/samples/flowmetrics/pods_ingress_traffic.yaml b/config/samples/flowmetrics/pods_ingress_traffic.yaml index ec7405bb26..9f8ff8a923 100644 --- a/config/samples/flowmetrics/pods_ingress_traffic.yaml +++ b/config/samples/flowmetrics/pods_ingress_traffic.yaml @@ -1,5 +1,5 @@ # This metric provides ingress (Rx) byte-rate per pod. It also provides a dashboard chart. -# More examples in https://github.com/netobserv/network-observability-operator/tree/main/config/samples/flowmetrics +# More examples in https://github.com/netobserv/netobserv-operator/tree/main/config/samples/flowmetrics apiVersion: flows.netobserv.io/v1alpha1 kind: FlowMetric metadata: diff --git a/config/samples/flowmetrics/pods_openshift_ingress_traffic.yaml b/config/samples/flowmetrics/pods_openshift_ingress_traffic.yaml index ed44c17c3f..b1d7747010 100644 --- a/config/samples/flowmetrics/pods_openshift_ingress_traffic.yaml +++ b/config/samples/flowmetrics/pods_openshift_ingress_traffic.yaml @@ -1,5 +1,5 @@ # This metric provides ingress (Rx) byte-rate traffic from openshift-ingress routers, per destination pod. -# More examples in https://github.com/netobserv/network-observability-operator/tree/main/config/samples/flowmetrics +# More examples in https://github.com/netobserv/netobserv-operator/tree/main/config/samples/flowmetrics apiVersion: flows.netobserv.io/v1alpha1 kind: FlowMetric metadata: diff --git a/config/samples/flowmetrics/root_ports_flows.yaml b/config/samples/flowmetrics/root_ports_flows.yaml index 1cdee3ff9e..4017ed09bb 100644 --- a/config/samples/flowmetrics/root_ports_flows.yaml +++ b/config/samples/flowmetrics/root_ports_flows.yaml @@ -1,5 +1,5 @@ # This metric provides a count of flows per destination ports smaller than 1029 (feel free to edit the regex to better suit your needs), with source and destination workloads -# More examples in https://github.com/netobserv/network-observability-operator/tree/main/config/samples/flowmetrics +# More examples in https://github.com/netobserv/netobserv-operator/tree/main/config/samples/flowmetrics apiVersion: flows.netobserv.io/v1alpha1 kind: FlowMetric metadata: diff --git a/config/samples/flowmetrics/services_ports_traffic.yaml b/config/samples/flowmetrics/services_ports_traffic.yaml index 9a1a2c9f22..d5e33ff3a5 100644 --- a/config/samples/flowmetrics/services_ports_traffic.yaml +++ b/config/samples/flowmetrics/services_ports_traffic.yaml @@ -1,5 +1,5 @@ # This metric provides byte-rate per service and port. It also provides a dashboard chart. -# More examples in https://github.com/netobserv/network-observability-operator/tree/main/config/samples/flowmetrics +# More examples in https://github.com/netobserv/netobserv-operator/tree/main/config/samples/flowmetrics apiVersion: flows.netobserv.io/v1alpha1 kind: FlowMetric metadata: diff --git a/config/samples/flowmetrics/traffic_across_az.yaml b/config/samples/flowmetrics/traffic_across_az.yaml index 8f7cd2bf1b..cafc3395e8 100644 --- a/config/samples/flowmetrics/traffic_across_az.yaml +++ b/config/samples/flowmetrics/traffic_across_az.yaml @@ -1,7 +1,7 @@ # This metric provides byte-rate traffic crossing availability zones, per source and destination workloads. It also provides dashboard charts. # This show-cases the use of relative filters (SrcK8S_Zone not equals to DstK8S_Zone). # The processor feature "addZone" must be enabled. -# More examples in https://github.com/netobserv/network-observability-operator/tree/main/config/samples/flowmetrics +# More examples in https://github.com/netobserv/netobserv-operator/tree/main/config/samples/flowmetrics apiVersion: flows.netobserv.io/v1alpha1 kind: FlowMetric metadata: diff --git a/config/samples/flowmetrics/workload-syn-in.yaml b/config/samples/flowmetrics/workload-syn-in.yaml index 42e70f1c4b..631eb1f330 100644 --- a/config/samples/flowmetrics/workload-syn-in.yaml +++ b/config/samples/flowmetrics/workload-syn-in.yaml @@ -1,5 +1,5 @@ # Workload flows matrix for TCP/SYN traffic, including destination port, with labels remapped for focusing on incoming traffic -# More examples in https://github.com/netobserv/network-observability-operator/tree/main/config/samples/flowmetrics +# More examples in https://github.com/netobserv/netobserv-operator/tree/main/config/samples/flowmetrics apiVersion: flows.netobserv.io/v1alpha1 kind: FlowMetric metadata: diff --git a/config/samples/flowmetrics/workload-syn-out.yaml b/config/samples/flowmetrics/workload-syn-out.yaml index 82e967c208..bf8771ce39 100644 --- a/config/samples/flowmetrics/workload-syn-out.yaml +++ b/config/samples/flowmetrics/workload-syn-out.yaml @@ -1,5 +1,5 @@ # Workload flows matrix for TCP/SYN traffic, including destination port, with labels remapped for focusing on outgoing traffic -# More examples in https://github.com/netobserv/network-observability-operator/tree/main/config/samples/flowmetrics +# More examples in https://github.com/netobserv/netobserv-operator/tree/main/config/samples/flowmetrics apiVersion: flows.netobserv.io/v1alpha1 kind: FlowMetric metadata: diff --git a/config/samples/flows_v1alpha1_flowmetric.yaml b/config/samples/flows_v1alpha1_flowmetric.yaml index 223bef56a9..bf9b441de6 100644 --- a/config/samples/flows_v1alpha1_flowmetric.yaml +++ b/config/samples/flows_v1alpha1_flowmetric.yaml @@ -3,7 +3,7 @@ kind: FlowMetric metadata: name: flowmetric-sample spec: - # More examples in https://github.com/netobserv/network-observability-operator/tree/main/config/samples/flowmetrics + # More examples in https://github.com/netobserv/netobserv-operator/tree/main/config/samples/flowmetrics type: Counter valueField: Bytes direction: Ingress diff --git a/docs/Architecture.md b/docs/Architecture.md index da35ab3928..c52f538428 100644 --- a/docs/Architecture.md +++ b/docs/Architecture.md @@ -17,14 +17,14 @@ The components are: - It derives all flows into metric counters, for Prometheus. - Raw flows can be exported to Loki and/or custom exporters (Kafka, IPFIX, OpenTelemetry). - As a standalone, FLP is very flexible and configurable. It supports more inputs and outputs, allows more arbitrary filters, sampling, aggregations, relabelling, etc. When deployed via the operator, only a subset of its capacities is used. -- When used in OpenShift, [a Console plugin](https://github.com/netobserv/network-observability-console-plugin) for flows visualization with powerful filtering options, a topology representation and more (outside of OpenShift, [it can be deployed as a standalone](https://github.com/netobserv/network-observability-operator/blob/main/FAQ.md#how-do-i-visualize-flows-and-metrics)). +- [A web console](https://github.com/netobserv/netobserv-web-console) for flows visualization with powerful filtering options, a topology representation and more. - It provides a polished web UI to visualize and explore the flow logs and metrics stored in Loki and/or Prometheus. - Different views include metrics overview, a network topology and a table listing raw flows logs. - It supports multi-tenant access, making it relevant for various use cases: cluster/network admins, SREs, development teams... -- [An operator](https://github.com/netobserv/network-observability-operator) that manages all of the above. - - It provides three APIs (CRD), one called [FlowCollector](https://github.com/netobserv/network-observability-operator/blob/main/docs/FlowCollector.md), which configures and pilots the whole deployment, another called [FlowCollectorSlice](https://github.com/netobserv/network-observability-operator/blob/main/docs/FlowCollectorSlice.md) for per-tenant configuration, and lastly [FlowMetrics](https://github.com/netobserv/network-observability-operator/blob/main/docs/FlowMetric.md) which allows to customize which metrics to generate out of flow logs. +- [An operator](https://github.com/netobserv/netobserv-operator) that manages all of the above. + - It provides three APIs (CRD), one called [FlowCollector](https://github.com/netobserv/netobserv-operator/blob/main/docs/FlowCollector.md), which configures and pilots the whole deployment, another called [FlowCollectorSlice](https://github.com/netobserv/netobserv-operator/blob/main/docs/FlowCollectorSlice.md) for per-tenant configuration, and lastly [FlowMetrics](https://github.com/netobserv/netobserv-operator/blob/main/docs/FlowMetric.md) which allows to customize which metrics to generate out of flow logs. - As an [OLM operator](https://olm.operatorframework.io/), it is designed with `operator-sdk`, and allows subscriptions for easy updates. -- [A CLI](https://github.com/netobserv/network-observability-cli) that also manages some of the above components, for on-demand monitoring and packet capture. +- [A CLI](https://github.com/netobserv/netobserv-cli) that also manages some of the above components, for on-demand monitoring and packet capture. - It is provided as a `kubectl` or `oc` plugin, allowing to capture flows (similar to what the operator does, except it's on-demand and in the terminal), full packets (much like a `tcpdump` command) or metrics. - It is also available via [Krew](https://krew.sigs.k8s.io/). - It offers a live visualization via a TUI. For metrics, when used in OpenShift, it provides out-of-the-box dashboards. diff --git a/docs/FlowCollector.md b/docs/FlowCollector.md index df5c3e44ce..289a6cd099 100644 --- a/docs/FlowCollector.md +++ b/docs/FlowCollector.md @@ -8437,7 +8437,7 @@ These network policies better isolate the NetObserv components to prevent undesi Because it cannot be tested with all CNIs, this option is only enabled by default when NetObserv runs in a known supported environment, and it is disabled by default otherwise. When disabled, it is highly recommended to create network policies manually, to prevent undesired accesses. -More information: https://github.com/netobserv/network-observability-operator/blob/main/docs/NetworkPolicy.md.
+More information: https://github.com/netobserv/netobserv-operator/blob/main/docs/NetworkPolicy.md.
false @@ -11588,7 +11588,7 @@ available.
`disableAlerts` is a list of alert groups that should be disabled from the default set of alerts. Possible values are: `NetObservNoFlows`, `NetObservLokiError`, `PacketDropsByKernel`, `PacketDropsByDevice`, `IPsecErrors`, `NetpolDenied`, `LatencyHighTrend`, `DNSErrors`, `DNSNxDomain`, `ExternalEgressHighTrend`, `ExternalIngressHighTrend`, `Ingress5xxErrors`, `IngressHTTPLatencyTrend`. -More information on alerts: https://github.com/netobserv/network-observability-operator/blob/main/docs/HealthRules.md
+More information on alerts: https://github.com/netobserv/netobserv-operator/blob/main/docs/HealthRules.md
false @@ -11597,7 +11597,7 @@ More information on alerts: https://github.com/netobserv/network-observability-o `healthRules` is a list of health rules to be created for Prometheus, organized by templates and variants. Each health rule can be configured to generate either alerts or recording rules based on the mode field. -More information on health rules: https://github.com/netobserv/network-observability-operator/blob/main/docs/HealthRules.md
+More information on health rules: https://github.com/netobserv/netobserv-operator/blob/main/docs/HealthRules.md
false @@ -11613,7 +11613,7 @@ Metrics enabled by default are: `workload_egress_bytes_total`, `namespace_drop_packets_total` (when `PacketDrop` feature is enabled), `namespace_rtt_seconds` (when `FlowRTT` feature is enabled), `namespace_dns_latency_seconds` (when `DNSTracking` feature is enabled), `namespace_network_policy_events_total` (when `NetworkEvents` feature is enabled). -More information, with full list of available metrics: https://github.com/netobserv/network-observability-operator/blob/main/docs/Metrics.md
+More information, with full list of available metrics: https://github.com/netobserv/netobserv-operator/blob/main/docs/Metrics.md
false @@ -11651,7 +11651,7 @@ More information, with full list of available metrics: https://github.com/netobs Possible values are: `PacketDropsByKernel`, `PacketDropsByDevice`, `IPsecErrors`, `NetpolDenied`, `LatencyHighTrend`, `DNSErrors`, `DNSNxDomain`, `ExternalEgressHighTrend`, `ExternalIngressHighTrend`, `Ingress5xxErrors`, `IngressHTTPLatencyTrend`. Note: `NetObservNoFlows` and `NetObservLokiError` are alert-only and cannot be used as health rules. -More information on health rules: https://github.com/netobserv/network-observability-operator/blob/main/docs/HealthRules.md
+More information on health rules: https://github.com/netobserv/netobserv-operator/blob/main/docs/HealthRules.md

Enum: PacketDropsByKernel, PacketDropsByDevice, IPsecErrors, NetpolDenied, LatencyHighTrend, DNSErrors, DNSNxDomain, ExternalEgressHighTrend, ExternalIngressHighTrend, Ingress5xxErrors, IngressHTTPLatencyTrend
diff --git a/docs/Konflux.md b/docs/Konflux.md index 1e578f84df..9b9d942be6 100644 --- a/docs/Konflux.md +++ b/docs/Konflux.md @@ -36,9 +36,9 @@ When using Konflux to release an operator, it is required to use a File Based Ca Konflux will regulary create new pull requests, there are three categories : -- [Nudging pull request](https://github.com/netobserv/network-observability-operator/pull/969) To upgrade the reference to another component -- [Konflux tasks update](https://github.com/netobserv/network-observability-operator/pull/787) Up to date tasks are required to pass security check during release. Also the migration note sometimes contains instruction to some required actions -- [Dependencies update](https://github.com/netobserv/network-observability-operator/pull/962) Kondlux internally use [https://github.com/renovatebot/renovate](renovate) to automatically create this PR. +- [Nudging pull request](https://github.com/netobserv/netobserv-operator/pull/969) To upgrade the reference to another component +- [Konflux tasks update](https://github.com/netobserv/netobserv-operator/pull/787) Up to date tasks are required to pass security check during release. Also the migration note sometimes contains instruction to some required actions +- [Dependencies update](https://github.com/netobserv/netobserv-operator/pull/962) Kondlux internally use [https://github.com/renovatebot/renovate](renovate) to automatically create this PR. ## Deploying diff --git a/docs/Metrics.md b/docs/Metrics.md index ec6d0d9598..3ae6f23e28 100644 --- a/docs/Metrics.md +++ b/docs/Metrics.md @@ -73,7 +73,7 @@ The full list of fields is [available there](./flows-format.adoc). The "Cardinal Be also aware that for each field used as a label, the fields cardinality is potentially multiplied - and this is especially true when mixing Source and Destination fields. For instance, using `SrcK8S_Name` or `DstK8S_Name` (ie. Pod/Node/Service names) alone as a label might be reasonable, but using both `SrcK8S_Name` and `DstK8S_Name` in the same metric potentially generates the square of the cardinality of Pods/Nodes/Services. -Don't hesitate to [reach out](https://github.com/netobserv/network-observability-operator/discussions/new/choose) if you need more guidance. +Don't hesitate to [reach out](https://github.com/netobserv/netobserv-operator/discussions/new/choose) if you need more guidance. Some of those fields require special features to be enabled in `FlowCollector`, such as `TimeFlowRttNs` via `spec.agent.ebpf.features` or `Src/DstK8S_Zone` via `spec.processor.addZone`. @@ -133,7 +133,7 @@ Since the RTT is provided as nanos in flows, we use a divider of 1 billion to co ### More examples -You can find more examples in https://github.com/netobserv/network-observability-operator/tree/main/config/samples/flowmetrics. +You can find more examples in https://github.com/netobserv/netobserv-operator/tree/main/config/samples/flowmetrics. ### Charts (OpenShift only) diff --git a/docs/flowcollector-flows-netobserv-io-v1beta2.adoc b/docs/flowcollector-flows-netobserv-io-v1beta2.adoc index 344c751951..c6164b89fb 100644 --- a/docs/flowcollector-flows-netobserv-io-v1beta2.adoc +++ b/docs/flowcollector-flows-netobserv-io-v1beta2.adoc @@ -3122,13 +3122,13 @@ Type:: | `disableAlerts` is a list of alert groups that should be disabled from the default set of alerts. Possible values are: `NetObservNoFlows`, `NetObservLokiError`, `PacketDropsByKernel`, `PacketDropsByDevice`, `IPsecErrors`, `NetpolDenied`, `LatencyHighTrend`, `DNSErrors`, `DNSNxDomain`, `ExternalEgressHighTrend`, `ExternalIngressHighTrend`, `Ingress5xxErrors`, `IngressHTTPLatencyTrend`. -More information on alerts: https://github.com/netobserv/network-observability-operator/blob/main/docs/HealthRules.md +More information on alerts: https://github.com/netobserv/netobserv-operator/blob/main/docs/HealthRules.md | `healthRules` | `array` | `healthRules` is a list of health rules to be created for Prometheus, organized by templates and variants. Each health rule can be configured to generate either alerts or recording rules based on the mode field. -More information on health rules: https://github.com/netobserv/network-observability-operator/blob/main/docs/HealthRules.md +More information on health rules: https://github.com/netobserv/netobserv-operator/blob/main/docs/HealthRules.md | `includeList` | `array (string)` @@ -3141,7 +3141,7 @@ Metrics enabled by default are: `workload_egress_bytes_total`, `namespace_drop_packets_total` (when `PacketDrop` feature is enabled), `namespace_rtt_seconds` (when `FlowRTT` feature is enabled), `namespace_dns_latency_seconds` (when `DNSTracking` feature is enabled), `namespace_network_policy_events_total` (when `NetworkEvents` feature is enabled). -More information, with full list of available metrics: https://github.com/netobserv/network-observability-operator/blob/main/docs/Metrics.md +More information, with full list of available metrics: https://github.com/netobserv/netobserv-operator/blob/main/docs/Metrics.md | `server` | `object` @@ -3154,7 +3154,7 @@ Description:: -- `healthRules` is a list of health rules to be created for Prometheus, organized by templates and variants. Each health rule can be configured to generate either alerts or recording rules based on the mode field. -More information on health rules: https://github.com/netobserv/network-observability-operator/blob/main/docs/HealthRules.md +More information on health rules: https://github.com/netobserv/netobserv-operator/blob/main/docs/HealthRules.md -- Type:: @@ -3197,7 +3197,7 @@ many new alerts burdensome. Possible values are: `PacketDropsByKernel`, `PacketDropsByDevice`, `IPsecErrors`, `NetpolDenied`, `LatencyHighTrend`, `DNSErrors`, `DNSNxDomain`, `ExternalEgressHighTrend`, `ExternalIngressHighTrend`, `Ingress5xxErrors`, `IngressHTTPLatencyTrend`. Note: `NetObservNoFlows` and `NetObservLokiError` are alert-only and cannot be used as health rules. -More information on health rules: https://github.com/netobserv/network-observability-operator/blob/main/docs/HealthRules.md +More information on health rules: https://github.com/netobserv/netobserv-operator/blob/main/docs/HealthRules.md | `variants` | `array` diff --git a/go.mod b/go.mod index 5d79f97fa2..9c7e68ce85 100644 --- a/go.mod +++ b/go.mod @@ -1,4 +1,4 @@ -module github.com/netobserv/network-observability-operator +module github.com/netobserv/netobserv-operator go 1.25.0 diff --git a/helm/Chart.yaml b/helm/Chart.yaml index f8e6f4ca16..5d4501e586 100644 --- a/helm/Chart.yaml +++ b/helm/Chart.yaml @@ -36,11 +36,11 @@ keywords: home: https://netobserv.io/ sources: -- https://github.com/netobserv/network-observability-operator +- https://github.com/netobserv/netobserv-operator - https://github.com/netobserv/flowlogs-pipeline - https://github.com/netobserv/netobserv-ebpf-agent -- https://github.com/netobserv/network-observability-console-plugin -- https://github.com/netobserv/network-observability-cli +- https://github.com/netobserv/netobserv-web-console +- https://github.com/netobserv/netobserv-cli maintainers: - email: jpinsonn@redhat.com diff --git a/helm/README.md b/helm/README.md index 0dbccd0d29..79f5ef07a6 100644 --- a/helm/README.md +++ b/helm/README.md @@ -56,7 +56,7 @@ helm install my-netobserv -n netobserv --create-namespace --set install.loki=tru helm install my-netobserv -n netobserv --create-namespace netobserv/netobserv-operator ``` -You can now create a `FlowCollector` resource ([full API reference](https://github.com/netobserv/network-observability-operator/blob/main/docs/FlowCollector.md#flowsnetobserviov1beta2)). A short `FlowCollector` should work, using most default values, plus with the standalone console enabled: +You can now create a `FlowCollector` resource ([full API reference](https://github.com/netobserv/netobserv-operator/blob/main/docs/FlowCollector.md#flowsnetobserviov1beta2)). A short `FlowCollector` should work, using most default values, plus with the standalone console enabled: ```bash cat <