apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T16:19:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-79-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-79.ec2.internal uid: 9312424d-56f1-4b6f-88dd-cb106c6f23e1 resourceVersion: "32550" uid: f0380bf0-02ae-4b82-8891-ca5b3498d4de spec: sourcePod: network-check-source-7cbc45fddc-z55rv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-18T16:26:58Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.067529ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T17:01:58Z" - latency: 1.276644ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T17:00:58Z" - latency: 1.300986ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:59:58Z" - latency: 1.50572ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:58:58Z" - latency: 1.040134ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:57:58Z" - latency: 1.195041ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:56:58Z" - latency: 1.095483ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:55:58Z" - latency: 1.051181ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:54:58Z" - latency: 970.706µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:53:58Z" - latency: 1.052001ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:52:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T16:19:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-79-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-79.ec2.internal uid: 9312424d-56f1-4b6f-88dd-cb106c6f23e1 resourceVersion: "32552" uid: f6b39400-9c19-4aa8-a830-5997975e84e7 spec: sourcePod: network-check-source-7cbc45fddc-z55rv targetEndpoint: ab205878015c242a6a9e68295ed09fac-f1214bb5be9beae9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-18T16:25:58Z" message: 'load-balancer-api-external: tcp connection to ab205878015c242a6a9e68295ed09fac-f1214bb5be9beae9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 14.40946ms message: 'load-balancer-api-external: tcp connection to ab205878015c242a6a9e68295ed09fac-f1214bb5be9beae9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T17:01:58Z" - latency: 9.737861ms message: 'load-balancer-api-external: resolved host name ab205878015c242a6a9e68295ed09fac-f1214bb5be9beae9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T17:01:58Z" - latency: 6.237687ms message: 'load-balancer-api-external: tcp connection to ab205878015c242a6a9e68295ed09fac-f1214bb5be9beae9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T17:00:58Z" - latency: 8.315861ms message: 'load-balancer-api-external: resolved host name ab205878015c242a6a9e68295ed09fac-f1214bb5be9beae9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T17:00:58Z" - latency: 5.602007ms message: 'load-balancer-api-external: tcp connection to ab205878015c242a6a9e68295ed09fac-f1214bb5be9beae9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:59:58Z" - latency: 8.442009ms message: 'load-balancer-api-external: resolved host name ab205878015c242a6a9e68295ed09fac-f1214bb5be9beae9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T16:59:58Z" - latency: 7.205345ms message: 'load-balancer-api-external: tcp connection to ab205878015c242a6a9e68295ed09fac-f1214bb5be9beae9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:58:58Z" - latency: 8.795795ms message: 'load-balancer-api-external: resolved host name ab205878015c242a6a9e68295ed09fac-f1214bb5be9beae9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T16:58:58Z" - latency: 6.019184ms message: 'load-balancer-api-external: tcp connection to ab205878015c242a6a9e68295ed09fac-f1214bb5be9beae9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:57:58Z" - latency: 9.462841ms message: 'load-balancer-api-external: resolved host name ab205878015c242a6a9e68295ed09fac-f1214bb5be9beae9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T16:57:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T16:19:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-79-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-79.ec2.internal uid: 9312424d-56f1-4b6f-88dd-cb106c6f23e1 resourceVersion: "32551" uid: 41c040e1-8df3-431b-888b-62686a3dbbe7 spec: sourcePod: network-check-source-7cbc45fddc-z55rv targetEndpoint: ab205878015c242a6a9e68295ed09fac-f1214bb5be9beae9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-18T16:25:58Z" message: 'load-balancer-api-internal: tcp connection to ab205878015c242a6a9e68295ed09fac-f1214bb5be9beae9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.571563ms message: 'load-balancer-api-internal: tcp connection to ab205878015c242a6a9e68295ed09fac-f1214bb5be9beae9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T17:01:58Z" - latency: 9.768037ms message: 'load-balancer-api-internal: resolved host name ab205878015c242a6a9e68295ed09fac-f1214bb5be9beae9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T17:01:58Z" - latency: 6.214904ms message: 'load-balancer-api-internal: tcp connection to ab205878015c242a6a9e68295ed09fac-f1214bb5be9beae9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T17:00:58Z" - latency: 8.360744ms message: 'load-balancer-api-internal: resolved host name ab205878015c242a6a9e68295ed09fac-f1214bb5be9beae9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T17:00:58Z" - latency: 5.565919ms message: 'load-balancer-api-internal: tcp connection to ab205878015c242a6a9e68295ed09fac-f1214bb5be9beae9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:59:58Z" - latency: 8.512979ms message: 'load-balancer-api-internal: resolved host name ab205878015c242a6a9e68295ed09fac-f1214bb5be9beae9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T16:59:58Z" - latency: 6.877542ms message: 'load-balancer-api-internal: tcp connection to ab205878015c242a6a9e68295ed09fac-f1214bb5be9beae9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:58:58Z" - latency: 8.811811ms message: 'load-balancer-api-internal: resolved host name ab205878015c242a6a9e68295ed09fac-f1214bb5be9beae9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T16:58:58Z" - latency: 7.598075ms message: 'load-balancer-api-internal: tcp connection to ab205878015c242a6a9e68295ed09fac-f1214bb5be9beae9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:57:58Z" - latency: 9.53892ms message: 'load-balancer-api-internal: resolved host name ab205878015c242a6a9e68295ed09fac-f1214bb5be9beae9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T16:57:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T16:19:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-79-to-network-check-target-ip-10-0-128-224 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-79.ec2.internal uid: 9312424d-56f1-4b6f-88dd-cb106c6f23e1 resourceVersion: "32547" uid: e6d3ff76-39ec-4741-aff1-005bd1fe3ab1 spec: sourcePod: network-check-source-7cbc45fddc-z55rv targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-18T16:26:58Z" message: 'network-check-target-ip-10-0-128-224: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.285147ms message: 'network-check-target-ip-10-0-128-224: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T17:01:58Z" - latency: 2.184029ms message: 'network-check-target-ip-10-0-128-224: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T17:00:58Z" - latency: 2.370351ms message: 'network-check-target-ip-10-0-128-224: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:59:58Z" - latency: 2.307582ms message: 'network-check-target-ip-10-0-128-224: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:58:58Z" - latency: 2.236419ms message: 'network-check-target-ip-10-0-128-224: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:57:58Z" - latency: 2.314236ms message: 'network-check-target-ip-10-0-128-224: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:56:58Z" - latency: 1.972093ms message: 'network-check-target-ip-10-0-128-224: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:55:58Z" - latency: 2.17816ms message: 'network-check-target-ip-10-0-128-224: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:54:58Z" - latency: 2.386096ms message: 'network-check-target-ip-10-0-128-224: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:53:58Z" - latency: 2.35301ms message: 'network-check-target-ip-10-0-128-224: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:52:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T16:19:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-79-to-network-check-target-ip-10-0-135-110 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-79.ec2.internal uid: 9312424d-56f1-4b6f-88dd-cb106c6f23e1 resourceVersion: "32548" uid: 70372252-3fa2-457b-b18c-dc9deb2469ac spec: sourcePod: network-check-source-7cbc45fddc-z55rv targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-18T16:26:58Z" message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.033906ms message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T17:01:58Z" - latency: 1.755852ms message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T17:00:58Z" - latency: 1.96572ms message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:59:58Z" - latency: 1.880296ms message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:58:58Z" - latency: 2.059956ms message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:57:58Z" - latency: 1.682883ms message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:56:58Z" - latency: 1.952322ms message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:55:58Z" - latency: 2.076767ms message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:54:58Z" - latency: 2.091158ms message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:53:58Z" - latency: 2.187365ms message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:52:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T16:19:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-79-to-network-check-target-ip-10-0-143-79 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-79.ec2.internal uid: 9312424d-56f1-4b6f-88dd-cb106c6f23e1 resourceVersion: "32546" uid: ad8d311c-9cae-4c8f-89be-40c431a7ded4 spec: sourcePod: network-check-source-7cbc45fddc-z55rv targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-18T16:26:58Z" message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 896.557µs message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T17:01:58Z" - latency: 1.321184ms message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T17:00:58Z" - latency: 926.417µs message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:59:58Z" - latency: 1.605079ms message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:58:58Z" - latency: 880.794µs message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:57:58Z" - latency: 1.358721ms message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:56:58Z" - latency: 788.109µs message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:55:58Z" - latency: 1.172794ms message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:54:58Z" - latency: 1.525052ms message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:53:58Z" - latency: 1.49531ms message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:52:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T16:19:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-79-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-79.ec2.internal uid: 9312424d-56f1-4b6f-88dd-cb106c6f23e1 resourceVersion: "32549" uid: ca29439b-3e1d-498b-8d9d-87c8bc27f921 spec: sourcePod: network-check-source-7cbc45fddc-z55rv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-18T16:25:58Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 813.379µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T17:01:58Z" - latency: 2.04849ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T17:01:58Z" - latency: 878.838µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T17:00:58Z" - latency: 1.846832ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T17:00:58Z" - latency: 5.745172ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:59:58Z" - latency: 1.941838ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T16:59:58Z" - latency: 1.010375ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:58:58Z" - latency: 2.17112ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T16:58:58Z" - latency: 1.144877ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:57:58Z" - latency: 2.084855ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T16:57:58Z" kind: List metadata: resourceVersion: ""