apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:52:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-140-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-140.ec2.internal uid: 42a569a1-6c78-4304-9542-c8ec312e03f6 resourceVersion: "46481" uid: f07a5848-1c01-4777-9185-56963a46c588 spec: sourcePod: network-check-source-7bc5b6bf85-kcprj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-17T17:59:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.651602ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:20:21Z" - latency: 1.183629ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:19:21Z" - latency: 1.079193ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:18:21Z" - latency: 1.185697ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:17:21Z" - latency: 1.228347ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:16:21Z" - latency: 1.014915ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:15:21Z" - latency: 1.468608ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:14:21Z" - latency: 1.176826ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:13:21Z" - latency: 1.123217ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:12:21Z" - latency: 811.625µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:11:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:52:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-140-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-140.ec2.internal uid: 42a569a1-6c78-4304-9542-c8ec312e03f6 resourceVersion: "48004" uid: a3b81eb9-38a3-4b7b-ab5f-7832c7ca611a spec: sourcePod: network-check-source-7bc5b6bf85-kcprj targetEndpoint: acc49473217c9412a9ffbc2889e00a6c-f825af96d0d0fc40.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T17:58:21Z" message: 'load-balancer-api-external: tcp connection to acc49473217c9412a9ffbc2889e00a6c-f825af96d0d0fc40.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.370891ms message: 'load-balancer-api-external: tcp connection to acc49473217c9412a9ffbc2889e00a6c-f825af96d0d0fc40.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:22:21Z" - latency: 7.158361ms message: 'load-balancer-api-external: resolved host name acc49473217c9412a9ffbc2889e00a6c-f825af96d0d0fc40.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:22:21Z" - latency: 5.602097ms message: 'load-balancer-api-external: tcp connection to acc49473217c9412a9ffbc2889e00a6c-f825af96d0d0fc40.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:21:21Z" - latency: 7.251219ms message: 'load-balancer-api-external: resolved host name acc49473217c9412a9ffbc2889e00a6c-f825af96d0d0fc40.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:21:21Z" - latency: 6.433226ms message: 'load-balancer-api-external: tcp connection to acc49473217c9412a9ffbc2889e00a6c-f825af96d0d0fc40.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:20:21Z" - latency: 7.674652ms message: 'load-balancer-api-external: resolved host name acc49473217c9412a9ffbc2889e00a6c-f825af96d0d0fc40.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:20:21Z" - latency: 4.318843ms message: 'load-balancer-api-external: tcp connection to acc49473217c9412a9ffbc2889e00a6c-f825af96d0d0fc40.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:19:21Z" - latency: 7.252993ms message: 'load-balancer-api-external: resolved host name acc49473217c9412a9ffbc2889e00a6c-f825af96d0d0fc40.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:19:21Z" - latency: 4.65981ms message: 'load-balancer-api-external: tcp connection to acc49473217c9412a9ffbc2889e00a6c-f825af96d0d0fc40.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:18:21Z" - latency: 6.981289ms message: 'load-balancer-api-external: resolved host name acc49473217c9412a9ffbc2889e00a6c-f825af96d0d0fc40.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:18:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:52:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-140-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-140.ec2.internal uid: 42a569a1-6c78-4304-9542-c8ec312e03f6 resourceVersion: "48003" uid: a0c3d315-1ca0-4875-afa2-45e0b855f1cd spec: sourcePod: network-check-source-7bc5b6bf85-kcprj targetEndpoint: acc49473217c9412a9ffbc2889e00a6c-f825af96d0d0fc40.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T17:58:21Z" message: 'load-balancer-api-internal: tcp connection to acc49473217c9412a9ffbc2889e00a6c-f825af96d0d0fc40.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.151045ms message: 'load-balancer-api-internal: tcp connection to acc49473217c9412a9ffbc2889e00a6c-f825af96d0d0fc40.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:22:21Z" - latency: 7.230385ms message: 'load-balancer-api-internal: resolved host name acc49473217c9412a9ffbc2889e00a6c-f825af96d0d0fc40.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:22:21Z" - latency: 5.676655ms message: 'load-balancer-api-internal: tcp connection to acc49473217c9412a9ffbc2889e00a6c-f825af96d0d0fc40.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:21:21Z" - latency: 7.304228ms message: 'load-balancer-api-internal: resolved host name acc49473217c9412a9ffbc2889e00a6c-f825af96d0d0fc40.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:21:21Z" - latency: 6.030857ms message: 'load-balancer-api-internal: tcp connection to acc49473217c9412a9ffbc2889e00a6c-f825af96d0d0fc40.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:20:21Z" - latency: 7.582334ms message: 'load-balancer-api-internal: resolved host name acc49473217c9412a9ffbc2889e00a6c-f825af96d0d0fc40.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:20:21Z" - latency: 3.507213ms message: 'load-balancer-api-internal: tcp connection to acc49473217c9412a9ffbc2889e00a6c-f825af96d0d0fc40.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:19:21Z" - latency: 7.215971ms message: 'load-balancer-api-internal: resolved host name acc49473217c9412a9ffbc2889e00a6c-f825af96d0d0fc40.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:19:21Z" - latency: 4.678913ms message: 'load-balancer-api-internal: tcp connection to acc49473217c9412a9ffbc2889e00a6c-f825af96d0d0fc40.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:18:21Z" - latency: 7.057941ms message: 'load-balancer-api-internal: resolved host name acc49473217c9412a9ffbc2889e00a6c-f825af96d0d0fc40.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:18:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:52:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-140-to-network-check-target-ip-10-0-135-140 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-140.ec2.internal uid: 42a569a1-6c78-4304-9542-c8ec312e03f6 resourceVersion: "46478" uid: 0cd8390f-260b-4f88-b192-5b6a4a71d021 spec: sourcePod: network-check-source-7bc5b6bf85-kcprj targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-17T17:59:21Z" message: 'network-check-target-ip-10-0-135-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 827.244µs message: 'network-check-target-ip-10-0-135-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:20:21Z" - latency: 938.503µs message: 'network-check-target-ip-10-0-135-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:19:21Z" - latency: 994.374µs message: 'network-check-target-ip-10-0-135-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:18:21Z" - latency: 983.851µs message: 'network-check-target-ip-10-0-135-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:17:21Z" - latency: 915.309µs message: 'network-check-target-ip-10-0-135-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:16:21Z" - latency: 983.321µs message: 'network-check-target-ip-10-0-135-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:15:21Z" - latency: 831.706µs message: 'network-check-target-ip-10-0-135-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:14:21Z" - latency: 955.585µs message: 'network-check-target-ip-10-0-135-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:13:21Z" - latency: 950.041µs message: 'network-check-target-ip-10-0-135-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:12:21Z" - latency: 851.947µs message: 'network-check-target-ip-10-0-135-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:11:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:52:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-140-to-network-check-target-ip-10-0-138-33 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-140.ec2.internal uid: 42a569a1-6c78-4304-9542-c8ec312e03f6 resourceVersion: "46480" uid: a497b114-e949-4094-bf78-e1a366ba52fd spec: sourcePod: network-check-source-7bc5b6bf85-kcprj targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-17T17:59:21Z" message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.549213ms message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:20:21Z" - latency: 2.072017ms message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:19:21Z" - latency: 2.581992ms message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:18:21Z" - latency: 2.220569ms message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:17:21Z" - latency: 2.055419ms message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:16:21Z" - latency: 2.21064ms message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:15:21Z" - latency: 2.028237ms message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:14:21Z" - latency: 2.269383ms message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:13:21Z" - latency: 2.291965ms message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:12:21Z" - latency: 2.116116ms message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:11:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:52:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-140-to-network-check-target-ip-10-0-142-155 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-140.ec2.internal uid: 42a569a1-6c78-4304-9542-c8ec312e03f6 resourceVersion: "46479" uid: 3acb943a-6b8b-44c2-ab7a-7a2a35317483 spec: sourcePod: network-check-source-7bc5b6bf85-kcprj targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-17T17:59:21Z" message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.028624ms message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:20:21Z" - latency: 2.124599ms message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:19:21Z" - latency: 2.079873ms message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:18:21Z" - latency: 1.967877ms message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:17:21Z" - latency: 1.887837ms message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:16:21Z" - latency: 1.973389ms message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:15:21Z" - latency: 1.944686ms message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:14:21Z" - latency: 1.783068ms message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:13:21Z" - latency: 1.816099ms message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:12:21Z" - latency: 1.705455ms message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:11:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:52:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-140-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-140.ec2.internal uid: 42a569a1-6c78-4304-9542-c8ec312e03f6 resourceVersion: "48002" uid: 90ed0611-2e11-4c40-b47c-9dcae2cca73d spec: sourcePod: network-check-source-7bc5b6bf85-kcprj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-17T17:58:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 874.947µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:22:21Z" - latency: 1.681464ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:22:21Z" - latency: 855.556µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:21:21Z" - latency: 2.050678ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:21:21Z" - latency: 1.163269ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:20:21Z" - latency: 2.139688ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:20:21Z" - latency: 1.03326ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:19:21Z" - latency: 1.827899ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:19:21Z" - latency: 1.070401ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:18:21Z" - latency: 1.666408ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:18:21Z" kind: List metadata: resourceVersion: ""