apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T13:10:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-103-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-103.ec2.internal uid: 2a571f5f-f006-4484-a854-3e41d52ae8bc resourceVersion: "32580" uid: d9af5615-233b-4aaa-b7cf-7f6dbcc4aec1 spec: sourcePod: network-check-source-7f44b6dd87-tmx95 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-25T13:17:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 902.326µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:52:15Z" - latency: 1.068207ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:51:15Z" - latency: 1.067484ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:50:15Z" - latency: 1.033622ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:49:15Z" - latency: 863.287µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:48:15Z" - latency: 882.619µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:47:15Z" - latency: 846.66µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:46:15Z" - latency: 1.041479ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:45:15Z" - latency: 932.741µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:44:15Z" - latency: 1.044708ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:43:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T13:10:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-103-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-103.ec2.internal uid: 2a571f5f-f006-4484-a854-3e41d52ae8bc resourceVersion: "32582" uid: 8f221174-8dbb-4193-8058-4b682bf7bbe0 spec: sourcePod: network-check-source-7f44b6dd87-tmx95 targetEndpoint: ab9d211dff7434a34b4acd54c50d3dbd-3249c04209d1cdaf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-25T13:16:15Z" message: 'load-balancer-api-external: tcp connection to ab9d211dff7434a34b4acd54c50d3dbd-3249c04209d1cdaf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.679993ms message: 'load-balancer-api-external: tcp connection to ab9d211dff7434a34b4acd54c50d3dbd-3249c04209d1cdaf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:52:15Z" - latency: 6.632609ms message: 'load-balancer-api-external: resolved host name ab9d211dff7434a34b4acd54c50d3dbd-3249c04209d1cdaf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:52:15Z" - latency: 4.585618ms message: 'load-balancer-api-external: tcp connection to ab9d211dff7434a34b4acd54c50d3dbd-3249c04209d1cdaf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:51:15Z" - latency: 7.459738ms message: 'load-balancer-api-external: resolved host name ab9d211dff7434a34b4acd54c50d3dbd-3249c04209d1cdaf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:51:15Z" - latency: 4.917061ms message: 'load-balancer-api-external: tcp connection to ab9d211dff7434a34b4acd54c50d3dbd-3249c04209d1cdaf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:50:15Z" - latency: 8.230947ms message: 'load-balancer-api-external: resolved host name ab9d211dff7434a34b4acd54c50d3dbd-3249c04209d1cdaf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:50:15Z" - latency: 4.444912ms message: 'load-balancer-api-external: tcp connection to ab9d211dff7434a34b4acd54c50d3dbd-3249c04209d1cdaf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:49:15Z" - latency: 8.195399ms message: 'load-balancer-api-external: resolved host name ab9d211dff7434a34b4acd54c50d3dbd-3249c04209d1cdaf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:49:15Z" - latency: 5.105642ms message: 'load-balancer-api-external: tcp connection to ab9d211dff7434a34b4acd54c50d3dbd-3249c04209d1cdaf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:48:15Z" - latency: 8.238627ms message: 'load-balancer-api-external: resolved host name ab9d211dff7434a34b4acd54c50d3dbd-3249c04209d1cdaf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:48:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T13:10:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-103-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-103.ec2.internal uid: 2a571f5f-f006-4484-a854-3e41d52ae8bc resourceVersion: "32581" uid: 519e71a7-c0c1-4ec9-a692-e9e6434fe2fb spec: sourcePod: network-check-source-7f44b6dd87-tmx95 targetEndpoint: ab9d211dff7434a34b4acd54c50d3dbd-3249c04209d1cdaf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-25T13:16:15Z" message: 'load-balancer-api-internal: tcp connection to ab9d211dff7434a34b4acd54c50d3dbd-3249c04209d1cdaf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.675712ms message: 'load-balancer-api-internal: tcp connection to ab9d211dff7434a34b4acd54c50d3dbd-3249c04209d1cdaf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:52:15Z" - latency: 6.598812ms message: 'load-balancer-api-internal: resolved host name ab9d211dff7434a34b4acd54c50d3dbd-3249c04209d1cdaf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:52:15Z" - latency: 4.860142ms message: 'load-balancer-api-internal: tcp connection to ab9d211dff7434a34b4acd54c50d3dbd-3249c04209d1cdaf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:51:15Z" - latency: 7.500567ms message: 'load-balancer-api-internal: resolved host name ab9d211dff7434a34b4acd54c50d3dbd-3249c04209d1cdaf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:51:15Z" - latency: 4.910787ms message: 'load-balancer-api-internal: tcp connection to ab9d211dff7434a34b4acd54c50d3dbd-3249c04209d1cdaf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:50:15Z" - latency: 8.201193ms message: 'load-balancer-api-internal: resolved host name ab9d211dff7434a34b4acd54c50d3dbd-3249c04209d1cdaf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:50:15Z" - latency: 4.465537ms message: 'load-balancer-api-internal: tcp connection to ab9d211dff7434a34b4acd54c50d3dbd-3249c04209d1cdaf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:49:15Z" - latency: 8.236727ms message: 'load-balancer-api-internal: resolved host name ab9d211dff7434a34b4acd54c50d3dbd-3249c04209d1cdaf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:49:15Z" - latency: 4.077917ms message: 'load-balancer-api-internal: tcp connection to ab9d211dff7434a34b4acd54c50d3dbd-3249c04209d1cdaf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:48:15Z" - latency: 8.255341ms message: 'load-balancer-api-internal: resolved host name ab9d211dff7434a34b4acd54c50d3dbd-3249c04209d1cdaf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:48:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T13:10:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-103-to-network-check-target-ip-10-0-130-213 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-103.ec2.internal uid: 2a571f5f-f006-4484-a854-3e41d52ae8bc resourceVersion: "32578" uid: 892c0169-3bbd-49d1-ac4d-50e3b17468eb spec: sourcePod: network-check-source-7f44b6dd87-tmx95 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-25T13:17:15Z" message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.204408ms message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:52:15Z" - latency: 2.30485ms message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:51:15Z" - latency: 2.319722ms message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:50:15Z" - latency: 2.173628ms message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:49:15Z" - latency: 2.015085ms message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:48:15Z" - latency: 2.09668ms message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:47:15Z" - latency: 2.10301ms message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:46:15Z" - latency: 2.614684ms message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:45:15Z" - latency: 2.275457ms message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:44:15Z" - latency: 2.23983ms message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:43:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T13:10:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-103-to-network-check-target-ip-10-0-135-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-103.ec2.internal uid: 2a571f5f-f006-4484-a854-3e41d52ae8bc resourceVersion: "32576" uid: da717016-fd49-448e-9282-a9d981fe135b spec: sourcePod: network-check-source-7f44b6dd87-tmx95 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-25T13:17:15Z" message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 960.876µs message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:52:15Z" - latency: 822.426µs message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:51:15Z" - latency: 836.775µs message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:50:15Z" - latency: 1.324668ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:49:15Z" - latency: 1.270895ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:48:15Z" - latency: 1.24955ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:47:15Z" - latency: 1.191259ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:46:15Z" - latency: 879.302µs message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:45:15Z" - latency: 954.098µs message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:44:15Z" - latency: 953.43µs message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:43:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T13:10:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-103-to-network-check-target-ip-10-0-139-18 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-103.ec2.internal uid: 2a571f5f-f006-4484-a854-3e41d52ae8bc resourceVersion: "32577" uid: 593075b3-616b-4de0-850f-dc75469e20d9 spec: sourcePod: network-check-source-7f44b6dd87-tmx95 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-25T13:17:15Z" message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.105784ms message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:52:15Z" - latency: 2.133159ms message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:51:15Z" - latency: 2.152001ms message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:50:15Z" - latency: 2.050389ms message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:49:15Z" - latency: 2.395466ms message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:48:15Z" - latency: 2.156616ms message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:47:15Z" - latency: 2.26907ms message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:46:15Z" - latency: 2.09587ms message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:45:15Z" - latency: 2.308995ms message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:44:15Z" - latency: 2.267417ms message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:43:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T13:10:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-103-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-103.ec2.internal uid: 2a571f5f-f006-4484-a854-3e41d52ae8bc resourceVersion: "32579" uid: deae5858-78c9-4a00-acbe-88e2a09aa590 spec: sourcePod: network-check-source-7f44b6dd87-tmx95 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-25T13:16:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.070161ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:52:15Z" - latency: 1.726771ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T13:52:15Z" - latency: 1.070589ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:51:15Z" - latency: 1.504196ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T13:51:15Z" - latency: 888.401µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:50:15Z" - latency: 1.652594ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T13:50:15Z" - latency: 904.74µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:49:15Z" - latency: 1.88399ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T13:49:15Z" - latency: 951.956µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:48:15Z" - latency: 1.660737ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T13:48:15Z" kind: List metadata: resourceVersion: ""