apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-19T08:25:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-141-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-141.ec2.internal uid: b921de57-6aae-49bc-8c7e-e4cae0ea2008 resourceVersion: "23799" uid: 6fb00810-d713-4372-b8bd-25512a30fc7e spec: sourcePod: network-check-source-7cbc45fddc-8mrzh targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-19T08:32:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 791.97µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:46:21Z" - latency: 847.169µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:45:21Z" - latency: 1.382568ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:44:21Z" - latency: 787.669µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:43:21Z" - latency: 1.215145ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:42:21Z" - latency: 899.302µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:41:21Z" - latency: 779.786µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:40:21Z" - latency: 1.10756ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:39:21Z" - latency: 1.341856ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:38:21Z" - latency: 983.232µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:37:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-19T08:25:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-141-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-141.ec2.internal uid: b921de57-6aae-49bc-8c7e-e4cae0ea2008 resourceVersion: "22413" uid: 0cfa84ba-f3b0-4d7b-b896-3d8cfd782b94 spec: sourcePod: network-check-source-7cbc45fddc-8mrzh targetEndpoint: ac1574285692c4c2fb5ed839e85e9cf2-172cce26f98ad568.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-19T08:31:21Z" message: 'load-balancer-api-external: tcp connection to ac1574285692c4c2fb5ed839e85e9cf2-172cce26f98ad568.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.781878ms message: 'load-balancer-api-external: tcp connection to ac1574285692c4c2fb5ed839e85e9cf2-172cce26f98ad568.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:43:21Z" - latency: 8.483886ms message: 'load-balancer-api-external: resolved host name ac1574285692c4c2fb5ed839e85e9cf2-172cce26f98ad568.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-19T08:43:21Z" - latency: 5.587287ms message: 'load-balancer-api-external: tcp connection to ac1574285692c4c2fb5ed839e85e9cf2-172cce26f98ad568.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:42:21Z" - latency: 8.237921ms message: 'load-balancer-api-external: resolved host name ac1574285692c4c2fb5ed839e85e9cf2-172cce26f98ad568.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-19T08:42:21Z" - latency: 5.548653ms message: 'load-balancer-api-external: tcp connection to ac1574285692c4c2fb5ed839e85e9cf2-172cce26f98ad568.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:41:21Z" - latency: 7.829537ms message: 'load-balancer-api-external: resolved host name ac1574285692c4c2fb5ed839e85e9cf2-172cce26f98ad568.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-19T08:41:21Z" - latency: 6.411907ms message: 'load-balancer-api-external: tcp connection to ac1574285692c4c2fb5ed839e85e9cf2-172cce26f98ad568.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:40:21Z" - latency: 8.933694ms message: 'load-balancer-api-external: resolved host name ac1574285692c4c2fb5ed839e85e9cf2-172cce26f98ad568.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-19T08:40:21Z" - latency: 5.623685ms message: 'load-balancer-api-external: tcp connection to ac1574285692c4c2fb5ed839e85e9cf2-172cce26f98ad568.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:39:21Z" - latency: 8.733001ms message: 'load-balancer-api-external: resolved host name ac1574285692c4c2fb5ed839e85e9cf2-172cce26f98ad568.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-19T08:39:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-19T08:25:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-141-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-141.ec2.internal uid: b921de57-6aae-49bc-8c7e-e4cae0ea2008 resourceVersion: "22414" uid: 190c3551-b371-48b5-8a12-046806b138a4 spec: sourcePod: network-check-source-7cbc45fddc-8mrzh targetEndpoint: ac1574285692c4c2fb5ed839e85e9cf2-172cce26f98ad568.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-19T08:31:21Z" message: 'load-balancer-api-internal: tcp connection to ac1574285692c4c2fb5ed839e85e9cf2-172cce26f98ad568.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.776898ms message: 'load-balancer-api-internal: tcp connection to ac1574285692c4c2fb5ed839e85e9cf2-172cce26f98ad568.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:43:21Z" - latency: 8.564101ms message: 'load-balancer-api-internal: resolved host name ac1574285692c4c2fb5ed839e85e9cf2-172cce26f98ad568.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-19T08:43:21Z" - latency: 5.073165ms message: 'load-balancer-api-internal: tcp connection to ac1574285692c4c2fb5ed839e85e9cf2-172cce26f98ad568.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:42:21Z" - latency: 8.2935ms message: 'load-balancer-api-internal: resolved host name ac1574285692c4c2fb5ed839e85e9cf2-172cce26f98ad568.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-19T08:42:21Z" - latency: 5.584668ms message: 'load-balancer-api-internal: tcp connection to ac1574285692c4c2fb5ed839e85e9cf2-172cce26f98ad568.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:41:21Z" - latency: 7.751298ms message: 'load-balancer-api-internal: resolved host name ac1574285692c4c2fb5ed839e85e9cf2-172cce26f98ad568.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-19T08:41:21Z" - latency: 6.417295ms message: 'load-balancer-api-internal: tcp connection to ac1574285692c4c2fb5ed839e85e9cf2-172cce26f98ad568.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:40:21Z" - latency: 8.973255ms message: 'load-balancer-api-internal: resolved host name ac1574285692c4c2fb5ed839e85e9cf2-172cce26f98ad568.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-19T08:40:21Z" - latency: 5.567351ms message: 'load-balancer-api-internal: tcp connection to ac1574285692c4c2fb5ed839e85e9cf2-172cce26f98ad568.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:39:21Z" - latency: 8.747537ms message: 'load-balancer-api-internal: resolved host name ac1574285692c4c2fb5ed839e85e9cf2-172cce26f98ad568.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-19T08:39:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-19T08:25:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-141-to-network-check-target-ip-10-0-134-26 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-141.ec2.internal uid: b921de57-6aae-49bc-8c7e-e4cae0ea2008 resourceVersion: "23797" uid: b3d36e57-3712-4d8b-874d-6f89d686ee90 spec: sourcePod: network-check-source-7cbc45fddc-8mrzh targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-19T08:32:21Z" message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.263058ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:46:21Z" - latency: 2.53959ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:45:21Z" - latency: 2.294985ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:44:21Z" - latency: 2.06245ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:43:21Z" - latency: 2.395874ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:42:21Z" - latency: 2.009873ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:41:21Z" - latency: 2.236448ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:40:21Z" - latency: 2.326293ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:39:21Z" - latency: 2.286502ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:38:21Z" - latency: 2.571999ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:37:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-19T08:25:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-141-to-network-check-target-ip-10-0-140-141 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-141.ec2.internal uid: b921de57-6aae-49bc-8c7e-e4cae0ea2008 resourceVersion: "23796" uid: bfac5824-1860-4194-96c8-58cf4e0904a6 spec: sourcePod: network-check-source-7cbc45fddc-8mrzh targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-19T08:32:21Z" message: 'network-check-target-ip-10-0-140-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 816.84µs message: 'network-check-target-ip-10-0-140-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:46:21Z" - latency: 1.307759ms message: 'network-check-target-ip-10-0-140-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:45:21Z" - latency: 1.594833ms message: 'network-check-target-ip-10-0-140-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:44:21Z" - latency: 931.669µs message: 'network-check-target-ip-10-0-140-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:43:21Z" - latency: 1.070127ms message: 'network-check-target-ip-10-0-140-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:42:21Z" - latency: 813.832µs message: 'network-check-target-ip-10-0-140-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:41:21Z" - latency: 867.886µs message: 'network-check-target-ip-10-0-140-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:40:21Z" - latency: 990.719µs message: 'network-check-target-ip-10-0-140-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:39:21Z" - latency: 1.443557ms message: 'network-check-target-ip-10-0-140-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:38:21Z" - latency: 962.922µs message: 'network-check-target-ip-10-0-140-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:37:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-19T08:25:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-141-to-network-check-target-ip-10-0-142-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-141.ec2.internal uid: b921de57-6aae-49bc-8c7e-e4cae0ea2008 resourceVersion: "23798" uid: 263cc93a-4ae9-4fbd-a711-3c578c0d96f0 spec: sourcePod: network-check-source-7cbc45fddc-8mrzh targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-19T08:32:21Z" message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.260716ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:46:21Z" - latency: 2.979309ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:45:21Z" - latency: 2.358799ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:44:21Z" - latency: 2.187383ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:43:21Z" - latency: 2.589223ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:42:21Z" - latency: 2.059663ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:41:21Z" - latency: 2.190017ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:40:21Z" - latency: 2.424274ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:39:21Z" - latency: 2.262896ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:38:21Z" - latency: 2.262847ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:37:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-19T08:25:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-141-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-141.ec2.internal uid: b921de57-6aae-49bc-8c7e-e4cae0ea2008 resourceVersion: "22412" uid: d9f9741f-0a15-4e0d-8489-11862fab1c7b spec: sourcePod: network-check-source-7cbc45fddc-8mrzh targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-19T08:31:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 900.671µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:43:21Z" - latency: 2.452102ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-19T08:43:21Z" - latency: 1.046598ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:42:21Z" - latency: 1.929944ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-19T08:42:21Z" - latency: 856.503µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:41:21Z" - latency: 1.794742ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-19T08:41:21Z" - latency: 1.071814ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:40:21Z" - latency: 1.835591ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-19T08:40:21Z" - latency: 953.897µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-19T08:39:21Z" - latency: 1.934517ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-19T08:39:21Z" kind: List metadata: resourceVersion: ""