apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:28:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-28-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-28.ec2.internal uid: f6936817-6e8b-4264-aa8a-0cc0b51bd244 resourceVersion: "54624" uid: b32f3824-63c1-4a21-aa1b-a21ad265e35b spec: sourcePod: network-check-source-869dcfcdcd-6c5jb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T18:35:40Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.034383ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:03:40Z" - latency: 845.84µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:02:40Z" - latency: 1.038646ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:01:40Z" - latency: 731.604µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:00:40Z" - latency: 1.59715ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:59:40Z" - latency: 820.848µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:58:40Z" - latency: 1.074488ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:57:40Z" - latency: 856.625µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:56:40Z" - latency: 911.227µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:55:40Z" - latency: 1.639111ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:54:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:28:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-28-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-28.ec2.internal uid: f6936817-6e8b-4264-aa8a-0cc0b51bd244 resourceVersion: "55693" uid: 8b4d1d78-ba10-41ae-9cb4-d8f18eef79df spec: sourcePod: network-check-source-869dcfcdcd-6c5jb targetEndpoint: aa306b164f3ac47c4a74f10d17b31c9f-6fb5f5914736c555.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T18:34:40Z" message: 'load-balancer-api-external: tcp connection to aa306b164f3ac47c4a74f10d17b31c9f-6fb5f5914736c555.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.508706ms message: 'load-balancer-api-external: tcp connection to aa306b164f3ac47c4a74f10d17b31c9f-6fb5f5914736c555.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:04:40Z" - latency: 7.545276ms message: 'load-balancer-api-external: resolved host name aa306b164f3ac47c4a74f10d17b31c9f-6fb5f5914736c555.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T19:04:40Z" - latency: 4.236489ms message: 'load-balancer-api-external: tcp connection to aa306b164f3ac47c4a74f10d17b31c9f-6fb5f5914736c555.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:03:40Z" - latency: 8.48827ms message: 'load-balancer-api-external: resolved host name aa306b164f3ac47c4a74f10d17b31c9f-6fb5f5914736c555.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T19:03:40Z" - latency: 3.889027ms message: 'load-balancer-api-external: tcp connection to aa306b164f3ac47c4a74f10d17b31c9f-6fb5f5914736c555.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:02:40Z" - latency: 7.941231ms message: 'load-balancer-api-external: resolved host name aa306b164f3ac47c4a74f10d17b31c9f-6fb5f5914736c555.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T19:02:40Z" - latency: 5.379633ms message: 'load-balancer-api-external: tcp connection to aa306b164f3ac47c4a74f10d17b31c9f-6fb5f5914736c555.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:01:40Z" - latency: 7.555093ms message: 'load-balancer-api-external: resolved host name aa306b164f3ac47c4a74f10d17b31c9f-6fb5f5914736c555.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T19:01:40Z" - latency: 5.785219ms message: 'load-balancer-api-external: tcp connection to aa306b164f3ac47c4a74f10d17b31c9f-6fb5f5914736c555.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:00:40Z" - latency: 7.103526ms message: 'load-balancer-api-external: resolved host name aa306b164f3ac47c4a74f10d17b31c9f-6fb5f5914736c555.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T19:00:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:28:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-28-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-28.ec2.internal uid: f6936817-6e8b-4264-aa8a-0cc0b51bd244 resourceVersion: "55694" uid: 6abe174a-6286-475e-8553-dfebe9fb4703 spec: sourcePod: network-check-source-869dcfcdcd-6c5jb targetEndpoint: aa306b164f3ac47c4a74f10d17b31c9f-6fb5f5914736c555.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T18:34:40Z" message: 'load-balancer-api-internal: tcp connection to aa306b164f3ac47c4a74f10d17b31c9f-6fb5f5914736c555.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.490803ms message: 'load-balancer-api-internal: tcp connection to aa306b164f3ac47c4a74f10d17b31c9f-6fb5f5914736c555.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:04:40Z" - latency: 7.52184ms message: 'load-balancer-api-internal: resolved host name aa306b164f3ac47c4a74f10d17b31c9f-6fb5f5914736c555.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T19:04:40Z" - latency: 4.223789ms message: 'load-balancer-api-internal: tcp connection to aa306b164f3ac47c4a74f10d17b31c9f-6fb5f5914736c555.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:03:40Z" - latency: 8.548135ms message: 'load-balancer-api-internal: resolved host name aa306b164f3ac47c4a74f10d17b31c9f-6fb5f5914736c555.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T19:03:40Z" - latency: 4.009748ms message: 'load-balancer-api-internal: tcp connection to aa306b164f3ac47c4a74f10d17b31c9f-6fb5f5914736c555.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:02:40Z" - latency: 7.971426ms message: 'load-balancer-api-internal: resolved host name aa306b164f3ac47c4a74f10d17b31c9f-6fb5f5914736c555.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T19:02:40Z" - latency: 5.367071ms message: 'load-balancer-api-internal: tcp connection to aa306b164f3ac47c4a74f10d17b31c9f-6fb5f5914736c555.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:01:40Z" - latency: 7.584901ms message: 'load-balancer-api-internal: resolved host name aa306b164f3ac47c4a74f10d17b31c9f-6fb5f5914736c555.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T19:01:40Z" - latency: 5.743297ms message: 'load-balancer-api-internal: tcp connection to aa306b164f3ac47c4a74f10d17b31c9f-6fb5f5914736c555.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:00:40Z" - latency: 7.12352ms message: 'load-balancer-api-internal: resolved host name aa306b164f3ac47c4a74f10d17b31c9f-6fb5f5914736c555.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T19:00:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:28:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-28-to-network-check-target-ip-10-0-135-28 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-28.ec2.internal uid: f6936817-6e8b-4264-aa8a-0cc0b51bd244 resourceVersion: "54620" uid: 5ce08e9d-6689-4b1e-ae18-74eb71a4f257 spec: sourcePod: network-check-source-869dcfcdcd-6c5jb targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T18:35:40Z" message: 'network-check-target-ip-10-0-135-28: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 830.919µs message: 'network-check-target-ip-10-0-135-28: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:03:40Z" - latency: 1.09639ms message: 'network-check-target-ip-10-0-135-28: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:02:40Z" - latency: 1.131651ms message: 'network-check-target-ip-10-0-135-28: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:01:40Z" - latency: 989.017µs message: 'network-check-target-ip-10-0-135-28: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:00:40Z" - latency: 761.792µs message: 'network-check-target-ip-10-0-135-28: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:59:40Z" - latency: 1.43252ms message: 'network-check-target-ip-10-0-135-28: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:58:40Z" - latency: 778.047µs message: 'network-check-target-ip-10-0-135-28: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:57:40Z" - latency: 797.319µs message: 'network-check-target-ip-10-0-135-28: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:56:40Z" - latency: 816.643µs message: 'network-check-target-ip-10-0-135-28: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:55:40Z" - latency: 1.456483ms message: 'network-check-target-ip-10-0-135-28: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:54:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:28:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-28-to-network-check-target-ip-10-0-138-253 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-28.ec2.internal uid: f6936817-6e8b-4264-aa8a-0cc0b51bd244 resourceVersion: "54621" uid: 8ab93cb6-d93f-45bc-8245-fca43e4df1a8 spec: sourcePod: network-check-source-869dcfcdcd-6c5jb targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T18:35:40Z" message: 'network-check-target-ip-10-0-138-253: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.395377ms message: 'network-check-target-ip-10-0-138-253: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:03:40Z" - latency: 2.236426ms message: 'network-check-target-ip-10-0-138-253: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:02:40Z" - latency: 2.312938ms message: 'network-check-target-ip-10-0-138-253: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:01:40Z" - latency: 2.107308ms message: 'network-check-target-ip-10-0-138-253: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:00:40Z" - latency: 1.753881ms message: 'network-check-target-ip-10-0-138-253: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:59:40Z" - latency: 2.192964ms message: 'network-check-target-ip-10-0-138-253: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:58:40Z" - latency: 2.366614ms message: 'network-check-target-ip-10-0-138-253: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:57:40Z" - latency: 1.988483ms message: 'network-check-target-ip-10-0-138-253: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:56:40Z" - latency: 1.924487ms message: 'network-check-target-ip-10-0-138-253: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:55:40Z" - latency: 1.992293ms message: 'network-check-target-ip-10-0-138-253: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:54:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:28:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-28-to-network-check-target-ip-10-0-141-101 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-28.ec2.internal uid: f6936817-6e8b-4264-aa8a-0cc0b51bd244 resourceVersion: "54622" uid: 7a75fc66-7586-4d71-8dff-49bcfe485a9e spec: sourcePod: network-check-source-869dcfcdcd-6c5jb targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T18:35:40Z" message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.835637ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:03:40Z" - latency: 2.333774ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:02:40Z" - latency: 2.436423ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:01:40Z" - latency: 2.503781ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:00:40Z" - latency: 2.105033ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:59:40Z" - latency: 2.248146ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:58:40Z" - latency: 2.534265ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:57:40Z" - latency: 2.446086ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:56:40Z" - latency: 2.328013ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:55:40Z" - latency: 2.654832ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:54:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:28:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-28-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-28.ec2.internal uid: f6936817-6e8b-4264-aa8a-0cc0b51bd244 resourceVersion: "55692" uid: eaf77633-dd31-47bf-bb24-3a3ee6a65d70 spec: sourcePod: network-check-source-869dcfcdcd-6c5jb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T18:34:40Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 811.743µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:04:40Z" - latency: 1.726032ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T19:04:40Z" - latency: 1.046542ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:03:40Z" - latency: 1.841084ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T19:03:40Z" - latency: 756.156µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:02:40Z" - latency: 1.650929ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T19:02:40Z" - latency: 996.652µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:01:40Z" - latency: 1.530801ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T19:01:40Z" - latency: 1.018349ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:00:40Z" - latency: 1.903849ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T19:00:40Z" kind: List metadata: resourceVersion: ""