apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T17:53:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-117-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-117.ec2.internal uid: f22dfa59-31a0-4921-a057-1f7dff5184e9 resourceVersion: "78162" uid: 1220f8d2-9bcf-41b1-bde5-3e4a6401b2f7 spec: sourcePod: network-check-source-65bdbbff45-pmwjr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-04T18:00:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.096729ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:49:19Z" - latency: 899.759µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:48:19Z" - latency: 4.128279ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:47:19Z" - latency: 1.229278ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:46:19Z" - latency: 1.183427ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:45:19Z" - latency: 1.593855ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:44:19Z" - latency: 854.421µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:43:19Z" - latency: 1.04657ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:42:19Z" - latency: 865.803µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:41:19Z" - latency: 1.085448ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:40:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T17:53:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-117-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-117.ec2.internal uid: f22dfa59-31a0-4921-a057-1f7dff5184e9 resourceVersion: "76172" uid: 3b116ada-6cec-49fe-90a3-0415fd3fe6bb spec: sourcePod: network-check-source-65bdbbff45-pmwjr targetEndpoint: a60fa55c8d7184c7ea7062101ab79fd0-5925e9e23be665bb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T17:59:19Z" message: 'load-balancer-api-external: tcp connection to a60fa55c8d7184c7ea7062101ab79fd0-5925e9e23be665bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.340164ms message: 'load-balancer-api-external: tcp connection to a60fa55c8d7184c7ea7062101ab79fd0-5925e9e23be665bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:47:19Z" - latency: 17.200776ms message: 'load-balancer-api-external: resolved host name a60fa55c8d7184c7ea7062101ab79fd0-5925e9e23be665bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:47:19Z" - latency: 5.357716ms message: 'load-balancer-api-external: tcp connection to a60fa55c8d7184c7ea7062101ab79fd0-5925e9e23be665bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:46:19Z" - latency: 10.344995ms message: 'load-balancer-api-external: resolved host name a60fa55c8d7184c7ea7062101ab79fd0-5925e9e23be665bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:46:19Z" - latency: 4.901159ms message: 'load-balancer-api-external: tcp connection to a60fa55c8d7184c7ea7062101ab79fd0-5925e9e23be665bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:45:19Z" - latency: 6.879418ms message: 'load-balancer-api-external: resolved host name a60fa55c8d7184c7ea7062101ab79fd0-5925e9e23be665bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:45:19Z" - latency: 3.615887ms message: 'load-balancer-api-external: tcp connection to a60fa55c8d7184c7ea7062101ab79fd0-5925e9e23be665bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:44:19Z" - latency: 8.674996ms message: 'load-balancer-api-external: resolved host name a60fa55c8d7184c7ea7062101ab79fd0-5925e9e23be665bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:44:19Z" - latency: 3.809596ms message: 'load-balancer-api-external: tcp connection to a60fa55c8d7184c7ea7062101ab79fd0-5925e9e23be665bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:43:19Z" - latency: 8.549654ms message: 'load-balancer-api-external: resolved host name a60fa55c8d7184c7ea7062101ab79fd0-5925e9e23be665bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:43:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T17:53:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-117-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-117.ec2.internal uid: f22dfa59-31a0-4921-a057-1f7dff5184e9 resourceVersion: "76171" uid: f7d47459-c083-4994-a542-7154b384275c spec: sourcePod: network-check-source-65bdbbff45-pmwjr targetEndpoint: a60fa55c8d7184c7ea7062101ab79fd0-5925e9e23be665bb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T17:59:19Z" message: 'load-balancer-api-internal: tcp connection to a60fa55c8d7184c7ea7062101ab79fd0-5925e9e23be665bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.863339ms message: 'load-balancer-api-internal: tcp connection to a60fa55c8d7184c7ea7062101ab79fd0-5925e9e23be665bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:47:19Z" - latency: 17.628312ms message: 'load-balancer-api-internal: resolved host name a60fa55c8d7184c7ea7062101ab79fd0-5925e9e23be665bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:47:19Z" - latency: 4.318296ms message: 'load-balancer-api-internal: tcp connection to a60fa55c8d7184c7ea7062101ab79fd0-5925e9e23be665bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:46:19Z" - latency: 10.371457ms message: 'load-balancer-api-internal: resolved host name a60fa55c8d7184c7ea7062101ab79fd0-5925e9e23be665bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:46:19Z" - latency: 4.885607ms message: 'load-balancer-api-internal: tcp connection to a60fa55c8d7184c7ea7062101ab79fd0-5925e9e23be665bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:45:19Z" - latency: 6.946403ms message: 'load-balancer-api-internal: resolved host name a60fa55c8d7184c7ea7062101ab79fd0-5925e9e23be665bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:45:19Z" - latency: 3.628025ms message: 'load-balancer-api-internal: tcp connection to a60fa55c8d7184c7ea7062101ab79fd0-5925e9e23be665bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:44:19Z" - latency: 8.704998ms message: 'load-balancer-api-internal: resolved host name a60fa55c8d7184c7ea7062101ab79fd0-5925e9e23be665bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:44:19Z" - latency: 3.800891ms message: 'load-balancer-api-internal: tcp connection to a60fa55c8d7184c7ea7062101ab79fd0-5925e9e23be665bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:43:19Z" - latency: 8.626366ms message: 'load-balancer-api-internal: resolved host name a60fa55c8d7184c7ea7062101ab79fd0-5925e9e23be665bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:43:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T17:53:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-117-to-network-check-target-ip-10-0-140-41 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-117.ec2.internal uid: f22dfa59-31a0-4921-a057-1f7dff5184e9 resourceVersion: "78161" uid: 7c34df1a-e616-4990-a2fc-64ce0678b28e spec: sourcePod: network-check-source-65bdbbff45-pmwjr targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-04T18:00:19Z" message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.065675ms message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:49:19Z" - latency: 1.969153ms message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:48:19Z" - latency: 3.44007ms message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:47:19Z" - latency: 2.033167ms message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:46:19Z" - latency: 1.905181ms message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:45:19Z" - latency: 1.85684ms message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:44:19Z" - latency: 1.657516ms message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:43:19Z" - latency: 2.00987ms message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:42:19Z" - latency: 1.854598ms message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:41:19Z" - latency: 2.019661ms message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:40:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T17:53:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-117-to-network-check-target-ip-10-0-141-117 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-117.ec2.internal uid: f22dfa59-31a0-4921-a057-1f7dff5184e9 resourceVersion: "78159" uid: df86449a-0619-4738-95d3-2e185839e8ab spec: sourcePod: network-check-source-65bdbbff45-pmwjr targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-04T18:00:19Z" message: 'network-check-target-ip-10-0-141-117: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.069216ms message: 'network-check-target-ip-10-0-141-117: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:49:19Z" - latency: 1.046725ms message: 'network-check-target-ip-10-0-141-117: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:48:19Z" - latency: 1.272355ms message: 'network-check-target-ip-10-0-141-117: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:47:19Z" - latency: 951.911µs message: 'network-check-target-ip-10-0-141-117: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:46:19Z" - latency: 1.302205ms message: 'network-check-target-ip-10-0-141-117: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:45:19Z" - latency: 990.994µs message: 'network-check-target-ip-10-0-141-117: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:44:19Z" - latency: 910.416µs message: 'network-check-target-ip-10-0-141-117: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:43:19Z" - latency: 887.744µs message: 'network-check-target-ip-10-0-141-117: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:42:19Z" - latency: 838.523µs message: 'network-check-target-ip-10-0-141-117: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:41:19Z" - latency: 775.871µs message: 'network-check-target-ip-10-0-141-117: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:40:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T17:53:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-117-to-network-check-target-ip-10-0-141-220 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-117.ec2.internal uid: f22dfa59-31a0-4921-a057-1f7dff5184e9 resourceVersion: "78160" uid: 39cff6ae-e3ed-439d-9af7-43287d788a11 spec: sourcePod: network-check-source-65bdbbff45-pmwjr targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-04T18:00:19Z" message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.957772ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:49:19Z" - latency: 1.850565ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:48:19Z" - latency: 3.761748ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:47:19Z" - latency: 1.869182ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:46:19Z" - latency: 2.4366ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:45:19Z" - latency: 1.962612ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:44:19Z" - latency: 2.038694ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:43:19Z" - latency: 1.691993ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:42:19Z" - latency: 1.8818ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:41:19Z" - latency: 1.783996ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:40:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T17:53:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-117-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-117.ec2.internal uid: f22dfa59-31a0-4921-a057-1f7dff5184e9 resourceVersion: "76170" uid: cb315669-4ef3-4e9c-8a2a-9d6ae347c56d spec: sourcePod: network-check-source-65bdbbff45-pmwjr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-04T17:59:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.734458ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:47:19Z" - latency: 5.781469ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T18:47:19Z" - latency: 950.392µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:46:19Z" - latency: 2.979409ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T18:46:19Z" - latency: 790.635µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:45:19Z" - latency: 1.958297ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T18:45:19Z" - latency: 995.428µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:44:19Z" - latency: 1.791648ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T18:44:19Z" - latency: 766.84µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:43:19Z" - latency: 1.60284ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T18:43:19Z" kind: List metadata: resourceVersion: ""