apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:02:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-23-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-23.ec2.internal uid: 0d80584e-0cf5-4d4a-be3b-b478eb66b4fb resourceVersion: "50055" uid: a76503d0-534e-4122-8ade-63bc01a02eee spec: sourcePod: network-check-source-7bc5b6bf85-7dgrt targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-20T10:09:24Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 909.473µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:19:24Z" - latency: 888.434µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:18:24Z" - latency: 845.149µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:17:24Z" - latency: 849.887µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:16:24Z" - latency: 839.138µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:15:24Z" - latency: 1.094614ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:14:24Z" - latency: 781.303µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:13:24Z" - latency: 795.508µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:12:24Z" - latency: 681.01µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:11:24Z" - latency: 794.643µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:10:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:02:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-23-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-23.ec2.internal uid: 0d80584e-0cf5-4d4a-be3b-b478eb66b4fb resourceVersion: "47314" uid: 9b66d22d-4450-4ff6-b2b9-d43a3e427a4a spec: sourcePod: network-check-source-7bc5b6bf85-7dgrt targetEndpoint: ac85140e7a1584603a10a3dbda8d1324-e18df6e95e85ebe3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T10:08:24Z" message: 'load-balancer-api-external: tcp connection to ac85140e7a1584603a10a3dbda8d1324-e18df6e95e85ebe3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.207801ms message: 'load-balancer-api-external: tcp connection to ac85140e7a1584603a10a3dbda8d1324-e18df6e95e85ebe3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:14:24Z" - latency: 19.661136ms message: 'load-balancer-api-external: resolved host name ac85140e7a1584603a10a3dbda8d1324-e18df6e95e85ebe3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:14:24Z" - latency: 4.30868ms message: 'load-balancer-api-external: tcp connection to ac85140e7a1584603a10a3dbda8d1324-e18df6e95e85ebe3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:13:24Z" - latency: 13.747337ms message: 'load-balancer-api-external: resolved host name ac85140e7a1584603a10a3dbda8d1324-e18df6e95e85ebe3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:13:24Z" - latency: 5.816343ms message: 'load-balancer-api-external: tcp connection to ac85140e7a1584603a10a3dbda8d1324-e18df6e95e85ebe3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:12:24Z" - latency: 7.211632ms message: 'load-balancer-api-external: resolved host name ac85140e7a1584603a10a3dbda8d1324-e18df6e95e85ebe3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:12:24Z" - latency: 3.411358ms message: 'load-balancer-api-external: tcp connection to ac85140e7a1584603a10a3dbda8d1324-e18df6e95e85ebe3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:11:24Z" - latency: 10.293397ms message: 'load-balancer-api-external: resolved host name ac85140e7a1584603a10a3dbda8d1324-e18df6e95e85ebe3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:11:24Z" - latency: 5.284673ms message: 'load-balancer-api-external: tcp connection to ac85140e7a1584603a10a3dbda8d1324-e18df6e95e85ebe3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:10:24Z" - latency: 11.786306ms message: 'load-balancer-api-external: resolved host name ac85140e7a1584603a10a3dbda8d1324-e18df6e95e85ebe3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:10:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:02:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-23-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-23.ec2.internal uid: 0d80584e-0cf5-4d4a-be3b-b478eb66b4fb resourceVersion: "47313" uid: 9de2394b-7216-4bea-901b-f84c2e7ddc8f spec: sourcePod: network-check-source-7bc5b6bf85-7dgrt targetEndpoint: ac85140e7a1584603a10a3dbda8d1324-e18df6e95e85ebe3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T10:08:24Z" message: 'load-balancer-api-internal: tcp connection to ac85140e7a1584603a10a3dbda8d1324-e18df6e95e85ebe3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.155376ms message: 'load-balancer-api-internal: tcp connection to ac85140e7a1584603a10a3dbda8d1324-e18df6e95e85ebe3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:14:24Z" - latency: 19.701907ms message: 'load-balancer-api-internal: resolved host name ac85140e7a1584603a10a3dbda8d1324-e18df6e95e85ebe3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:14:24Z" - latency: 4.323898ms message: 'load-balancer-api-internal: tcp connection to ac85140e7a1584603a10a3dbda8d1324-e18df6e95e85ebe3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:13:24Z" - latency: 13.811913ms message: 'load-balancer-api-internal: resolved host name ac85140e7a1584603a10a3dbda8d1324-e18df6e95e85ebe3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:13:24Z" - latency: 5.873849ms message: 'load-balancer-api-internal: tcp connection to ac85140e7a1584603a10a3dbda8d1324-e18df6e95e85ebe3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:12:24Z" - latency: 7.234822ms message: 'load-balancer-api-internal: resolved host name ac85140e7a1584603a10a3dbda8d1324-e18df6e95e85ebe3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:12:24Z" - latency: 14.040369ms message: 'load-balancer-api-internal: tcp connection to ac85140e7a1584603a10a3dbda8d1324-e18df6e95e85ebe3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:11:24Z" - latency: 10.364682ms message: 'load-balancer-api-internal: resolved host name ac85140e7a1584603a10a3dbda8d1324-e18df6e95e85ebe3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:11:24Z" - latency: 5.75084ms message: 'load-balancer-api-internal: tcp connection to ac85140e7a1584603a10a3dbda8d1324-e18df6e95e85ebe3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:10:24Z" - latency: 11.884362ms message: 'load-balancer-api-internal: resolved host name ac85140e7a1584603a10a3dbda8d1324-e18df6e95e85ebe3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:10:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:02:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-23-to-network-check-target-ip-10-0-132-39 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-23.ec2.internal uid: 0d80584e-0cf5-4d4a-be3b-b478eb66b4fb resourceVersion: "50054" uid: 99b1ddb4-8790-418a-a76d-7e9c9ae1fb52 spec: sourcePod: network-check-source-7bc5b6bf85-7dgrt targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-20T10:09:24Z" message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.313764ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:19:24Z" - latency: 2.372945ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:18:24Z" - latency: 2.238048ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:17:24Z" - latency: 2.192678ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:16:24Z" - latency: 1.839309ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:15:24Z" - latency: 2.113831ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:14:24Z" - latency: 2.364046ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:13:24Z" - latency: 2.509616ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:12:24Z" - latency: 1.896297ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:11:24Z" - latency: 2.10535ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:10:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:02:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-23-to-network-check-target-ip-10-0-134-80 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-23.ec2.internal uid: 0d80584e-0cf5-4d4a-be3b-b478eb66b4fb resourceVersion: "50052" uid: 4ad1e26b-0428-4128-8c91-dc04e037a290 spec: sourcePod: network-check-source-7bc5b6bf85-7dgrt targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-20T10:09:24Z" message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.875082ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:19:24Z" - latency: 1.748875ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:18:24Z" - latency: 1.852034ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:17:24Z" - latency: 2.15341ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:16:24Z" - latency: 2.120205ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:15:24Z" - latency: 1.979973ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:14:24Z" - latency: 1.998499ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:13:24Z" - latency: 2.227091ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:12:24Z" - latency: 2.001133ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:11:24Z" - latency: 2.279939ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:10:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:02:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-23-to-network-check-target-ip-10-0-142-23 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-23.ec2.internal uid: 0d80584e-0cf5-4d4a-be3b-b478eb66b4fb resourceVersion: "50053" uid: 905997be-f59f-45a1-9e2b-2673efa1c3ed spec: sourcePod: network-check-source-7bc5b6bf85-7dgrt targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-20T10:09:24Z" message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.016822ms message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:19:24Z" - latency: 791.509µs message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:18:24Z" - latency: 1.066396ms message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:17:24Z" - latency: 1.227198ms message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:16:24Z" - latency: 829.991µs message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:15:24Z" - latency: 751.272µs message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:14:24Z" - latency: 808.462µs message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:13:24Z" - latency: 756.68µs message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:12:24Z" - latency: 678.193µs message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:11:24Z" - latency: 1.137212ms message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:10:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:02:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-23-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-23.ec2.internal uid: 0d80584e-0cf5-4d4a-be3b-b478eb66b4fb resourceVersion: "47312" uid: 57e14cdd-89f3-4d36-9664-3447f73b4ff3 spec: sourcePod: network-check-source-7bc5b6bf85-7dgrt targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-20T10:08:24Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 762.349µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:14:24Z" - latency: 1.590239ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T11:14:24Z" - latency: 735.917µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:13:24Z" - latency: 1.65685ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T11:13:24Z" - latency: 918.714µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:12:24Z" - latency: 1.714648ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T11:12:24Z" - latency: 906.598µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:11:24Z" - latency: 1.628072ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T11:11:24Z" - latency: 1.073765ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:10:24Z" - latency: 1.506459ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T11:10:24Z" kind: List metadata: resourceVersion: ""