apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T13:13:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-224-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-224.ec2.internal uid: c87917d8-e96b-4331-a26e-e63326a0ff4d resourceVersion: "62613" uid: 693f45a5-7a67-4d1a-bb32-e25094b92e2c spec: sourcePod: network-check-source-869dcfcdcd-knnp9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-15T13:20:05Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 919.581µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:55:05Z" - latency: 1.110999ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:54:05Z" - latency: 1.390887ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:53:05Z" - latency: 1.199332ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:52:05Z" - latency: 1.421799ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:51:05Z" - latency: 923.065µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:50:05Z" - latency: 1.263863ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:49:05Z" - latency: 1.094738ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:48:05Z" - latency: 1.552963ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:47:05Z" - latency: 909.08µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:46:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T13:13:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-224-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-224.ec2.internal uid: c87917d8-e96b-4331-a26e-e63326a0ff4d resourceVersion: "62615" uid: be88636e-c1d7-4418-94e5-6aa455d68a63 spec: sourcePod: network-check-source-869dcfcdcd-knnp9 targetEndpoint: a50b9ed0e66f24de080dbc11df32ab36-4b565e74ade598ae.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T13:19:05Z" message: 'load-balancer-api-external: tcp connection to a50b9ed0e66f24de080dbc11df32ab36-4b565e74ade598ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.632147ms message: 'load-balancer-api-external: tcp connection to a50b9ed0e66f24de080dbc11df32ab36-4b565e74ade598ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:55:05Z" - latency: 8.270239ms message: 'load-balancer-api-external: resolved host name a50b9ed0e66f24de080dbc11df32ab36-4b565e74ade598ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T13:55:05Z" - latency: 5.540887ms message: 'load-balancer-api-external: tcp connection to a50b9ed0e66f24de080dbc11df32ab36-4b565e74ade598ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:54:05Z" - latency: 7.560107ms message: 'load-balancer-api-external: resolved host name a50b9ed0e66f24de080dbc11df32ab36-4b565e74ade598ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T13:54:05Z" - latency: 4.490788ms message: 'load-balancer-api-external: tcp connection to a50b9ed0e66f24de080dbc11df32ab36-4b565e74ade598ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:53:05Z" - latency: 7.467998ms message: 'load-balancer-api-external: resolved host name a50b9ed0e66f24de080dbc11df32ab36-4b565e74ade598ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T13:53:05Z" - latency: 4.960226ms message: 'load-balancer-api-external: tcp connection to a50b9ed0e66f24de080dbc11df32ab36-4b565e74ade598ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:52:05Z" - latency: 8.370785ms message: 'load-balancer-api-external: resolved host name a50b9ed0e66f24de080dbc11df32ab36-4b565e74ade598ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T13:52:05Z" - latency: 5.539339ms message: 'load-balancer-api-external: tcp connection to a50b9ed0e66f24de080dbc11df32ab36-4b565e74ade598ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:51:05Z" - latency: 10.213196ms message: 'load-balancer-api-external: resolved host name a50b9ed0e66f24de080dbc11df32ab36-4b565e74ade598ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T13:51:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T13:13:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-224-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-224.ec2.internal uid: c87917d8-e96b-4331-a26e-e63326a0ff4d resourceVersion: "62614" uid: 7230d7f7-9e63-445e-908a-76136d6fbf00 spec: sourcePod: network-check-source-869dcfcdcd-knnp9 targetEndpoint: a50b9ed0e66f24de080dbc11df32ab36-4b565e74ade598ae.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T13:19:05Z" message: 'load-balancer-api-internal: tcp connection to a50b9ed0e66f24de080dbc11df32ab36-4b565e74ade598ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.867424ms message: 'load-balancer-api-internal: tcp connection to a50b9ed0e66f24de080dbc11df32ab36-4b565e74ade598ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:55:05Z" - latency: 8.313505ms message: 'load-balancer-api-internal: resolved host name a50b9ed0e66f24de080dbc11df32ab36-4b565e74ade598ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T13:55:05Z" - latency: 5.463675ms message: 'load-balancer-api-internal: tcp connection to a50b9ed0e66f24de080dbc11df32ab36-4b565e74ade598ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:54:05Z" - latency: 7.578484ms message: 'load-balancer-api-internal: resolved host name a50b9ed0e66f24de080dbc11df32ab36-4b565e74ade598ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T13:54:05Z" - latency: 4.474434ms message: 'load-balancer-api-internal: tcp connection to a50b9ed0e66f24de080dbc11df32ab36-4b565e74ade598ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:53:05Z" - latency: 7.437028ms message: 'load-balancer-api-internal: resolved host name a50b9ed0e66f24de080dbc11df32ab36-4b565e74ade598ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T13:53:05Z" - latency: 4.936963ms message: 'load-balancer-api-internal: tcp connection to a50b9ed0e66f24de080dbc11df32ab36-4b565e74ade598ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:52:05Z" - latency: 8.443553ms message: 'load-balancer-api-internal: resolved host name a50b9ed0e66f24de080dbc11df32ab36-4b565e74ade598ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T13:52:05Z" - latency: 5.576977ms message: 'load-balancer-api-internal: tcp connection to a50b9ed0e66f24de080dbc11df32ab36-4b565e74ade598ae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:51:05Z" - latency: 10.192218ms message: 'load-balancer-api-internal: resolved host name a50b9ed0e66f24de080dbc11df32ab36-4b565e74ade598ae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T13:51:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T13:13:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-224-to-network-check-target-ip-10-0-131-140 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-224.ec2.internal uid: c87917d8-e96b-4331-a26e-e63326a0ff4d resourceVersion: "62610" uid: 6076a4a4-a3c2-4839-bd28-ca6a2fc07ba4 spec: sourcePod: network-check-source-869dcfcdcd-knnp9 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T13:20:05Z" message: 'network-check-target-ip-10-0-131-140: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.030445ms message: 'network-check-target-ip-10-0-131-140: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:55:05Z" - latency: 2.160304ms message: 'network-check-target-ip-10-0-131-140: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:54:05Z" - latency: 2.165741ms message: 'network-check-target-ip-10-0-131-140: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:53:05Z" - latency: 2.502571ms message: 'network-check-target-ip-10-0-131-140: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:52:05Z" - latency: 2.069522ms message: 'network-check-target-ip-10-0-131-140: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:51:05Z" - latency: 1.756872ms message: 'network-check-target-ip-10-0-131-140: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:50:05Z" - latency: 2.318204ms message: 'network-check-target-ip-10-0-131-140: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:49:05Z" - latency: 2.328222ms message: 'network-check-target-ip-10-0-131-140: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:48:05Z" - latency: 2.18909ms message: 'network-check-target-ip-10-0-131-140: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:47:05Z" - latency: 2.165773ms message: 'network-check-target-ip-10-0-131-140: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:46:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T13:13:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-224-to-network-check-target-ip-10-0-139-149 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-224.ec2.internal uid: c87917d8-e96b-4331-a26e-e63326a0ff4d resourceVersion: "62609" uid: 788d7d30-fab4-48c3-8960-f30c8e4d612f spec: sourcePod: network-check-source-869dcfcdcd-knnp9 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-15T13:20:05Z" message: 'network-check-target-ip-10-0-139-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.83493ms message: 'network-check-target-ip-10-0-139-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:55:05Z" - latency: 1.614329ms message: 'network-check-target-ip-10-0-139-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:54:05Z" - latency: 1.994476ms message: 'network-check-target-ip-10-0-139-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:53:05Z" - latency: 2.279735ms message: 'network-check-target-ip-10-0-139-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:52:05Z" - latency: 2.275087ms message: 'network-check-target-ip-10-0-139-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:51:05Z" - latency: 2.183432ms message: 'network-check-target-ip-10-0-139-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:50:05Z" - latency: 1.954101ms message: 'network-check-target-ip-10-0-139-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:49:05Z" - latency: 2.603854ms message: 'network-check-target-ip-10-0-139-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:48:05Z" - latency: 1.983991ms message: 'network-check-target-ip-10-0-139-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:47:05Z" - latency: 1.719511ms message: 'network-check-target-ip-10-0-139-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:46:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T13:13:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-224-to-network-check-target-ip-10-0-143-224 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-224.ec2.internal uid: c87917d8-e96b-4331-a26e-e63326a0ff4d resourceVersion: "62608" uid: 4390aff4-25b3-4367-8c39-497d5c85e558 spec: sourcePod: network-check-source-869dcfcdcd-knnp9 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-15T13:20:05Z" message: 'network-check-target-ip-10-0-143-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 814.613µs message: 'network-check-target-ip-10-0-143-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:55:05Z" - latency: 878.769µs message: 'network-check-target-ip-10-0-143-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:54:05Z" - latency: 830.839µs message: 'network-check-target-ip-10-0-143-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:53:05Z" - latency: 1.034813ms message: 'network-check-target-ip-10-0-143-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:52:05Z" - latency: 794.402µs message: 'network-check-target-ip-10-0-143-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:51:05Z" - latency: 859.377µs message: 'network-check-target-ip-10-0-143-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:50:05Z" - latency: 871.964µs message: 'network-check-target-ip-10-0-143-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:49:05Z" - latency: 1.43418ms message: 'network-check-target-ip-10-0-143-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:48:05Z" - latency: 1.405799ms message: 'network-check-target-ip-10-0-143-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:47:05Z" - latency: 1.053095ms message: 'network-check-target-ip-10-0-143-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:46:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T13:13:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-224-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-224.ec2.internal uid: c87917d8-e96b-4331-a26e-e63326a0ff4d resourceVersion: "62611" uid: 864c023d-b4d2-4479-bdee-2547a2a08df9 spec: sourcePod: network-check-source-869dcfcdcd-knnp9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-15T13:19:05Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 939.472µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:55:05Z" - latency: 1.788381ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T13:55:05Z" - latency: 886.497µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:54:05Z" - latency: 1.873674ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T13:54:05Z" - latency: 832.029µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:53:05Z" - latency: 2.180901ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T13:53:05Z" - latency: 779.644µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:52:05Z" - latency: 1.936792ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T13:52:05Z" - latency: 978.448µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:51:05Z" - latency: 1.875327ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T13:51:05Z" kind: List metadata: resourceVersion: ""