apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T14:44:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-134-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-134.ec2.internal uid: 450355ff-e180-483e-96ce-1c2f58933fe5 resourceVersion: "31361" uid: 0be54512-1a87-42d0-b6bc-36f6496d9c54 spec: sourcePod: network-check-source-dbd9cf844-qjmpc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-09T14:51:32Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.010445ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:58:32Z" - latency: 1.170715ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:57:32Z" - latency: 879.561µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:56:32Z" - latency: 935.185µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:55:32Z" - latency: 989.438µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:54:32Z" - latency: 1.445979ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:53:32Z" - latency: 945.842µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:52:32Z" - latency: 1.407849ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:51:32Z" - latency: 1.082755ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:50:32Z" - latency: 1.67643ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:49:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T14:44:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-134-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-134.ec2.internal uid: 450355ff-e180-483e-96ce-1c2f58933fe5 resourceVersion: "35271" uid: 0385456f-26d6-4064-83af-49e6949fb08c spec: sourcePod: network-check-source-dbd9cf844-qjmpc targetEndpoint: abab9aaafa4924df786f00cbe1060e16-5f75df3d657d4918.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T14:50:32Z" message: 'load-balancer-api-external: tcp connection to abab9aaafa4924df786f00cbe1060e16-5f75df3d657d4918.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.0412ms message: 'load-balancer-api-external: tcp connection to abab9aaafa4924df786f00cbe1060e16-5f75df3d657d4918.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:02:32Z" - latency: 8.269943ms message: 'load-balancer-api-external: resolved host name abab9aaafa4924df786f00cbe1060e16-5f75df3d657d4918.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:02:32Z" - latency: 5.735317ms message: 'load-balancer-api-external: tcp connection to abab9aaafa4924df786f00cbe1060e16-5f75df3d657d4918.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:01:32Z" - latency: 9.331759ms message: 'load-balancer-api-external: resolved host name abab9aaafa4924df786f00cbe1060e16-5f75df3d657d4918.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:01:32Z" - latency: 5.89601ms message: 'load-balancer-api-external: tcp connection to abab9aaafa4924df786f00cbe1060e16-5f75df3d657d4918.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:00:32Z" - latency: 7.884454ms message: 'load-balancer-api-external: resolved host name abab9aaafa4924df786f00cbe1060e16-5f75df3d657d4918.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:00:32Z" - latency: 4.673148ms message: 'load-balancer-api-external: tcp connection to abab9aaafa4924df786f00cbe1060e16-5f75df3d657d4918.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:59:32Z" - latency: 6.934593ms message: 'load-balancer-api-external: resolved host name abab9aaafa4924df786f00cbe1060e16-5f75df3d657d4918.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T14:59:32Z" - latency: 4.895931ms message: 'load-balancer-api-external: tcp connection to abab9aaafa4924df786f00cbe1060e16-5f75df3d657d4918.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:58:32Z" - latency: 8.460899ms message: 'load-balancer-api-external: resolved host name abab9aaafa4924df786f00cbe1060e16-5f75df3d657d4918.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T14:58:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T14:44:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-134-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-134.ec2.internal uid: 450355ff-e180-483e-96ce-1c2f58933fe5 resourceVersion: "35270" uid: c3706227-5e5a-4b5c-8c0b-ba6ac08e8b6d spec: sourcePod: network-check-source-dbd9cf844-qjmpc targetEndpoint: abab9aaafa4924df786f00cbe1060e16-5f75df3d657d4918.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T14:50:32Z" message: 'load-balancer-api-internal: tcp connection to abab9aaafa4924df786f00cbe1060e16-5f75df3d657d4918.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.357272ms message: 'load-balancer-api-internal: tcp connection to abab9aaafa4924df786f00cbe1060e16-5f75df3d657d4918.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:02:32Z" - latency: 8.206105ms message: 'load-balancer-api-internal: resolved host name abab9aaafa4924df786f00cbe1060e16-5f75df3d657d4918.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:02:32Z" - latency: 5.764185ms message: 'load-balancer-api-internal: tcp connection to abab9aaafa4924df786f00cbe1060e16-5f75df3d657d4918.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:01:32Z" - latency: 9.23528ms message: 'load-balancer-api-internal: resolved host name abab9aaafa4924df786f00cbe1060e16-5f75df3d657d4918.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:01:32Z" - latency: 5.831759ms message: 'load-balancer-api-internal: tcp connection to abab9aaafa4924df786f00cbe1060e16-5f75df3d657d4918.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:00:32Z" - latency: 7.978351ms message: 'load-balancer-api-internal: resolved host name abab9aaafa4924df786f00cbe1060e16-5f75df3d657d4918.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:00:32Z" - latency: 4.754664ms message: 'load-balancer-api-internal: tcp connection to abab9aaafa4924df786f00cbe1060e16-5f75df3d657d4918.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:59:32Z" - latency: 7.014095ms message: 'load-balancer-api-internal: resolved host name abab9aaafa4924df786f00cbe1060e16-5f75df3d657d4918.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T14:59:32Z" - latency: 14.38666ms message: 'load-balancer-api-internal: tcp connection to abab9aaafa4924df786f00cbe1060e16-5f75df3d657d4918.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:58:32Z" - latency: 8.39416ms message: 'load-balancer-api-internal: resolved host name abab9aaafa4924df786f00cbe1060e16-5f75df3d657d4918.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T14:58:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T14:44:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-134-to-network-check-target-ip-10-0-137-134 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-134.ec2.internal uid: 450355ff-e180-483e-96ce-1c2f58933fe5 resourceVersion: "31358" uid: 0e45b1da-e19b-48b5-b786-392a99c98a1d spec: sourcePod: network-check-source-dbd9cf844-qjmpc targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T14:51:32Z" message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.383443ms message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:58:32Z" - latency: 2.34693ms message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:57:32Z" - latency: 2.263995ms message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:56:32Z" - latency: 2.366594ms message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:55:32Z" - latency: 2.224526ms message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:54:32Z" - latency: 2.548353ms message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:53:32Z" - latency: 2.150286ms message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:52:32Z" - latency: 2.70225ms message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:51:32Z" - latency: 2.582721ms message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:50:32Z" - latency: 2.511824ms message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:49:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T14:44:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-134-to-network-check-target-ip-10-0-143-134 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-134.ec2.internal uid: 450355ff-e180-483e-96ce-1c2f58933fe5 resourceVersion: "31357" uid: 1185f8ce-453a-4b2f-8982-257f03fc32d7 spec: sourcePod: network-check-source-dbd9cf844-qjmpc targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T14:51:32Z" message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.437223ms message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:58:32Z" - latency: 848.859µs message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:57:32Z" - latency: 1.342299ms message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:56:32Z" - latency: 838.059µs message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:55:32Z" - latency: 889.921µs message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:54:32Z" - latency: 1.071344ms message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:53:32Z" - latency: 762.268µs message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:52:32Z" - latency: 1.222527ms message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:51:32Z" - latency: 824.199µs message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:50:32Z" - latency: 905.349µs message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:49:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T14:44:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-134-to-network-check-target-ip-10-0-143-219 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-134.ec2.internal uid: 450355ff-e180-483e-96ce-1c2f58933fe5 resourceVersion: "31359" uid: 29ca2a5f-210d-4f4d-88c3-0f1bbfe555a4 spec: sourcePod: network-check-source-dbd9cf844-qjmpc targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T14:51:32Z" message: 'network-check-target-ip-10-0-143-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.274245ms message: 'network-check-target-ip-10-0-143-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:58:32Z" - latency: 2.23635ms message: 'network-check-target-ip-10-0-143-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:57:32Z" - latency: 2.360886ms message: 'network-check-target-ip-10-0-143-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:56:32Z" - latency: 2.238331ms message: 'network-check-target-ip-10-0-143-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:55:32Z" - latency: 2.026811ms message: 'network-check-target-ip-10-0-143-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:54:32Z" - latency: 2.60593ms message: 'network-check-target-ip-10-0-143-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:53:32Z" - latency: 2.144297ms message: 'network-check-target-ip-10-0-143-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:52:32Z" - latency: 2.518273ms message: 'network-check-target-ip-10-0-143-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:51:32Z" - latency: 2.533432ms message: 'network-check-target-ip-10-0-143-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:50:32Z" - latency: 3.119003ms message: 'network-check-target-ip-10-0-143-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:49:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T14:44:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-134-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-134.ec2.internal uid: 450355ff-e180-483e-96ce-1c2f58933fe5 resourceVersion: "35269" uid: 9dfc035f-6428-44fc-a3c5-b4e0694e4eee spec: sourcePod: network-check-source-dbd9cf844-qjmpc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-09T14:50:32Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.085617ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:02:32Z" - latency: 1.883111ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T15:02:32Z" - latency: 768.37µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:01:32Z" - latency: 1.80579ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T15:01:32Z" - latency: 1.086857ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:00:32Z" - latency: 1.630545ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T15:00:32Z" - latency: 877.113µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:59:32Z" - latency: 1.757798ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T14:59:32Z" - latency: 1.213622ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:58:32Z" - latency: 1.678925ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T14:58:32Z" kind: List metadata: resourceVersion: ""