apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:04:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-67-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-67.us-east-2.compute.internal uid: ded1b416-6207-48c3-88e9-c374a391c054 resourceVersion: "115255" uid: 7104179e-a9e8-4792-bed1-c1dc0f686f70 spec: sourcePod: network-check-source-6f78d59f99-zc968 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-04T01:11:07Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 988.214µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:46:07Z" - latency: 1.465527ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:45:07Z" - latency: 1.161914ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:44:07Z" - latency: 4.170342ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:43:07Z" - latency: 1.00138ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:42:07Z" - latency: 1.248259ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:41:07Z" - latency: 1.163136ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:40:07Z" - latency: 1.470114ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:39:07Z" - latency: 1.17544ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:38:07Z" - latency: 1.216507ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:37:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:04:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-67-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-67.us-east-2.compute.internal uid: ded1b416-6207-48c3-88e9-c374a391c054 resourceVersion: "123395" uid: cd25e03e-2974-4e82-82f2-e6cb7775df75 spec: sourcePod: network-check-source-6f78d59f99-zc968 targetEndpoint: a4c9203df9b0a4f4e95839bc0404c7e1-63c713fa30addae8.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T01:10:07Z" message: 'load-balancer-api-external: tcp connection to a4c9203df9b0a4f4e95839bc0404c7e1-63c713fa30addae8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.664543ms message: 'load-balancer-api-external: tcp connection to a4c9203df9b0a4f4e95839bc0404c7e1-63c713fa30addae8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:52:07Z" - latency: 6.94445ms message: 'load-balancer-api-external: resolved host name a4c9203df9b0a4f4e95839bc0404c7e1-63c713fa30addae8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:52:07Z" - latency: 4.771526ms message: 'load-balancer-api-external: tcp connection to a4c9203df9b0a4f4e95839bc0404c7e1-63c713fa30addae8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:51:07Z" - latency: 6.964366ms message: 'load-balancer-api-external: resolved host name a4c9203df9b0a4f4e95839bc0404c7e1-63c713fa30addae8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:51:07Z" - latency: 4.930396ms message: 'load-balancer-api-external: tcp connection to a4c9203df9b0a4f4e95839bc0404c7e1-63c713fa30addae8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:50:07Z" - latency: 7.09447ms message: 'load-balancer-api-external: resolved host name a4c9203df9b0a4f4e95839bc0404c7e1-63c713fa30addae8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:50:07Z" - latency: 4.761553ms message: 'load-balancer-api-external: tcp connection to a4c9203df9b0a4f4e95839bc0404c7e1-63c713fa30addae8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:49:07Z" - latency: 6.780308ms message: 'load-balancer-api-external: resolved host name a4c9203df9b0a4f4e95839bc0404c7e1-63c713fa30addae8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:49:07Z" - latency: 9.896103ms message: 'load-balancer-api-external: tcp connection to a4c9203df9b0a4f4e95839bc0404c7e1-63c713fa30addae8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:48:07Z" - latency: 7.001855ms message: 'load-balancer-api-external: resolved host name a4c9203df9b0a4f4e95839bc0404c7e1-63c713fa30addae8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:48:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:04:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-67-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-67.us-east-2.compute.internal uid: ded1b416-6207-48c3-88e9-c374a391c054 resourceVersion: "123396" uid: d268d728-176e-4a21-8847-ef1512e5ca0c spec: sourcePod: network-check-source-6f78d59f99-zc968 targetEndpoint: a4c9203df9b0a4f4e95839bc0404c7e1-63c713fa30addae8.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T01:10:07Z" message: 'load-balancer-api-internal: tcp connection to a4c9203df9b0a4f4e95839bc0404c7e1-63c713fa30addae8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.753522ms message: 'load-balancer-api-internal: tcp connection to a4c9203df9b0a4f4e95839bc0404c7e1-63c713fa30addae8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:52:07Z" - latency: 6.973641ms message: 'load-balancer-api-internal: resolved host name a4c9203df9b0a4f4e95839bc0404c7e1-63c713fa30addae8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:52:07Z" - latency: 4.804957ms message: 'load-balancer-api-internal: tcp connection to a4c9203df9b0a4f4e95839bc0404c7e1-63c713fa30addae8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:51:07Z" - latency: 6.877342ms message: 'load-balancer-api-internal: resolved host name a4c9203df9b0a4f4e95839bc0404c7e1-63c713fa30addae8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:51:07Z" - latency: 4.966596ms message: 'load-balancer-api-internal: tcp connection to a4c9203df9b0a4f4e95839bc0404c7e1-63c713fa30addae8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:50:07Z" - latency: 7.200183ms message: 'load-balancer-api-internal: resolved host name a4c9203df9b0a4f4e95839bc0404c7e1-63c713fa30addae8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:50:07Z" - latency: 4.741523ms message: 'load-balancer-api-internal: tcp connection to a4c9203df9b0a4f4e95839bc0404c7e1-63c713fa30addae8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:49:07Z" - latency: 6.718835ms message: 'load-balancer-api-internal: resolved host name a4c9203df9b0a4f4e95839bc0404c7e1-63c713fa30addae8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:49:07Z" - latency: 6.752168ms message: 'load-balancer-api-internal: tcp connection to a4c9203df9b0a4f4e95839bc0404c7e1-63c713fa30addae8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:48:07Z" - latency: 7.027161ms message: 'load-balancer-api-internal: resolved host name a4c9203df9b0a4f4e95839bc0404c7e1-63c713fa30addae8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:48:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:04:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-67-to-network-check-target-ip-10-0-132-67 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-67.us-east-2.compute.internal uid: ded1b416-6207-48c3-88e9-c374a391c054 resourceVersion: "115252" uid: a1fcfb58-46e3-4090-b16b-2332fe875b5b spec: sourcePod: network-check-source-6f78d59f99-zc968 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-04T01:11:07Z" message: 'network-check-target-ip-10-0-132-67: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.319937ms message: 'network-check-target-ip-10-0-132-67: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:46:07Z" - latency: 1.712788ms message: 'network-check-target-ip-10-0-132-67: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:45:07Z" - latency: 1.136971ms message: 'network-check-target-ip-10-0-132-67: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:44:07Z" - latency: 2.873253ms message: 'network-check-target-ip-10-0-132-67: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:43:07Z" - latency: 1.626853ms message: 'network-check-target-ip-10-0-132-67: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:42:07Z" - latency: 1.741141ms message: 'network-check-target-ip-10-0-132-67: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:41:07Z" - latency: 1.21441ms message: 'network-check-target-ip-10-0-132-67: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:40:07Z" - latency: 1.38226ms message: 'network-check-target-ip-10-0-132-67: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:39:07Z" - latency: 1.103238ms message: 'network-check-target-ip-10-0-132-67: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:38:07Z" - latency: 986.606µs message: 'network-check-target-ip-10-0-132-67: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:37:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:04:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-67-to-network-check-target-ip-10-0-136-96 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-67.us-east-2.compute.internal uid: ded1b416-6207-48c3-88e9-c374a391c054 resourceVersion: "115253" uid: efc83a1b-c08e-4e4f-bf79-06065104f323 spec: sourcePod: network-check-source-6f78d59f99-zc968 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-04T01:11:07Z" message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.235341ms message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:46:07Z" - latency: 2.455703ms message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:45:07Z" - latency: 2.397594ms message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:44:07Z" - latency: 11.524396ms message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:43:07Z" - latency: 2.200376ms message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:42:07Z" - latency: 2.23702ms message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:41:07Z" - latency: 2.121092ms message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:40:07Z" - latency: 2.423941ms message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:39:07Z" - latency: 2.281445ms message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:38:07Z" - latency: 2.357404ms message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:37:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:04:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-67-to-network-check-target-ip-10-0-140-186 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-67.us-east-2.compute.internal uid: ded1b416-6207-48c3-88e9-c374a391c054 resourceVersion: "115276" uid: 81c1ddbc-20f3-407f-8636-c96dee87ac44 spec: sourcePod: network-check-source-6f78d59f99-zc968 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-04T01:11:09Z" message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.151458ms message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:46:09Z" - latency: 2.171917ms message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:45:09Z" - latency: 2.113104ms message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:44:09Z" - latency: 1.556955ms message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:43:09Z" - latency: 1.763726ms message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:42:09Z" - latency: 873.66µs message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:41:09Z" - latency: 1.983401ms message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:40:09Z" - latency: 2.205275ms message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:39:09Z" - latency: 2.16096ms message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:38:09Z" - latency: 860.049µs message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:37:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:04:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-67-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-67.us-east-2.compute.internal uid: ded1b416-6207-48c3-88e9-c374a391c054 resourceVersion: "123393" uid: 69bac626-cfd1-49a4-9ec5-550daf290235 spec: sourcePod: network-check-source-6f78d59f99-zc968 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-04T01:10:07Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 763.202µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:52:07Z" - latency: 1.728807ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T01:52:07Z" - latency: 987.43µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:51:07Z" - latency: 1.912554ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T01:51:07Z" - latency: 892.535µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:50:07Z" - latency: 1.940612ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T01:50:07Z" - latency: 1.918024ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:49:07Z" - latency: 1.861367ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T01:49:07Z" - latency: 891.368µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:48:07Z" - latency: 1.903415ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T01:48:07Z" kind: List metadata: resourceVersion: ""