apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T21:20:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-233-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-233.ec2.internal uid: 8024e540-c3c1-4974-aa01-8e745f0f2591 resourceVersion: "76532" uid: 49ab9575-53f4-466d-842a-3c595d9d3895 spec: sourcePod: network-check-source-7d88cb55d8-52fvv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-29T21:27:55Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 963µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:16:55Z" - latency: 962.479µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:15:55Z" - latency: 1.084129ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:14:55Z" - latency: 995.949µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:13:55Z" - latency: 974.573µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:12:55Z" - latency: 1.274674ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:11:55Z" - latency: 1.028206ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:10:55Z" - latency: 922.896µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:09:55Z" - latency: 980.928µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:08:55Z" - latency: 1.467368ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:07:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T21:20:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-233-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-233.ec2.internal uid: 8024e540-c3c1-4974-aa01-8e745f0f2591 resourceVersion: "80653" uid: a6c0d5d2-0270-4521-8890-605f64f4e62d spec: sourcePod: network-check-source-7d88cb55d8-52fvv targetEndpoint: afd28181d74294124bec7e742396b0c2-7bb9583e0315b57e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T21:26:55Z" message: 'load-balancer-api-external: tcp connection to afd28181d74294124bec7e742396b0c2-7bb9583e0315b57e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.8749ms message: 'load-balancer-api-external: tcp connection to afd28181d74294124bec7e742396b0c2-7bb9583e0315b57e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:20:55Z" - latency: 8.093533ms message: 'load-balancer-api-external: resolved host name afd28181d74294124bec7e742396b0c2-7bb9583e0315b57e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T22:20:55Z" - latency: 5.17968ms message: 'load-balancer-api-external: tcp connection to afd28181d74294124bec7e742396b0c2-7bb9583e0315b57e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:19:55Z" - latency: 9.811562ms message: 'load-balancer-api-external: resolved host name afd28181d74294124bec7e742396b0c2-7bb9583e0315b57e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T22:19:55Z" - latency: 4.832055ms message: 'load-balancer-api-external: tcp connection to afd28181d74294124bec7e742396b0c2-7bb9583e0315b57e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:18:55Z" - latency: 7.839783ms message: 'load-balancer-api-external: resolved host name afd28181d74294124bec7e742396b0c2-7bb9583e0315b57e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T22:18:55Z" - latency: 3.695997ms message: 'load-balancer-api-external: tcp connection to afd28181d74294124bec7e742396b0c2-7bb9583e0315b57e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:17:55Z" - latency: 8.261985ms message: 'load-balancer-api-external: resolved host name afd28181d74294124bec7e742396b0c2-7bb9583e0315b57e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T22:17:55Z" - latency: 4.581849ms message: 'load-balancer-api-external: tcp connection to afd28181d74294124bec7e742396b0c2-7bb9583e0315b57e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:16:55Z" - latency: 8.261952ms message: 'load-balancer-api-external: resolved host name afd28181d74294124bec7e742396b0c2-7bb9583e0315b57e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T22:16:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T21:20:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-233-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-233.ec2.internal uid: 8024e540-c3c1-4974-aa01-8e745f0f2591 resourceVersion: "80652" uid: ddacd7eb-6e81-4cc8-9ef6-3c7b80d57806 spec: sourcePod: network-check-source-7d88cb55d8-52fvv targetEndpoint: afd28181d74294124bec7e742396b0c2-7bb9583e0315b57e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T21:26:55Z" message: 'load-balancer-api-internal: tcp connection to afd28181d74294124bec7e742396b0c2-7bb9583e0315b57e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.730927ms message: 'load-balancer-api-internal: tcp connection to afd28181d74294124bec7e742396b0c2-7bb9583e0315b57e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:20:55Z" - latency: 8.132386ms message: 'load-balancer-api-internal: resolved host name afd28181d74294124bec7e742396b0c2-7bb9583e0315b57e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T22:20:55Z" - latency: 5.15402ms message: 'load-balancer-api-internal: tcp connection to afd28181d74294124bec7e742396b0c2-7bb9583e0315b57e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:19:55Z" - latency: 9.940711ms message: 'load-balancer-api-internal: resolved host name afd28181d74294124bec7e742396b0c2-7bb9583e0315b57e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T22:19:55Z" - latency: 4.849396ms message: 'load-balancer-api-internal: tcp connection to afd28181d74294124bec7e742396b0c2-7bb9583e0315b57e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:18:55Z" - latency: 7.861951ms message: 'load-balancer-api-internal: resolved host name afd28181d74294124bec7e742396b0c2-7bb9583e0315b57e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T22:18:55Z" - latency: 3.721512ms message: 'load-balancer-api-internal: tcp connection to afd28181d74294124bec7e742396b0c2-7bb9583e0315b57e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:17:55Z" - latency: 8.321691ms message: 'load-balancer-api-internal: resolved host name afd28181d74294124bec7e742396b0c2-7bb9583e0315b57e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T22:17:55Z" - latency: 4.342104ms message: 'load-balancer-api-internal: tcp connection to afd28181d74294124bec7e742396b0c2-7bb9583e0315b57e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:16:55Z" - latency: 8.195439ms message: 'load-balancer-api-internal: resolved host name afd28181d74294124bec7e742396b0c2-7bb9583e0315b57e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T22:16:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T21:20:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-233-to-network-check-target-ip-10-0-129-123 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-233.ec2.internal uid: 8024e540-c3c1-4974-aa01-8e745f0f2591 resourceVersion: "76530" uid: 8cb6c595-1577-4cc3-bfec-c7fbf9fcd883 spec: sourcePod: network-check-source-7d88cb55d8-52fvv targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T21:27:55Z" message: 'network-check-target-ip-10-0-129-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.31473ms message: 'network-check-target-ip-10-0-129-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:16:55Z" - latency: 2.515947ms message: 'network-check-target-ip-10-0-129-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:15:55Z" - latency: 2.43085ms message: 'network-check-target-ip-10-0-129-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:14:55Z" - latency: 2.2938ms message: 'network-check-target-ip-10-0-129-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:13:55Z" - latency: 2.51611ms message: 'network-check-target-ip-10-0-129-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:12:55Z" - latency: 2.169021ms message: 'network-check-target-ip-10-0-129-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:11:55Z" - latency: 2.545907ms message: 'network-check-target-ip-10-0-129-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:10:55Z" - latency: 2.122638ms message: 'network-check-target-ip-10-0-129-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:09:55Z" - latency: 2.320823ms message: 'network-check-target-ip-10-0-129-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:08:55Z" - latency: 2.321261ms message: 'network-check-target-ip-10-0-129-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:07:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T21:20:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-233-to-network-check-target-ip-10-0-129-242 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-233.ec2.internal uid: 8024e540-c3c1-4974-aa01-8e745f0f2591 resourceVersion: "76531" uid: bb1732a4-b958-400e-acaa-11dcb1a59ca7 spec: sourcePod: network-check-source-7d88cb55d8-52fvv targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-29T21:27:55Z" message: 'network-check-target-ip-10-0-129-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.62899ms message: 'network-check-target-ip-10-0-129-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:16:55Z" - latency: 2.607705ms message: 'network-check-target-ip-10-0-129-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:15:55Z" - latency: 2.470423ms message: 'network-check-target-ip-10-0-129-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:14:55Z" - latency: 2.528288ms message: 'network-check-target-ip-10-0-129-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:13:55Z" - latency: 2.415302ms message: 'network-check-target-ip-10-0-129-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:12:55Z" - latency: 2.377101ms message: 'network-check-target-ip-10-0-129-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:11:55Z" - latency: 2.384106ms message: 'network-check-target-ip-10-0-129-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:10:55Z" - latency: 2.380643ms message: 'network-check-target-ip-10-0-129-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:09:55Z" - latency: 2.303517ms message: 'network-check-target-ip-10-0-129-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:08:55Z" - latency: 2.499386ms message: 'network-check-target-ip-10-0-129-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:07:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T21:20:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-233-to-network-check-target-ip-10-0-141-233 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-233.ec2.internal uid: 8024e540-c3c1-4974-aa01-8e745f0f2591 resourceVersion: "76529" uid: 4d6f0338-e924-4390-8565-39e205fcb375 spec: sourcePod: network-check-source-7d88cb55d8-52fvv targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-29T21:27:55Z" message: 'network-check-target-ip-10-0-141-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 975.561µs message: 'network-check-target-ip-10-0-141-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:16:55Z" - latency: 948.334µs message: 'network-check-target-ip-10-0-141-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:15:55Z" - latency: 863.511µs message: 'network-check-target-ip-10-0-141-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:14:55Z" - latency: 958.231µs message: 'network-check-target-ip-10-0-141-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:13:55Z" - latency: 792.61µs message: 'network-check-target-ip-10-0-141-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:12:55Z" - latency: 950.878µs message: 'network-check-target-ip-10-0-141-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:11:55Z" - latency: 999.978µs message: 'network-check-target-ip-10-0-141-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:10:55Z" - latency: 854.359µs message: 'network-check-target-ip-10-0-141-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:09:55Z" - latency: 800.733µs message: 'network-check-target-ip-10-0-141-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:08:55Z" - latency: 1.264405ms message: 'network-check-target-ip-10-0-141-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:07:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T21:20:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-233-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-233.ec2.internal uid: 8024e540-c3c1-4974-aa01-8e745f0f2591 resourceVersion: "80649" uid: 92776aaf-7b41-4c51-8f00-c15abcfac96a spec: sourcePod: network-check-source-7d88cb55d8-52fvv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-29T21:26:55Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 886.714µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:20:55Z" - latency: 1.770148ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T22:20:55Z" - latency: 1.238223ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:19:55Z" - latency: 2.001842ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T22:19:55Z" - latency: 888.228µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:18:55Z" - latency: 1.812324ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T22:18:55Z" - latency: 1.205467ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:17:55Z" - latency: 1.7569ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T22:17:55Z" - latency: 1.097115ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:16:55Z" - latency: 1.877834ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T22:16:55Z" kind: List metadata: resourceVersion: ""