apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T12:52:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-1-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-1.ec2.internal uid: b131da3e-dd67-47a9-81a3-c44bf931238a resourceVersion: "53834" uid: fdf45167-d108-45af-9fd9-79e4d05aec5e spec: sourcePod: network-check-source-685456655f-nmtv2 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-09T12:59:36Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.031129ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:20:36Z" - latency: 942.219µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:19:36Z" - latency: 1.197668ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:18:36Z" - latency: 1.104443ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:17:36Z" - latency: 1.28656ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:16:36Z" - latency: 1.010146ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:15:36Z" - latency: 1.236193ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:14:36Z" - latency: 1.135582ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:13:36Z" - latency: 931.333µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:12:36Z" - latency: 1.582334ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:11:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T12:52:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-1-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-1.ec2.internal uid: b131da3e-dd67-47a9-81a3-c44bf931238a resourceVersion: "55376" uid: 10e54357-2492-4217-a766-3366dc14085e spec: sourcePod: network-check-source-685456655f-nmtv2 targetEndpoint: a2bb5dbd922234d14bed52a5b2ddcf5e-405781b06cbf71a9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T12:58:36Z" message: 'load-balancer-api-external: tcp connection to a2bb5dbd922234d14bed52a5b2ddcf5e-405781b06cbf71a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.425156ms message: 'load-balancer-api-external: tcp connection to a2bb5dbd922234d14bed52a5b2ddcf5e-405781b06cbf71a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:22:36Z" - latency: 9.075735ms message: 'load-balancer-api-external: resolved host name a2bb5dbd922234d14bed52a5b2ddcf5e-405781b06cbf71a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T13:22:36Z" - latency: 3.802584ms message: 'load-balancer-api-external: tcp connection to a2bb5dbd922234d14bed52a5b2ddcf5e-405781b06cbf71a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:21:36Z" - latency: 11.422872ms message: 'load-balancer-api-external: resolved host name a2bb5dbd922234d14bed52a5b2ddcf5e-405781b06cbf71a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T13:21:36Z" - latency: 5.696853ms message: 'load-balancer-api-external: tcp connection to a2bb5dbd922234d14bed52a5b2ddcf5e-405781b06cbf71a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:20:36Z" - latency: 8.715831ms message: 'load-balancer-api-external: resolved host name a2bb5dbd922234d14bed52a5b2ddcf5e-405781b06cbf71a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T13:20:36Z" - latency: 5.106323ms message: 'load-balancer-api-external: tcp connection to a2bb5dbd922234d14bed52a5b2ddcf5e-405781b06cbf71a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:19:36Z" - latency: 8.577547ms message: 'load-balancer-api-external: resolved host name a2bb5dbd922234d14bed52a5b2ddcf5e-405781b06cbf71a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T13:19:36Z" - latency: 5.108722ms message: 'load-balancer-api-external: tcp connection to a2bb5dbd922234d14bed52a5b2ddcf5e-405781b06cbf71a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:18:36Z" - latency: 8.871962ms message: 'load-balancer-api-external: resolved host name a2bb5dbd922234d14bed52a5b2ddcf5e-405781b06cbf71a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T13:18:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T12:52:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-1-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-1.ec2.internal uid: b131da3e-dd67-47a9-81a3-c44bf931238a resourceVersion: "55377" uid: 7155faa8-415f-4eb1-a10f-fef6139385d4 spec: sourcePod: network-check-source-685456655f-nmtv2 targetEndpoint: a2bb5dbd922234d14bed52a5b2ddcf5e-405781b06cbf71a9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T12:58:36Z" message: 'load-balancer-api-internal: tcp connection to a2bb5dbd922234d14bed52a5b2ddcf5e-405781b06cbf71a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.199753ms message: 'load-balancer-api-internal: tcp connection to a2bb5dbd922234d14bed52a5b2ddcf5e-405781b06cbf71a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:22:36Z" - latency: 9.009475ms message: 'load-balancer-api-internal: resolved host name a2bb5dbd922234d14bed52a5b2ddcf5e-405781b06cbf71a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T13:22:36Z" - latency: 3.771405ms message: 'load-balancer-api-internal: tcp connection to a2bb5dbd922234d14bed52a5b2ddcf5e-405781b06cbf71a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:21:36Z" - latency: 11.334803ms message: 'load-balancer-api-internal: resolved host name a2bb5dbd922234d14bed52a5b2ddcf5e-405781b06cbf71a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T13:21:36Z" - latency: 5.718308ms message: 'load-balancer-api-internal: tcp connection to a2bb5dbd922234d14bed52a5b2ddcf5e-405781b06cbf71a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:20:36Z" - latency: 8.651201ms message: 'load-balancer-api-internal: resolved host name a2bb5dbd922234d14bed52a5b2ddcf5e-405781b06cbf71a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T13:20:36Z" - latency: 5.114172ms message: 'load-balancer-api-internal: tcp connection to a2bb5dbd922234d14bed52a5b2ddcf5e-405781b06cbf71a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:19:36Z" - latency: 8.654246ms message: 'load-balancer-api-internal: resolved host name a2bb5dbd922234d14bed52a5b2ddcf5e-405781b06cbf71a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T13:19:36Z" - latency: 5.122755ms message: 'load-balancer-api-internal: tcp connection to a2bb5dbd922234d14bed52a5b2ddcf5e-405781b06cbf71a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:18:36Z" - latency: 8.8485ms message: 'load-balancer-api-internal: resolved host name a2bb5dbd922234d14bed52a5b2ddcf5e-405781b06cbf71a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T13:18:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T12:52:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-1-to-network-check-target-ip-10-0-132-160 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-1.ec2.internal uid: b131da3e-dd67-47a9-81a3-c44bf931238a resourceVersion: "53833" uid: edbfa198-b2d7-485e-9f3b-50099e640e8d spec: sourcePod: network-check-source-685456655f-nmtv2 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-09T12:59:36Z" message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.475181ms message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:20:36Z" - latency: 2.234971ms message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:19:36Z" - latency: 2.401379ms message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:18:36Z" - latency: 2.622743ms message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:17:36Z" - latency: 2.613578ms message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:16:36Z" - latency: 2.735285ms message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:15:36Z" - latency: 2.418451ms message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:14:36Z" - latency: 2.484861ms message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:13:36Z" - latency: 3.397002ms message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:12:36Z" - latency: 2.403318ms message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:11:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T12:52:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-1-to-network-check-target-ip-10-0-137-1 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-1.ec2.internal uid: b131da3e-dd67-47a9-81a3-c44bf931238a resourceVersion: "53831" uid: c05e2126-2d9d-45b1-bafc-2b82c7287658 spec: sourcePod: network-check-source-685456655f-nmtv2 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-09T12:59:36Z" message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.007844ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:20:36Z" - latency: 1.077868ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:19:36Z" - latency: 1.360711ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:18:36Z" - latency: 1.59639ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:17:36Z" - latency: 1.701067ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:16:36Z" - latency: 1.664785ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:15:36Z" - latency: 1.293873ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:14:36Z" - latency: 1.939587ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:13:36Z" - latency: 920.94µs message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:12:36Z" - latency: 1.001231ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:11:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T12:52:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-1-to-network-check-target-ip-10-0-140-133 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-1.ec2.internal uid: b131da3e-dd67-47a9-81a3-c44bf931238a resourceVersion: "53832" uid: 82eb6a9d-b5ca-4b73-b30e-e055fe8a7a11 spec: sourcePod: network-check-source-685456655f-nmtv2 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-09T12:59:36Z" message: 'network-check-target-ip-10-0-140-133: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.463857ms message: 'network-check-target-ip-10-0-140-133: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:20:36Z" - latency: 2.140345ms message: 'network-check-target-ip-10-0-140-133: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:19:36Z" - latency: 3.277748ms message: 'network-check-target-ip-10-0-140-133: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:18:36Z" - latency: 2.719824ms message: 'network-check-target-ip-10-0-140-133: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:17:36Z" - latency: 2.575461ms message: 'network-check-target-ip-10-0-140-133: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:16:36Z" - latency: 3.057468ms message: 'network-check-target-ip-10-0-140-133: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:15:36Z" - latency: 2.951855ms message: 'network-check-target-ip-10-0-140-133: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:14:36Z" - latency: 2.238805ms message: 'network-check-target-ip-10-0-140-133: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:13:36Z" - latency: 2.492424ms message: 'network-check-target-ip-10-0-140-133: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:12:36Z" - latency: 2.738503ms message: 'network-check-target-ip-10-0-140-133: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:11:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T12:52:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-1-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-1.ec2.internal uid: b131da3e-dd67-47a9-81a3-c44bf931238a resourceVersion: "55375" uid: c357ab75-bea7-4bb2-afb1-7f5c23855832 spec: sourcePod: network-check-source-685456655f-nmtv2 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-09T12:58:36Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 970.425µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:22:36Z" - latency: 1.877126ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T13:22:36Z" - latency: 948.815µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:21:36Z" - latency: 2.298737ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T13:21:36Z" - latency: 1.377415ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:20:36Z" - latency: 1.794488ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T13:20:36Z" - latency: 891.114µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:19:36Z" - latency: 1.919081ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T13:19:36Z" - latency: 851.604µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:18:36Z" - latency: 1.852159ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T13:18:36Z" kind: List metadata: resourceVersion: ""