apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:53:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-31-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-31.ec2.internal uid: 7fe8505d-af40-4e28-a58c-9d5da5ebc66c resourceVersion: "69663" uid: 08f502da-330a-4c61-a0ee-30b1f448695b spec: sourcePod: network-check-source-7bc5b6bf85-97n2z targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-16T22:00:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.107369ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:42:59Z" - latency: 1.050051ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:41:59Z" - latency: 1.113588ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:40:59Z" - latency: 924.118µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:39:59Z" - latency: 1.218604ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:38:59Z" - latency: 954.373µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:37:59Z" - latency: 1.21317ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:36:59Z" - latency: 1.409002ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:35:59Z" - latency: 874.59µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:34:59Z" - latency: 1.040777ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:33:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:53:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-31-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-31.ec2.internal uid: 7fe8505d-af40-4e28-a58c-9d5da5ebc66c resourceVersion: "75428" uid: b8284047-1e8a-4e7d-af57-dadf0618e7f6 spec: sourcePod: network-check-source-7bc5b6bf85-97n2z targetEndpoint: aa31fc6a1045843428bb3dcbfe7b3e85-00ce526af4e0453d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T21:59:59Z" message: 'load-balancer-api-external: tcp connection to aa31fc6a1045843428bb3dcbfe7b3e85-00ce526af4e0453d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.885067ms message: 'load-balancer-api-external: tcp connection to aa31fc6a1045843428bb3dcbfe7b3e85-00ce526af4e0453d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:47:59Z" - latency: 6.847512ms message: 'load-balancer-api-external: resolved host name aa31fc6a1045843428bb3dcbfe7b3e85-00ce526af4e0453d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:47:59Z" - latency: 4.349199ms message: 'load-balancer-api-external: tcp connection to aa31fc6a1045843428bb3dcbfe7b3e85-00ce526af4e0453d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:46:59Z" - latency: 9.080282ms message: 'load-balancer-api-external: resolved host name aa31fc6a1045843428bb3dcbfe7b3e85-00ce526af4e0453d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:46:59Z" - latency: 4.655121ms message: 'load-balancer-api-external: tcp connection to aa31fc6a1045843428bb3dcbfe7b3e85-00ce526af4e0453d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:45:59Z" - latency: 6.763706ms message: 'load-balancer-api-external: resolved host name aa31fc6a1045843428bb3dcbfe7b3e85-00ce526af4e0453d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:45:59Z" - latency: 5.482981ms message: 'load-balancer-api-external: tcp connection to aa31fc6a1045843428bb3dcbfe7b3e85-00ce526af4e0453d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:44:59Z" - latency: 6.937167ms message: 'load-balancer-api-external: resolved host name aa31fc6a1045843428bb3dcbfe7b3e85-00ce526af4e0453d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:44:59Z" - latency: 4.399281ms message: 'load-balancer-api-external: tcp connection to aa31fc6a1045843428bb3dcbfe7b3e85-00ce526af4e0453d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:43:59Z" - latency: 7.103138ms message: 'load-balancer-api-external: resolved host name aa31fc6a1045843428bb3dcbfe7b3e85-00ce526af4e0453d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:43:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:53:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-31-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-31.ec2.internal uid: 7fe8505d-af40-4e28-a58c-9d5da5ebc66c resourceVersion: "75427" uid: 9f4d311a-1dbf-4bab-ad41-df074e558396 spec: sourcePod: network-check-source-7bc5b6bf85-97n2z targetEndpoint: aa31fc6a1045843428bb3dcbfe7b3e85-00ce526af4e0453d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T21:59:59Z" message: 'load-balancer-api-internal: tcp connection to aa31fc6a1045843428bb3dcbfe7b3e85-00ce526af4e0453d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.405684ms message: 'load-balancer-api-internal: tcp connection to aa31fc6a1045843428bb3dcbfe7b3e85-00ce526af4e0453d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:47:59Z" - latency: 6.910227ms message: 'load-balancer-api-internal: resolved host name aa31fc6a1045843428bb3dcbfe7b3e85-00ce526af4e0453d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:47:59Z" - latency: 4.051889ms message: 'load-balancer-api-internal: tcp connection to aa31fc6a1045843428bb3dcbfe7b3e85-00ce526af4e0453d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:46:59Z" - latency: 8.974379ms message: 'load-balancer-api-internal: resolved host name aa31fc6a1045843428bb3dcbfe7b3e85-00ce526af4e0453d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:46:59Z" - latency: 4.656299ms message: 'load-balancer-api-internal: tcp connection to aa31fc6a1045843428bb3dcbfe7b3e85-00ce526af4e0453d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:45:59Z" - latency: 6.795553ms message: 'load-balancer-api-internal: resolved host name aa31fc6a1045843428bb3dcbfe7b3e85-00ce526af4e0453d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:45:59Z" - latency: 5.497139ms message: 'load-balancer-api-internal: tcp connection to aa31fc6a1045843428bb3dcbfe7b3e85-00ce526af4e0453d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:44:59Z" - latency: 7.008271ms message: 'load-balancer-api-internal: resolved host name aa31fc6a1045843428bb3dcbfe7b3e85-00ce526af4e0453d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:44:59Z" - latency: 5.188656ms message: 'load-balancer-api-internal: tcp connection to aa31fc6a1045843428bb3dcbfe7b3e85-00ce526af4e0453d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:43:59Z" - latency: 7.161669ms message: 'load-balancer-api-internal: resolved host name aa31fc6a1045843428bb3dcbfe7b3e85-00ce526af4e0453d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:43:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:53:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-31-to-network-check-target-ip-10-0-136-31 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-31.ec2.internal uid: 7fe8505d-af40-4e28-a58c-9d5da5ebc66c resourceVersion: "69660" uid: 35cb0770-34dd-462b-a424-8e9e66aad589 spec: sourcePod: network-check-source-7bc5b6bf85-97n2z targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-16T22:00:59Z" message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 730.946µs message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:42:59Z" - latency: 826.598µs message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:41:59Z" - latency: 921.652µs message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:40:59Z" - latency: 807.238µs message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:39:59Z" - latency: 1.301253ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:38:59Z" - latency: 1.125446ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:37:59Z" - latency: 1.366139ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:36:59Z" - latency: 950.13µs message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:35:59Z" - latency: 951.541µs message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:34:59Z" - latency: 820.663µs message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:33:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:53:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-31-to-network-check-target-ip-10-0-138-223 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-31.ec2.internal uid: 7fe8505d-af40-4e28-a58c-9d5da5ebc66c resourceVersion: "69661" uid: 9fdc6563-e62b-4c34-ae90-e19988b7d9dc spec: sourcePod: network-check-source-7bc5b6bf85-97n2z targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T22:00:59Z" message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.347537ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:42:59Z" - latency: 2.594816ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:41:59Z" - latency: 2.140993ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:40:59Z" - latency: 1.814205ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:39:59Z" - latency: 1.994726ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:38:59Z" - latency: 2.287697ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:37:59Z" - latency: 2.206368ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:36:59Z" - latency: 2.322253ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:35:59Z" - latency: 1.777566ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:34:59Z" - latency: 2.155999ms message: 'network-check-target-ip-10-0-138-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:33:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:53:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-31-to-network-check-target-ip-10-0-139-156 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-31.ec2.internal uid: 7fe8505d-af40-4e28-a58c-9d5da5ebc66c resourceVersion: "69662" uid: a4d1e363-e0c8-4b1c-b9b8-ccca059c6f89 spec: sourcePod: network-check-source-7bc5b6bf85-97n2z targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-16T22:00:59Z" message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.071717ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:42:59Z" - latency: 1.829613ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:41:59Z" - latency: 1.468709ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:40:59Z" - latency: 1.808327ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:39:59Z" - latency: 1.922647ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:38:59Z" - latency: 1.942111ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:37:59Z" - latency: 1.929455ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:36:59Z" - latency: 1.622394ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:35:59Z" - latency: 1.691378ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:34:59Z" - latency: 1.929408ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:33:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:53:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-31-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-31.ec2.internal uid: 7fe8505d-af40-4e28-a58c-9d5da5ebc66c resourceVersion: "75424" uid: 76a515b7-a5ea-4b49-95d0-7f4b8119c432 spec: sourcePod: network-check-source-7bc5b6bf85-97n2z targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-16T21:59:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 929.741µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:47:59Z" - latency: 1.870934ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T22:47:59Z" - latency: 891.592µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:46:59Z" - latency: 1.919557ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T22:46:59Z" - latency: 1.213146ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:45:59Z" - latency: 1.767261ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T22:45:59Z" - latency: 945.782µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:44:59Z" - latency: 1.677604ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T22:44:59Z" - latency: 756.091µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:43:59Z" - latency: 1.758485ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T22:43:59Z" kind: List metadata: resourceVersion: ""