apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T15:40:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-232-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-232.ec2.internal uid: f50ff464-db37-45b6-a652-dfeb5c45b6de resourceVersion: "33221" uid: 7d5cc6bf-e4e9-443e-ae0b-5077d893b8cd spec: sourcePod: network-check-source-8894fc9bd-9nzlb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-21T15:47:56Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.517135ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:01:56Z" - latency: 1.010826ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:00:56Z" - latency: 1.161114ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:59:56Z" - latency: 1.018621ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:58:56Z" - latency: 1.191411ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:57:56Z" - latency: 855.412µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:56:56Z" - latency: 968.29µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:55:56Z" - latency: 903.63µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:54:56Z" - latency: 1.448378ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:53:56Z" - latency: 993.049µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:52:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T15:40:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-232-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-232.ec2.internal uid: f50ff464-db37-45b6-a652-dfeb5c45b6de resourceVersion: "35983" uid: 71f27036-3b18-4a41-8fb8-affb75134bf1 spec: sourcePod: network-check-source-8894fc9bd-9nzlb targetEndpoint: a3d634364264c45ce8ca4d81cf941faa-76f327e51f69b0a9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-21T15:46:56Z" message: 'load-balancer-api-external: tcp connection to a3d634364264c45ce8ca4d81cf941faa-76f327e51f69b0a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.932303ms message: 'load-balancer-api-external: tcp connection to a3d634364264c45ce8ca4d81cf941faa-76f327e51f69b0a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:04:56Z" - latency: 6.972256ms message: 'load-balancer-api-external: resolved host name a3d634364264c45ce8ca4d81cf941faa-76f327e51f69b0a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T16:04:56Z" - latency: 4.548953ms message: 'load-balancer-api-external: tcp connection to a3d634364264c45ce8ca4d81cf941faa-76f327e51f69b0a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:03:56Z" - latency: 7.021179ms message: 'load-balancer-api-external: resolved host name a3d634364264c45ce8ca4d81cf941faa-76f327e51f69b0a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T16:03:56Z" - latency: 4.640104ms message: 'load-balancer-api-external: tcp connection to a3d634364264c45ce8ca4d81cf941faa-76f327e51f69b0a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:02:56Z" - latency: 10.452636ms message: 'load-balancer-api-external: resolved host name a3d634364264c45ce8ca4d81cf941faa-76f327e51f69b0a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T16:02:56Z" - latency: 4.215128ms message: 'load-balancer-api-external: tcp connection to a3d634364264c45ce8ca4d81cf941faa-76f327e51f69b0a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:01:56Z" - latency: 7.665373ms message: 'load-balancer-api-external: resolved host name a3d634364264c45ce8ca4d81cf941faa-76f327e51f69b0a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T16:01:56Z" - latency: 5.158322ms message: 'load-balancer-api-external: tcp connection to a3d634364264c45ce8ca4d81cf941faa-76f327e51f69b0a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:00:56Z" - latency: 6.898208ms message: 'load-balancer-api-external: resolved host name a3d634364264c45ce8ca4d81cf941faa-76f327e51f69b0a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T16:00:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T15:40:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-232-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-232.ec2.internal uid: f50ff464-db37-45b6-a652-dfeb5c45b6de resourceVersion: "35982" uid: 74fdd30f-eae9-464b-93ec-1b271e5188a3 spec: sourcePod: network-check-source-8894fc9bd-9nzlb targetEndpoint: a3d634364264c45ce8ca4d81cf941faa-76f327e51f69b0a9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-21T15:46:56Z" message: 'load-balancer-api-internal: tcp connection to a3d634364264c45ce8ca4d81cf941faa-76f327e51f69b0a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.875911ms message: 'load-balancer-api-internal: tcp connection to a3d634364264c45ce8ca4d81cf941faa-76f327e51f69b0a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:04:56Z" - latency: 6.910009ms message: 'load-balancer-api-internal: resolved host name a3d634364264c45ce8ca4d81cf941faa-76f327e51f69b0a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T16:04:56Z" - latency: 4.511074ms message: 'load-balancer-api-internal: tcp connection to a3d634364264c45ce8ca4d81cf941faa-76f327e51f69b0a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:03:56Z" - latency: 6.897965ms message: 'load-balancer-api-internal: resolved host name a3d634364264c45ce8ca4d81cf941faa-76f327e51f69b0a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T16:03:56Z" - latency: 4.649772ms message: 'load-balancer-api-internal: tcp connection to a3d634364264c45ce8ca4d81cf941faa-76f327e51f69b0a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:02:56Z" - latency: 13.7654ms message: 'load-balancer-api-internal: resolved host name a3d634364264c45ce8ca4d81cf941faa-76f327e51f69b0a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T16:02:56Z" - latency: 3.8039ms message: 'load-balancer-api-internal: tcp connection to a3d634364264c45ce8ca4d81cf941faa-76f327e51f69b0a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:01:56Z" - latency: 7.545762ms message: 'load-balancer-api-internal: resolved host name a3d634364264c45ce8ca4d81cf941faa-76f327e51f69b0a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T16:01:56Z" - latency: 5.183041ms message: 'load-balancer-api-internal: tcp connection to a3d634364264c45ce8ca4d81cf941faa-76f327e51f69b0a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:00:56Z" - latency: 6.816311ms message: 'load-balancer-api-internal: resolved host name a3d634364264c45ce8ca4d81cf941faa-76f327e51f69b0a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T16:00:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T15:40:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-232-to-network-check-target-ip-10-0-128-232 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-232.ec2.internal uid: f50ff464-db37-45b6-a652-dfeb5c45b6de resourceVersion: "33218" uid: aec91294-b914-464d-8e5a-b941f6f52316 spec: sourcePod: network-check-source-8894fc9bd-9nzlb targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-21T15:47:56Z" message: 'network-check-target-ip-10-0-128-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.508636ms message: 'network-check-target-ip-10-0-128-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:01:56Z" - latency: 1.53407ms message: 'network-check-target-ip-10-0-128-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:00:56Z" - latency: 915.748µs message: 'network-check-target-ip-10-0-128-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:59:56Z" - latency: 1.032895ms message: 'network-check-target-ip-10-0-128-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:58:56Z" - latency: 1.112673ms message: 'network-check-target-ip-10-0-128-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:57:56Z" - latency: 713.31µs message: 'network-check-target-ip-10-0-128-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:56:56Z" - latency: 1.057ms message: 'network-check-target-ip-10-0-128-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:55:56Z" - latency: 1.02525ms message: 'network-check-target-ip-10-0-128-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:54:56Z" - latency: 1.263649ms message: 'network-check-target-ip-10-0-128-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:53:56Z" - latency: 942.29µs message: 'network-check-target-ip-10-0-128-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:52:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T15:40:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-232-to-network-check-target-ip-10-0-132-141 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-232.ec2.internal uid: f50ff464-db37-45b6-a652-dfeb5c45b6de resourceVersion: "33220" uid: c5a33636-7709-4e12-b12e-8fd8c53a6f73 spec: sourcePod: network-check-source-8894fc9bd-9nzlb targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-21T15:47:56Z" message: 'network-check-target-ip-10-0-132-141: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.381117ms message: 'network-check-target-ip-10-0-132-141: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:01:56Z" - latency: 1.970178ms message: 'network-check-target-ip-10-0-132-141: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:00:56Z" - latency: 2.001499ms message: 'network-check-target-ip-10-0-132-141: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:59:56Z" - latency: 1.926911ms message: 'network-check-target-ip-10-0-132-141: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:58:56Z" - latency: 2.258488ms message: 'network-check-target-ip-10-0-132-141: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:57:56Z" - latency: 1.671567ms message: 'network-check-target-ip-10-0-132-141: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:56:56Z" - latency: 2.103764ms message: 'network-check-target-ip-10-0-132-141: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:55:56Z" - latency: 1.866067ms message: 'network-check-target-ip-10-0-132-141: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:54:56Z" - latency: 1.762625ms message: 'network-check-target-ip-10-0-132-141: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:53:56Z" - latency: 1.771135ms message: 'network-check-target-ip-10-0-132-141: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:52:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T15:40:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-232-to-network-check-target-ip-10-0-136-123 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-232.ec2.internal uid: f50ff464-db37-45b6-a652-dfeb5c45b6de resourceVersion: "33219" uid: feb17e41-4391-4d50-94be-a9444c5d28d7 spec: sourcePod: network-check-source-8894fc9bd-9nzlb targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-21T15:47:56Z" message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.090101ms message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:01:56Z" - latency: 2.10495ms message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:00:56Z" - latency: 2.328596ms message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:59:56Z" - latency: 3.086897ms message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:58:56Z" - latency: 2.161127ms message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:57:56Z" - latency: 2.028733ms message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:56:56Z" - latency: 2.46533ms message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:55:56Z" - latency: 2.673847ms message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:54:56Z" - latency: 2.226651ms message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:53:56Z" - latency: 2.169069ms message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:52:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T15:40:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-232-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-232.ec2.internal uid: f50ff464-db37-45b6-a652-dfeb5c45b6de resourceVersion: "35981" uid: dbb46fc3-34ff-46fd-a319-25f96824748c spec: sourcePod: network-check-source-8894fc9bd-9nzlb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-21T15:46:56Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.069408ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:04:56Z" - latency: 1.862462ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T16:04:56Z" - latency: 892.205µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:03:56Z" - latency: 2.167788ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T16:03:56Z" - latency: 1.439474ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:02:56Z" - latency: 1.523501ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T16:02:56Z" - latency: 1.00358ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:01:56Z" - latency: 2.171693ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T16:01:56Z" - latency: 924.594µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T16:00:56Z" - latency: 2.05575ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T16:00:56Z" kind: List metadata: resourceVersion: ""