apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:51:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-147-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-147.us-west-1.compute.internal uid: ea720a72-0da2-4502-9a49-c756fea25d5e resourceVersion: "101157" uid: 330927d6-1f8b-4d73-9588-82a499b14540 spec: sourcePod: network-check-source-6f78d59f99-t9z6m targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T21:58:28Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.256444ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:54:27Z" - latency: 1.36007ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:53:27Z" - latency: 1.378408ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:27Z" - latency: 1.074018ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:51:27Z" - latency: 1.554164ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:50:27Z" - latency: 852.547µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:49:27Z" - latency: 1.319392ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:48:27Z" - latency: 824.816µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:47:27Z" - latency: 1.142987ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:46:27Z" - latency: 1.366641ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:45:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:51:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-147-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-147.us-west-1.compute.internal uid: ea720a72-0da2-4502-9a49-c756fea25d5e resourceVersion: "99121" uid: 1d73de58-b988-44e6-9d08-c7355eb36245 spec: sourcePod: network-check-source-6f78d59f99-t9z6m targetEndpoint: aa7caa7bfd2874950af3c2a870e3e248-6e00b72b7f2ae867.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T21:57:28Z" message: 'load-balancer-api-external: tcp connection to aa7caa7bfd2874950af3c2a870e3e248-6e00b72b7f2ae867.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.159181ms message: 'load-balancer-api-external: tcp connection to aa7caa7bfd2874950af3c2a870e3e248-6e00b72b7f2ae867.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:51:27Z" - latency: 6.227857ms message: 'load-balancer-api-external: resolved host name aa7caa7bfd2874950af3c2a870e3e248-6e00b72b7f2ae867.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:51:27Z" - latency: 54.720946ms message: 'load-balancer-api-external: tcp connection to aa7caa7bfd2874950af3c2a870e3e248-6e00b72b7f2ae867.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:50:27Z" - latency: 6.442606ms message: 'load-balancer-api-external: resolved host name aa7caa7bfd2874950af3c2a870e3e248-6e00b72b7f2ae867.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:50:27Z" - latency: 54.451228ms message: 'load-balancer-api-external: tcp connection to aa7caa7bfd2874950af3c2a870e3e248-6e00b72b7f2ae867.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:49:27Z" - latency: 6.704457ms message: 'load-balancer-api-external: resolved host name aa7caa7bfd2874950af3c2a870e3e248-6e00b72b7f2ae867.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:49:27Z" - latency: 54.336972ms message: 'load-balancer-api-external: tcp connection to aa7caa7bfd2874950af3c2a870e3e248-6e00b72b7f2ae867.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:48:27Z" - latency: 13.087562ms message: 'load-balancer-api-external: resolved host name aa7caa7bfd2874950af3c2a870e3e248-6e00b72b7f2ae867.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:48:27Z" - latency: 55.241121ms message: 'load-balancer-api-external: tcp connection to aa7caa7bfd2874950af3c2a870e3e248-6e00b72b7f2ae867.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:47:27Z" - latency: 6.953769ms message: 'load-balancer-api-external: resolved host name aa7caa7bfd2874950af3c2a870e3e248-6e00b72b7f2ae867.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:47:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:51:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-147-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-147.us-west-1.compute.internal uid: ea720a72-0da2-4502-9a49-c756fea25d5e resourceVersion: "99122" uid: 94a57da5-707d-45da-9038-2905e605d7d1 spec: sourcePod: network-check-source-6f78d59f99-t9z6m targetEndpoint: aa7caa7bfd2874950af3c2a870e3e248-6e00b72b7f2ae867.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T21:57:28Z" message: 'load-balancer-api-internal: tcp connection to aa7caa7bfd2874950af3c2a870e3e248-6e00b72b7f2ae867.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 59.497617ms message: 'load-balancer-api-internal: tcp connection to aa7caa7bfd2874950af3c2a870e3e248-6e00b72b7f2ae867.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:51:27Z" - latency: 6.28939ms message: 'load-balancer-api-internal: resolved host name aa7caa7bfd2874950af3c2a870e3e248-6e00b72b7f2ae867.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:51:27Z" - latency: 55.756365ms message: 'load-balancer-api-internal: tcp connection to aa7caa7bfd2874950af3c2a870e3e248-6e00b72b7f2ae867.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:50:27Z" - latency: 6.515387ms message: 'load-balancer-api-internal: resolved host name aa7caa7bfd2874950af3c2a870e3e248-6e00b72b7f2ae867.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:50:27Z" - latency: 56.603351ms message: 'load-balancer-api-internal: tcp connection to aa7caa7bfd2874950af3c2a870e3e248-6e00b72b7f2ae867.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:49:27Z" - latency: 6.758981ms message: 'load-balancer-api-internal: resolved host name aa7caa7bfd2874950af3c2a870e3e248-6e00b72b7f2ae867.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:49:27Z" - latency: 53.495204ms message: 'load-balancer-api-internal: tcp connection to aa7caa7bfd2874950af3c2a870e3e248-6e00b72b7f2ae867.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:48:27Z" - latency: 13.217549ms message: 'load-balancer-api-internal: resolved host name aa7caa7bfd2874950af3c2a870e3e248-6e00b72b7f2ae867.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:48:27Z" - latency: 55.66625ms message: 'load-balancer-api-internal: tcp connection to aa7caa7bfd2874950af3c2a870e3e248-6e00b72b7f2ae867.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:47:27Z" - latency: 7.037794ms message: 'load-balancer-api-internal: resolved host name aa7caa7bfd2874950af3c2a870e3e248-6e00b72b7f2ae867.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:47:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:51:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-147-to-network-check-target-ip-10-0-135-59 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-147.us-west-1.compute.internal uid: ea720a72-0da2-4502-9a49-c756fea25d5e resourceVersion: "101154" uid: 17c3c0a4-1fa3-4325-ac43-970d5d60a227 spec: sourcePod: network-check-source-6f78d59f99-t9z6m targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:58:27Z" message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.826528ms message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:54:27Z" - latency: 2.317377ms message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:53:27Z" - latency: 2.268221ms message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:27Z" - latency: 2.416305ms message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:51:27Z" - latency: 2.426122ms message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:50:27Z" - latency: 2.059276ms message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:49:27Z" - latency: 2.003024ms message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:48:27Z" - latency: 1.954025ms message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:47:27Z" - latency: 1.60578ms message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:46:27Z" - latency: 2.404153ms message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:45:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:51:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-147-to-network-check-target-ip-10-0-137-81 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-147.us-west-1.compute.internal uid: ea720a72-0da2-4502-9a49-c756fea25d5e resourceVersion: "101155" uid: 8fa6909c-9bd1-43cf-925a-411e7a8aada8 spec: sourcePod: network-check-source-6f78d59f99-t9z6m targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:58:27Z" message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.424831ms message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:54:27Z" - latency: 2.449104ms message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:53:27Z" - latency: 2.564772ms message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:27Z" - latency: 2.145741ms message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:51:27Z" - latency: 2.474157ms message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:50:27Z" - latency: 2.297547ms message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:49:27Z" - latency: 2.399844ms message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:48:27Z" - latency: 1.979353ms message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:47:27Z" - latency: 2.031003ms message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:46:27Z" - latency: 2.295663ms message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:45:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:51:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-147-to-network-check-target-ip-10-0-141-147 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-147.us-west-1.compute.internal uid: ea720a72-0da2-4502-9a49-c756fea25d5e resourceVersion: "101153" uid: ad7ddca6-0a48-43bd-a2c1-8ba80020f098 spec: sourcePod: network-check-source-6f78d59f99-t9z6m targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:58:27Z" message: 'network-check-target-ip-10-0-141-147: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.272311ms message: 'network-check-target-ip-10-0-141-147: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:54:27Z" - latency: 1.179285ms message: 'network-check-target-ip-10-0-141-147: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:53:27Z" - latency: 1.181407ms message: 'network-check-target-ip-10-0-141-147: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:27Z" - latency: 959.247µs message: 'network-check-target-ip-10-0-141-147: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:51:27Z" - latency: 1.524799ms message: 'network-check-target-ip-10-0-141-147: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:50:27Z" - latency: 1.908922ms message: 'network-check-target-ip-10-0-141-147: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:49:27Z" - latency: 1.000533ms message: 'network-check-target-ip-10-0-141-147: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:48:27Z" - latency: 967.814µs message: 'network-check-target-ip-10-0-141-147: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:47:27Z" - latency: 1.180958ms message: 'network-check-target-ip-10-0-141-147: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:46:27Z" - latency: 1.088351ms message: 'network-check-target-ip-10-0-141-147: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:45:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:51:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-147-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-147.us-west-1.compute.internal uid: ea720a72-0da2-4502-9a49-c756fea25d5e resourceVersion: "99118" uid: 768a21dd-388d-4171-8fd4-1695c85c40a5 spec: sourcePod: network-check-source-6f78d59f99-t9z6m targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T21:57:27Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.027318ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:51:27Z" - latency: 1.914047ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:51:27Z" - latency: 944.782µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:50:27Z" - latency: 1.941015ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:50:27Z" - latency: 1.084445ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:49:27Z" - latency: 2.063984ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:49:27Z" - latency: 1.043682ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:48:27Z" - latency: 2.100762ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:48:27Z" - latency: 1.063572ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:47:27Z" - latency: 2.251317ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:47:27Z" kind: List metadata: resourceVersion: ""