breaking(node-agent): remove node-agent

Signed-off-by: Bence Csati <[email protected]>

Author: csatib02

charts/logging-operator/README.md

@@ -91,7 +91,6 @@ Use `createCustomResource=false` with Helm v3 to avoid trying to create CRDs fro
 | logging.clusterDomain | string | `"cluster.local."` | Cluster domain name to be used when templating URLs to services |
 | logging.controlNamespace | string | `""` | Namespace for cluster wide configuration resources like ClusterFlow and ClusterOutput. This should be a protected namespace from regular users. Resources like fluentbit and fluentd will run in this namespace as well. |
 | logging.allowClusterResourcesFromAllNamespaces | bool | `false` | Allow configuration of cluster resources from any namespace. Mutually exclusive with ControlNamespace restriction of Cluster resources |
-| logging.nodeAgents | list | `[]` | NodeAgent Configuration DEPRECATED: This field will be removed in a future release. |
 | logging.configCheck | object | `{}` | configCheck provides possibility for timeout-based configuration checks https://kube-logging.dev/docs/whats-new/#timeout-based-configuration-checks |
 | logging.enableRecreateWorkloadOnImmutableFieldChange | bool | `false` | EnableRecreateWorkloadOnImmutableFieldChange enables the operator to recreate the fluentbit daemonset and the fluentd statefulset (and possibly other resource in the future) in case there is a change in an immutable field that otherwise couldn’t be managed with a simple update. |
 | logging.enableDockerParserCompatibilityForCRI | bool | `false` | EnableDockerParserCompatibilityForCRI enables Docker log format compatibility for CRI workloads. |

charts/logging-operator/charts/logging-operator-crds/templates/logging.banzaicloud.io_loggings.yaml

@@ -164,7 +164,6 @@ rules:
   - fluentdconfigs
   - loggingroutes
   - loggings
-  - nodeagents
   - outputs
   - syslogngclusterflows
   - syslogngclusteroutputs
@@ -190,7 +189,6 @@ rules:
   - fluentdconfigs/status
   - loggingroutes/status
   - loggings/status
-  - nodeagents/status
   - outputs/status
   - syslogngclusterflows/status
   - syslogngclusteroutputs/status

charts/logging-operator/charts/logging-operator-crds/templates/logging.banzaicloud.io_nodeagents.yaml

@@ -48,9 +48,6 @@ spec:
   {{- with .Values.logging.allowClusterResourcesFromAllNamespaces }}
   allowClusterResourcesFromAllNamespaces: {{ . }}
   {{- end }}
-  {{- with .Values.logging.nodeAgents }}
-  nodeAgents: {{- toYaml . | nindent 4 }}
-  {{- end }}
   {{- with .Values.logging.enableRecreateWorkloadOnImmutableFieldChange }}
   enableRecreateWorkloadOnImmutableFieldChange: {{ . }}
   {{- end }}

charts/logging-operator/crds/logging.banzaicloud.io_loggings.yaml

@@ -206,30 +206,6 @@ logging:
   # -- Allow configuration of cluster resources from any namespace. Mutually exclusive with ControlNamespace restriction of Cluster resources
   allowClusterResourcesFromAllNamespaces: false
 
-  # -- NodeAgent Configuration
-  # DEPRECATED: This field will be removed in a future release.
-  nodeAgents: []
-  #  - name: win-agent
-  #    profile: windows
-  #    nodeAgentFluentbit:
-  #      daemonSet:
-  #        spec:
-  #          template:
-  #            spec:
-  #              containers:
-  #              - image: banzaicloud/fluentbit:1.9.5
-  #                name: fluent-bit
-  #      tls:
-  #        enabled: false
-  #  - name: linux-agent
-  #    profile: linux
-  #    nodeAgentFluentbit:
-  #      metrics:
-  #        prometheusAnnotations: true
-  #        serviceMonitor: false
-  #      tls:
-  #        enabled: false
-
   # -- configCheck provides possibility for timeout-based configuration checks https://kube-logging.dev/docs/whats-new/#timeout-based-configuration-checks
   configCheck: {}