apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T06:20:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-215-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-215.ec2.internal uid: c17a9873-b9d1-4d2f-b3aa-a420d389cbc7 resourceVersion: "55441" uid: 66671d5f-4472-43bb-b438-8b40f7e4339b spec: sourcePod: network-check-source-7bc5b6bf85-pg5gq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-21T06:27:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 909.449µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:55:59Z" - latency: 1.0909ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:54:59Z" - latency: 1.148486ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:53:59Z" - latency: 1.064659ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:52:59Z" - latency: 1.039056ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:51:59Z" - latency: 1.141514ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:50:59Z" - latency: 1.214085ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:49:59Z" - latency: 1.050836ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:48:59Z" - latency: 956.072µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:47:59Z" - latency: 904.551µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:46:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T06:20:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-215-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-215.ec2.internal uid: c17a9873-b9d1-4d2f-b3aa-a420d389cbc7 resourceVersion: "56544" uid: ec55d6b0-386f-4ec1-ad30-04d96fb89e86 spec: sourcePod: network-check-source-7bc5b6bf85-pg5gq targetEndpoint: af55510b724494f2e8118d679c3017f3-e30376f527ca993e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T06:26:59Z" message: 'load-balancer-api-external: tcp connection to af55510b724494f2e8118d679c3017f3-e30376f527ca993e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.939412ms message: 'load-balancer-api-external: tcp connection to af55510b724494f2e8118d679c3017f3-e30376f527ca993e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:56:59Z" - latency: 8.642747ms message: 'load-balancer-api-external: resolved host name af55510b724494f2e8118d679c3017f3-e30376f527ca993e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T06:56:59Z" - latency: 3.380684ms message: 'load-balancer-api-external: tcp connection to af55510b724494f2e8118d679c3017f3-e30376f527ca993e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:55:59Z" - latency: 6.880558ms message: 'load-balancer-api-external: resolved host name af55510b724494f2e8118d679c3017f3-e30376f527ca993e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T06:55:59Z" - latency: 4.105603ms message: 'load-balancer-api-external: tcp connection to af55510b724494f2e8118d679c3017f3-e30376f527ca993e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:54:59Z" - latency: 14.027832ms message: 'load-balancer-api-external: resolved host name af55510b724494f2e8118d679c3017f3-e30376f527ca993e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T06:54:59Z" - latency: 5.248042ms message: 'load-balancer-api-external: tcp connection to af55510b724494f2e8118d679c3017f3-e30376f527ca993e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:53:59Z" - latency: 9.132015ms message: 'load-balancer-api-external: resolved host name af55510b724494f2e8118d679c3017f3-e30376f527ca993e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T06:53:59Z" - latency: 4.157405ms message: 'load-balancer-api-external: tcp connection to af55510b724494f2e8118d679c3017f3-e30376f527ca993e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:52:59Z" - latency: 7.278601ms message: 'load-balancer-api-external: resolved host name af55510b724494f2e8118d679c3017f3-e30376f527ca993e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T06:52:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T06:20:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-215-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-215.ec2.internal uid: c17a9873-b9d1-4d2f-b3aa-a420d389cbc7 resourceVersion: "56545" uid: 514384f5-b469-49b0-9ff2-0c58613be866 spec: sourcePod: network-check-source-7bc5b6bf85-pg5gq targetEndpoint: af55510b724494f2e8118d679c3017f3-e30376f527ca993e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T06:26:59Z" message: 'load-balancer-api-internal: tcp connection to af55510b724494f2e8118d679c3017f3-e30376f527ca993e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.491319ms message: 'load-balancer-api-internal: tcp connection to af55510b724494f2e8118d679c3017f3-e30376f527ca993e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:56:59Z" - latency: 8.619084ms message: 'load-balancer-api-internal: resolved host name af55510b724494f2e8118d679c3017f3-e30376f527ca993e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T06:56:59Z" - latency: 3.690701ms message: 'load-balancer-api-internal: tcp connection to af55510b724494f2e8118d679c3017f3-e30376f527ca993e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:55:59Z" - latency: 6.839156ms message: 'load-balancer-api-internal: resolved host name af55510b724494f2e8118d679c3017f3-e30376f527ca993e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T06:55:59Z" - latency: 4.147879ms message: 'load-balancer-api-internal: tcp connection to af55510b724494f2e8118d679c3017f3-e30376f527ca993e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:54:59Z" - latency: 14.008093ms message: 'load-balancer-api-internal: resolved host name af55510b724494f2e8118d679c3017f3-e30376f527ca993e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T06:54:59Z" - latency: 5.254255ms message: 'load-balancer-api-internal: tcp connection to af55510b724494f2e8118d679c3017f3-e30376f527ca993e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:53:59Z" - latency: 9.09411ms message: 'load-balancer-api-internal: resolved host name af55510b724494f2e8118d679c3017f3-e30376f527ca993e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T06:53:59Z" - latency: 4.16731ms message: 'load-balancer-api-internal: tcp connection to af55510b724494f2e8118d679c3017f3-e30376f527ca993e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:52:59Z" - latency: 7.251756ms message: 'load-balancer-api-internal: resolved host name af55510b724494f2e8118d679c3017f3-e30376f527ca993e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T06:52:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T06:20:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-215-to-network-check-target-ip-10-0-128-56 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-215.ec2.internal uid: c17a9873-b9d1-4d2f-b3aa-a420d389cbc7 resourceVersion: "55439" uid: 0944a20a-8925-477b-8ae7-87ed1583baf4 spec: sourcePod: network-check-source-7bc5b6bf85-pg5gq targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T06:27:59Z" message: 'network-check-target-ip-10-0-128-56: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.80952ms message: 'network-check-target-ip-10-0-128-56: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:55:59Z" - latency: 1.918003ms message: 'network-check-target-ip-10-0-128-56: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:54:59Z" - latency: 1.975272ms message: 'network-check-target-ip-10-0-128-56: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:53:59Z" - latency: 1.937584ms message: 'network-check-target-ip-10-0-128-56: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:52:59Z" - latency: 1.9441ms message: 'network-check-target-ip-10-0-128-56: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:51:59Z" - latency: 1.876957ms message: 'network-check-target-ip-10-0-128-56: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:50:59Z" - latency: 1.810017ms message: 'network-check-target-ip-10-0-128-56: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:49:59Z" - latency: 1.828457ms message: 'network-check-target-ip-10-0-128-56: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:48:59Z" - latency: 1.745936ms message: 'network-check-target-ip-10-0-128-56: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:47:59Z" - latency: 2.161283ms message: 'network-check-target-ip-10-0-128-56: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:46:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T06:20:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-215-to-network-check-target-ip-10-0-136-215 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-215.ec2.internal uid: c17a9873-b9d1-4d2f-b3aa-a420d389cbc7 resourceVersion: "55438" uid: 953f2a16-2ac8-4c0f-a1fd-e06c65c12b80 spec: sourcePod: network-check-source-7bc5b6bf85-pg5gq targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-21T06:27:59Z" message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 827.511µs message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:55:59Z" - latency: 1.037117ms message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:54:59Z" - latency: 894.929µs message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:53:59Z" - latency: 884.541µs message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:52:59Z" - latency: 702.317µs message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:51:59Z" - latency: 1.041438ms message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:50:59Z" - latency: 1.004799ms message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:49:59Z" - latency: 829.075µs message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:48:59Z" - latency: 1.068333ms message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:47:59Z" - latency: 832.815µs message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:46:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T06:20:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-215-to-network-check-target-ip-10-0-140-159 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-215.ec2.internal uid: c17a9873-b9d1-4d2f-b3aa-a420d389cbc7 resourceVersion: "55440" uid: 2b692785-6cab-4a4b-9049-97ef52dfef65 spec: sourcePod: network-check-source-7bc5b6bf85-pg5gq targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T06:27:59Z" message: 'network-check-target-ip-10-0-140-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.22029ms message: 'network-check-target-ip-10-0-140-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:55:59Z" - latency: 2.328814ms message: 'network-check-target-ip-10-0-140-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:54:59Z" - latency: 2.416814ms message: 'network-check-target-ip-10-0-140-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:53:59Z" - latency: 2.259544ms message: 'network-check-target-ip-10-0-140-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:52:59Z" - latency: 2.171992ms message: 'network-check-target-ip-10-0-140-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:51:59Z" - latency: 1.851323ms message: 'network-check-target-ip-10-0-140-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:50:59Z" - latency: 2.026232ms message: 'network-check-target-ip-10-0-140-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:49:59Z" - latency: 2.588971ms message: 'network-check-target-ip-10-0-140-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:48:59Z" - latency: 2.00985ms message: 'network-check-target-ip-10-0-140-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:47:59Z" - latency: 2.263239ms message: 'network-check-target-ip-10-0-140-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:46:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T06:20:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-215-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-215.ec2.internal uid: c17a9873-b9d1-4d2f-b3aa-a420d389cbc7 resourceVersion: "56543" uid: 05d92480-8883-4863-94da-07bb5a89fc71 spec: sourcePod: network-check-source-7bc5b6bf85-pg5gq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-21T06:26:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.037924ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:56:59Z" - latency: 2.291273ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T06:56:59Z" - latency: 1.103591ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:55:59Z" - latency: 2.088996ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T06:55:59Z" - latency: 831.636µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:54:59Z" - latency: 2.556869ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T06:54:59Z" - latency: 1.166717ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:53:59Z" - latency: 1.852247ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T06:53:59Z" - latency: 978.964µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T06:52:59Z" - latency: 1.83206ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T06:52:59Z" kind: List metadata: resourceVersion: ""