From 4bb4a3bf952ae72b120132fa99c4d747b52dbcf8 Mon Sep 17 00:00:00 2001 From: Servesha Dudhgaonkar Date: Fri, 4 Mar 2022 08:44:40 +0530 Subject: [PATCH] Remove endpointPublishingStrategy --- modules/nw-configure-ingress-access-logging.adoc | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/modules/nw-configure-ingress-access-logging.adoc b/modules/nw-configure-ingress-access-logging.adoc index 9f4cb49aac..bbc1fb8995 100644 --- a/modules/nw-configure-ingress-access-logging.adoc +++ b/modules/nw-configure-ingress-access-logging.adoc @@ -31,15 +31,12 @@ metadata: namespace: openshift-ingress-operator spec: replicas: 2 - endpointPublishingStrategy: - type: NodePortService <1> logging: access: destination: type: Container ---- -<1> `NodePortService` is not required to configure Ingress access logging to a sidecar. Ingress logging is compatible with any `endpointPublishingStrategy`. -+ + * When you configure the Ingress Controller to log to a sidecar, the operator creates a container named `logs` inside the Ingress Controller Pod: + [source,terminal] @@ -66,8 +63,6 @@ metadata: namespace: openshift-ingress-operator spec: replicas: 2 - endpointPublishingStrategy: - type: NodePortService logging: access: destination: @@ -95,8 +90,6 @@ metadata: namespace: openshift-ingress-operator spec: replicas: 2 - endpointPublishingStrategy: - type: NodePortService logging: access: destination: @@ -120,8 +113,6 @@ metadata: namespace: openshift-ingress-operator spec: replicas: 2 - endpointPublishingStrategy: - type: NodePortService logging: access: null ----