apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T21:12:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-152-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-152.ec2.internal uid: b687ed41-ec35-4164-9bf7-8404ac5671e3 resourceVersion: "60494" uid: 7e21a65e-420d-48d0-9d17-99a696be3712 spec: sourcePod: network-check-source-869dcfcdcd-qpxz7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-13T21:19:18Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.09164ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:54:18Z" - latency: 1.02221ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:53:18Z" - latency: 887.011µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:52:18Z" - latency: 925.511µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:51:18Z" - latency: 1.248055ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:50:18Z" - latency: 1.257373ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:49:18Z" - latency: 895.223µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:48:18Z" - latency: 1.055612ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:47:18Z" - latency: 985.145µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:46:18Z" - latency: 1.058085ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:45:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T21:12:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-152-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-152.ec2.internal uid: b687ed41-ec35-4164-9bf7-8404ac5671e3 resourceVersion: "60497" uid: b90e8a8f-fc9b-4dd1-aa5e-6d1b17be7443 spec: sourcePod: network-check-source-869dcfcdcd-qpxz7 targetEndpoint: ad937aea2ec5a4378a0a64ac57493bb4-72ab0bbc73cf858f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T21:18:18Z" message: 'load-balancer-api-external: tcp connection to ad937aea2ec5a4378a0a64ac57493bb4-72ab0bbc73cf858f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.315833ms message: 'load-balancer-api-external: tcp connection to ad937aea2ec5a4378a0a64ac57493bb4-72ab0bbc73cf858f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:54:18Z" - latency: 9.113549ms message: 'load-balancer-api-external: resolved host name ad937aea2ec5a4378a0a64ac57493bb4-72ab0bbc73cf858f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:54:18Z" - latency: 4.878038ms message: 'load-balancer-api-external: tcp connection to ad937aea2ec5a4378a0a64ac57493bb4-72ab0bbc73cf858f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:53:18Z" - latency: 9.045935ms message: 'load-balancer-api-external: resolved host name ad937aea2ec5a4378a0a64ac57493bb4-72ab0bbc73cf858f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:53:18Z" - latency: 3.647544ms message: 'load-balancer-api-external: tcp connection to ad937aea2ec5a4378a0a64ac57493bb4-72ab0bbc73cf858f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:52:18Z" - latency: 13.995216ms message: 'load-balancer-api-external: resolved host name ad937aea2ec5a4378a0a64ac57493bb4-72ab0bbc73cf858f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:52:18Z" - latency: 4.284269ms message: 'load-balancer-api-external: tcp connection to ad937aea2ec5a4378a0a64ac57493bb4-72ab0bbc73cf858f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:51:18Z" - latency: 8.360021ms message: 'load-balancer-api-external: resolved host name ad937aea2ec5a4378a0a64ac57493bb4-72ab0bbc73cf858f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:51:18Z" - latency: 5.103116ms message: 'load-balancer-api-external: tcp connection to ad937aea2ec5a4378a0a64ac57493bb4-72ab0bbc73cf858f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:50:18Z" - latency: 8.018319ms message: 'load-balancer-api-external: resolved host name ad937aea2ec5a4378a0a64ac57493bb4-72ab0bbc73cf858f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:50:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T21:12:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-152-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-152.ec2.internal uid: b687ed41-ec35-4164-9bf7-8404ac5671e3 resourceVersion: "60496" uid: a19632b2-7628-4203-99ea-252671b07122 spec: sourcePod: network-check-source-869dcfcdcd-qpxz7 targetEndpoint: ad937aea2ec5a4378a0a64ac57493bb4-72ab0bbc73cf858f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T21:18:18Z" message: 'load-balancer-api-internal: tcp connection to ad937aea2ec5a4378a0a64ac57493bb4-72ab0bbc73cf858f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.027575ms message: 'load-balancer-api-internal: tcp connection to ad937aea2ec5a4378a0a64ac57493bb4-72ab0bbc73cf858f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:54:18Z" - latency: 9.255793ms message: 'load-balancer-api-internal: resolved host name ad937aea2ec5a4378a0a64ac57493bb4-72ab0bbc73cf858f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:54:18Z" - latency: 4.809386ms message: 'load-balancer-api-internal: tcp connection to ad937aea2ec5a4378a0a64ac57493bb4-72ab0bbc73cf858f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:53:18Z" - latency: 9.071594ms message: 'load-balancer-api-internal: resolved host name ad937aea2ec5a4378a0a64ac57493bb4-72ab0bbc73cf858f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:53:18Z" - latency: 3.654074ms message: 'load-balancer-api-internal: tcp connection to ad937aea2ec5a4378a0a64ac57493bb4-72ab0bbc73cf858f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:52:18Z" - latency: 14.130684ms message: 'load-balancer-api-internal: resolved host name ad937aea2ec5a4378a0a64ac57493bb4-72ab0bbc73cf858f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:52:18Z" - latency: 4.35033ms message: 'load-balancer-api-internal: tcp connection to ad937aea2ec5a4378a0a64ac57493bb4-72ab0bbc73cf858f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:51:18Z" - latency: 8.316711ms message: 'load-balancer-api-internal: resolved host name ad937aea2ec5a4378a0a64ac57493bb4-72ab0bbc73cf858f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:51:18Z" - latency: 5.015941ms message: 'load-balancer-api-internal: tcp connection to ad937aea2ec5a4378a0a64ac57493bb4-72ab0bbc73cf858f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:50:18Z" - latency: 8.167849ms message: 'load-balancer-api-internal: resolved host name ad937aea2ec5a4378a0a64ac57493bb4-72ab0bbc73cf858f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:50:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T21:12:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-152-to-network-check-target-ip-10-0-128-82 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-152.ec2.internal uid: b687ed41-ec35-4164-9bf7-8404ac5671e3 resourceVersion: "60492" uid: c4158f0e-d396-4104-9892-3f9f0dec920b spec: sourcePod: network-check-source-869dcfcdcd-qpxz7 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-13T21:19:18Z" message: 'network-check-target-ip-10-0-128-82: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.080965ms message: 'network-check-target-ip-10-0-128-82: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:54:18Z" - latency: 1.876621ms message: 'network-check-target-ip-10-0-128-82: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:53:18Z" - latency: 1.875259ms message: 'network-check-target-ip-10-0-128-82: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:52:18Z" - latency: 1.800241ms message: 'network-check-target-ip-10-0-128-82: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:51:18Z" - latency: 1.716455ms message: 'network-check-target-ip-10-0-128-82: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:50:18Z" - latency: 1.879213ms message: 'network-check-target-ip-10-0-128-82: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:49:18Z" - latency: 2.05553ms message: 'network-check-target-ip-10-0-128-82: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:48:18Z" - latency: 2.028855ms message: 'network-check-target-ip-10-0-128-82: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:47:18Z" - latency: 1.747883ms message: 'network-check-target-ip-10-0-128-82: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:46:18Z" - latency: 2.048093ms message: 'network-check-target-ip-10-0-128-82: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:45:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T21:12:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-152-to-network-check-target-ip-10-0-133-136 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-152.ec2.internal uid: b687ed41-ec35-4164-9bf7-8404ac5671e3 resourceVersion: "60490" uid: bb72f9f6-04d7-4c50-a642-efa5b6aa13f2 spec: sourcePod: network-check-source-869dcfcdcd-qpxz7 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-13T21:19:18Z" message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.740236ms message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:54:18Z" - latency: 2.040859ms message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:53:18Z" - latency: 2.04035ms message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:52:18Z" - latency: 1.965969ms message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:51:18Z" - latency: 2.215817ms message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:50:18Z" - latency: 2.013297ms message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:49:18Z" - latency: 2.06709ms message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:48:18Z" - latency: 2.311453ms message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:47:18Z" - latency: 1.758483ms message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:46:18Z" - latency: 1.940761ms message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:45:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T21:12:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-152-to-network-check-target-ip-10-0-141-152 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-152.ec2.internal uid: b687ed41-ec35-4164-9bf7-8404ac5671e3 resourceVersion: "60491" uid: 3e524bdd-4705-499f-b8e5-02e35e7fd0ce spec: sourcePod: network-check-source-869dcfcdcd-qpxz7 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-13T21:19:18Z" message: 'network-check-target-ip-10-0-141-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 915.677µs message: 'network-check-target-ip-10-0-141-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:54:18Z" - latency: 825.727µs message: 'network-check-target-ip-10-0-141-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:53:18Z" - latency: 966.224µs message: 'network-check-target-ip-10-0-141-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:52:18Z" - latency: 1.092878ms message: 'network-check-target-ip-10-0-141-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:51:18Z" - latency: 681.17µs message: 'network-check-target-ip-10-0-141-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:50:18Z" - latency: 814.244µs message: 'network-check-target-ip-10-0-141-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:49:18Z" - latency: 963.969µs message: 'network-check-target-ip-10-0-141-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:48:18Z" - latency: 1.017587ms message: 'network-check-target-ip-10-0-141-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:47:18Z" - latency: 872.52µs message: 'network-check-target-ip-10-0-141-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:46:18Z" - latency: 869.776µs message: 'network-check-target-ip-10-0-141-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:45:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T21:12:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-152-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-152.ec2.internal uid: b687ed41-ec35-4164-9bf7-8404ac5671e3 resourceVersion: "60493" uid: e338f1f5-9bf5-4041-b81f-2d917d3bb324 spec: sourcePod: network-check-source-869dcfcdcd-qpxz7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-13T21:18:18Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.256057ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:54:18Z" - latency: 1.76614ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T21:54:18Z" - latency: 900.111µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:53:18Z" - latency: 2.401446ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T21:53:18Z" - latency: 895.015µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:52:18Z" - latency: 1.763055ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T21:52:18Z" - latency: 1.000699ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:51:18Z" - latency: 1.75604ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T21:51:18Z" - latency: 1.103606ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:50:18Z" - latency: 1.545167ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T21:50:18Z" kind: List metadata: resourceVersion: ""