apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:06:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-64-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-64.ec2.internal uid: 7ad8b124-1ebb-4b6b-99ec-246739341046 resourceVersion: "28658" uid: e6dc30bd-5fd4-44f6-9a0a-65aa48a0445f spec: sourcePod: network-check-source-dbd9cf844-jvrxs targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T15:13:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 821.591µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:20:57Z" - latency: 1.175333ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:19:57Z" - latency: 1.332829ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:18:57Z" - latency: 1.092274ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:17:57Z" - latency: 922.69µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:16:57Z" - latency: 1.110502ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:15:57Z" - latency: 1.555774ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:14:57Z" - latency: 1.093257ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:13:57Z" - latency: 1.276918ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:12:57Z" - latency: 1.102868ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:11:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:06:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-64-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-64.ec2.internal uid: 7ad8b124-1ebb-4b6b-99ec-246739341046 resourceVersion: "27364" uid: d2dc3d60-f0dc-460c-8f3a-06bed652e744 spec: sourcePod: network-check-source-dbd9cf844-jvrxs targetEndpoint: a596fc5c8133341b3a865d69ad18cd42-a7334047ed04b2c1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T15:12:57Z" message: 'load-balancer-api-external: tcp connection to a596fc5c8133341b3a865d69ad18cd42-a7334047ed04b2c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.746445ms message: 'load-balancer-api-external: tcp connection to a596fc5c8133341b3a865d69ad18cd42-a7334047ed04b2c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:18:57Z" - latency: 8.919936ms message: 'load-balancer-api-external: resolved host name a596fc5c8133341b3a865d69ad18cd42-a7334047ed04b2c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:18:57Z" - latency: 5.819938ms message: 'load-balancer-api-external: tcp connection to a596fc5c8133341b3a865d69ad18cd42-a7334047ed04b2c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:17:57Z" - latency: 9.572117ms message: 'load-balancer-api-external: resolved host name a596fc5c8133341b3a865d69ad18cd42-a7334047ed04b2c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:17:57Z" - latency: 7.815338ms message: 'load-balancer-api-external: tcp connection to a596fc5c8133341b3a865d69ad18cd42-a7334047ed04b2c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:16:57Z" - latency: 8.171913ms message: 'load-balancer-api-external: resolved host name a596fc5c8133341b3a865d69ad18cd42-a7334047ed04b2c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:16:57Z" - latency: 6.434642ms message: 'load-balancer-api-external: tcp connection to a596fc5c8133341b3a865d69ad18cd42-a7334047ed04b2c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:15:57Z" - latency: 11.354185ms message: 'load-balancer-api-external: resolved host name a596fc5c8133341b3a865d69ad18cd42-a7334047ed04b2c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:15:57Z" - latency: 5.553006ms message: 'load-balancer-api-external: tcp connection to a596fc5c8133341b3a865d69ad18cd42-a7334047ed04b2c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:14:57Z" - latency: 7.681633ms message: 'load-balancer-api-external: resolved host name a596fc5c8133341b3a865d69ad18cd42-a7334047ed04b2c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:14:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:06:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-64-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-64.ec2.internal uid: 7ad8b124-1ebb-4b6b-99ec-246739341046 resourceVersion: "27363" uid: ec28baa5-65c2-4aa4-8d04-f0c5c05786e7 spec: sourcePod: network-check-source-dbd9cf844-jvrxs targetEndpoint: a596fc5c8133341b3a865d69ad18cd42-a7334047ed04b2c1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T15:12:57Z" message: 'load-balancer-api-internal: tcp connection to a596fc5c8133341b3a865d69ad18cd42-a7334047ed04b2c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.749495ms message: 'load-balancer-api-internal: tcp connection to a596fc5c8133341b3a865d69ad18cd42-a7334047ed04b2c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:18:57Z" - latency: 8.848666ms message: 'load-balancer-api-internal: resolved host name a596fc5c8133341b3a865d69ad18cd42-a7334047ed04b2c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:18:57Z" - latency: 7.073226ms message: 'load-balancer-api-internal: tcp connection to a596fc5c8133341b3a865d69ad18cd42-a7334047ed04b2c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:17:57Z" - latency: 9.654875ms message: 'load-balancer-api-internal: resolved host name a596fc5c8133341b3a865d69ad18cd42-a7334047ed04b2c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:17:57Z" - latency: 5.751487ms message: 'load-balancer-api-internal: tcp connection to a596fc5c8133341b3a865d69ad18cd42-a7334047ed04b2c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:16:57Z" - latency: 8.196271ms message: 'load-balancer-api-internal: resolved host name a596fc5c8133341b3a865d69ad18cd42-a7334047ed04b2c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:16:57Z" - latency: 6.514615ms message: 'load-balancer-api-internal: tcp connection to a596fc5c8133341b3a865d69ad18cd42-a7334047ed04b2c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:15:57Z" - latency: 11.314835ms message: 'load-balancer-api-internal: resolved host name a596fc5c8133341b3a865d69ad18cd42-a7334047ed04b2c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:15:57Z" - latency: 7.005028ms message: 'load-balancer-api-internal: tcp connection to a596fc5c8133341b3a865d69ad18cd42-a7334047ed04b2c1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:14:57Z" - latency: 7.70061ms message: 'load-balancer-api-internal: resolved host name a596fc5c8133341b3a865d69ad18cd42-a7334047ed04b2c1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:14:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:06:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-64-to-network-check-target-ip-10-0-140-126 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-64.ec2.internal uid: 7ad8b124-1ebb-4b6b-99ec-246739341046 resourceVersion: "28657" uid: edfae38e-509f-4673-80a2-abbf18492a1c spec: sourcePod: network-check-source-dbd9cf844-jvrxs targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T15:13:57Z" message: 'network-check-target-ip-10-0-140-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.245826ms message: 'network-check-target-ip-10-0-140-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:20:57Z" - latency: 2.164252ms message: 'network-check-target-ip-10-0-140-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:19:57Z" - latency: 2.006457ms message: 'network-check-target-ip-10-0-140-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:18:57Z" - latency: 2.23357ms message: 'network-check-target-ip-10-0-140-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:17:57Z" - latency: 2.176158ms message: 'network-check-target-ip-10-0-140-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:16:57Z" - latency: 2.129492ms message: 'network-check-target-ip-10-0-140-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:15:57Z" - latency: 2.142471ms message: 'network-check-target-ip-10-0-140-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:14:57Z" - latency: 1.989519ms message: 'network-check-target-ip-10-0-140-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:13:57Z" - latency: 2.103616ms message: 'network-check-target-ip-10-0-140-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:12:57Z" - latency: 2.191468ms message: 'network-check-target-ip-10-0-140-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:11:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:06:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-64-to-network-check-target-ip-10-0-140-64 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-64.ec2.internal uid: 7ad8b124-1ebb-4b6b-99ec-246739341046 resourceVersion: "28655" uid: d0676f8a-6e7a-4050-a177-6fdb24e9067c spec: sourcePod: network-check-source-dbd9cf844-jvrxs targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T15:13:57Z" message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.015166ms message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:20:57Z" - latency: 851.505µs message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:19:57Z" - latency: 1.478327ms message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:18:57Z" - latency: 1.351802ms message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:17:57Z" - latency: 946.147µs message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:16:57Z" - latency: 1.150784ms message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:15:57Z" - latency: 755.267µs message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:14:57Z" - latency: 830.024µs message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:13:57Z" - latency: 815.272µs message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:12:57Z" - latency: 980.6µs message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:11:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:06:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-64-to-network-check-target-ip-10-0-143-5 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-64.ec2.internal uid: 7ad8b124-1ebb-4b6b-99ec-246739341046 resourceVersion: "28656" uid: 0dbdce66-16ca-4241-86f6-8f9586c45cb7 spec: sourcePod: network-check-source-dbd9cf844-jvrxs targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T15:13:57Z" message: 'network-check-target-ip-10-0-143-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.022798ms message: 'network-check-target-ip-10-0-143-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:20:57Z" - latency: 1.846563ms message: 'network-check-target-ip-10-0-143-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:19:57Z" - latency: 1.809482ms message: 'network-check-target-ip-10-0-143-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:18:57Z" - latency: 2.052148ms message: 'network-check-target-ip-10-0-143-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:17:57Z" - latency: 1.793974ms message: 'network-check-target-ip-10-0-143-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:16:57Z" - latency: 1.615502ms message: 'network-check-target-ip-10-0-143-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:15:57Z" - latency: 1.833698ms message: 'network-check-target-ip-10-0-143-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:14:57Z" - latency: 1.828595ms message: 'network-check-target-ip-10-0-143-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:13:57Z" - latency: 1.877948ms message: 'network-check-target-ip-10-0-143-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:12:57Z" - latency: 1.916261ms message: 'network-check-target-ip-10-0-143-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:11:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:06:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-64-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-64.ec2.internal uid: 7ad8b124-1ebb-4b6b-99ec-246739341046 resourceVersion: "27362" uid: 6de8517a-d5e4-4c36-881c-87d831909b3a spec: sourcePod: network-check-source-dbd9cf844-jvrxs targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T15:12:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 761.455µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:18:57Z" - latency: 2.098645ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:18:57Z" - latency: 895.157µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:17:57Z" - latency: 1.76553ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:17:57Z" - latency: 955.695µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:16:57Z" - latency: 1.751441ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:16:57Z" - latency: 1.168214ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:15:57Z" - latency: 1.704194ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:15:57Z" - latency: 892.788µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:14:57Z" - latency: 1.753993ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:14:57Z" kind: List metadata: resourceVersion: ""