apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T21:12:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-213-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-213.ec2.internal uid: 49101a6e-4c88-4232-8d94-07a285270ccb resourceVersion: "55271" uid: 5c2e7fb6-6f45-46a7-b615-df6bcf2b6691 spec: sourcePod: network-check-source-989f8b8dc-s5zz4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-08T21:19:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.153865ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:47:15Z" - latency: 830.814µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:46:15Z" - latency: 1.172536ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:45:15Z" - latency: 877.34µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:44:15Z" - latency: 734.12µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:43:15Z" - latency: 704.11µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:42:15Z" - latency: 857.934µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:41:15Z" - latency: 693.648µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:40:15Z" - latency: 1.30971ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:39:15Z" - latency: 1.148332ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:38:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T21:12:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-213-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-213.ec2.internal uid: 49101a6e-4c88-4232-8d94-07a285270ccb resourceVersion: "56357" uid: 532d02a1-3a45-46ef-bb21-42619136742d spec: sourcePod: network-check-source-989f8b8dc-s5zz4 targetEndpoint: ae031de3cb716427faedb725be995e09-b2428c2ab90ec8af.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T21:18:15Z" message: 'load-balancer-api-external: tcp connection to ae031de3cb716427faedb725be995e09-b2428c2ab90ec8af.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.867665ms message: 'load-balancer-api-external: tcp connection to ae031de3cb716427faedb725be995e09-b2428c2ab90ec8af.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:48:15Z" - latency: 8.583267ms message: 'load-balancer-api-external: resolved host name ae031de3cb716427faedb725be995e09-b2428c2ab90ec8af.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T21:48:15Z" - latency: 4.820993ms message: 'load-balancer-api-external: tcp connection to ae031de3cb716427faedb725be995e09-b2428c2ab90ec8af.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:47:15Z" - latency: 8.714841ms message: 'load-balancer-api-external: resolved host name ae031de3cb716427faedb725be995e09-b2428c2ab90ec8af.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T21:47:15Z" - latency: 3.999863ms message: 'load-balancer-api-external: tcp connection to ae031de3cb716427faedb725be995e09-b2428c2ab90ec8af.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:46:15Z" - latency: 7.004903ms message: 'load-balancer-api-external: resolved host name ae031de3cb716427faedb725be995e09-b2428c2ab90ec8af.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T21:46:15Z" - latency: 3.478558ms message: 'load-balancer-api-external: tcp connection to ae031de3cb716427faedb725be995e09-b2428c2ab90ec8af.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:45:15Z" - latency: 8.271909ms message: 'load-balancer-api-external: resolved host name ae031de3cb716427faedb725be995e09-b2428c2ab90ec8af.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T21:45:15Z" - latency: 3.274714ms message: 'load-balancer-api-external: tcp connection to ae031de3cb716427faedb725be995e09-b2428c2ab90ec8af.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:44:15Z" - latency: 7.940478ms message: 'load-balancer-api-external: resolved host name ae031de3cb716427faedb725be995e09-b2428c2ab90ec8af.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T21:44:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T21:12:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-213-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-213.ec2.internal uid: 49101a6e-4c88-4232-8d94-07a285270ccb resourceVersion: "56356" uid: e87d8060-cd3a-4707-9a39-ae2d82281b2d spec: sourcePod: network-check-source-989f8b8dc-s5zz4 targetEndpoint: ae031de3cb716427faedb725be995e09-b2428c2ab90ec8af.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T21:18:15Z" message: 'load-balancer-api-internal: tcp connection to ae031de3cb716427faedb725be995e09-b2428c2ab90ec8af.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.896179ms message: 'load-balancer-api-internal: tcp connection to ae031de3cb716427faedb725be995e09-b2428c2ab90ec8af.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:48:15Z" - latency: 8.557831ms message: 'load-balancer-api-internal: resolved host name ae031de3cb716427faedb725be995e09-b2428c2ab90ec8af.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T21:48:15Z" - latency: 4.828779ms message: 'load-balancer-api-internal: tcp connection to ae031de3cb716427faedb725be995e09-b2428c2ab90ec8af.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:47:15Z" - latency: 8.687039ms message: 'load-balancer-api-internal: resolved host name ae031de3cb716427faedb725be995e09-b2428c2ab90ec8af.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T21:47:15Z" - latency: 3.984239ms message: 'load-balancer-api-internal: tcp connection to ae031de3cb716427faedb725be995e09-b2428c2ab90ec8af.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:46:15Z" - latency: 7.059729ms message: 'load-balancer-api-internal: resolved host name ae031de3cb716427faedb725be995e09-b2428c2ab90ec8af.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T21:46:15Z" - latency: 3.450995ms message: 'load-balancer-api-internal: tcp connection to ae031de3cb716427faedb725be995e09-b2428c2ab90ec8af.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:45:15Z" - latency: 8.187245ms message: 'load-balancer-api-internal: resolved host name ae031de3cb716427faedb725be995e09-b2428c2ab90ec8af.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T21:45:15Z" - latency: 3.315619ms message: 'load-balancer-api-internal: tcp connection to ae031de3cb716427faedb725be995e09-b2428c2ab90ec8af.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:44:15Z" - latency: 7.866008ms message: 'load-balancer-api-internal: resolved host name ae031de3cb716427faedb725be995e09-b2428c2ab90ec8af.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T21:44:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T21:12:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-213-to-network-check-target-ip-10-0-128-213 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-213.ec2.internal uid: 49101a6e-4c88-4232-8d94-07a285270ccb resourceVersion: "55268" uid: 3f3e7dec-10c2-4ae9-b872-af11056609e9 spec: sourcePod: network-check-source-989f8b8dc-s5zz4 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-08T21:19:15Z" message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.502788ms message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:47:15Z" - latency: 873.452µs message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:46:15Z" - latency: 936.328µs message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:45:15Z" - latency: 1.384731ms message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:44:15Z" - latency: 1.616182ms message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:43:15Z" - latency: 942.511µs message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:42:15Z" - latency: 1.35372ms message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:41:15Z" - latency: 697.946µs message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:40:15Z" - latency: 742.974µs message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:39:15Z" - latency: 985.313µs message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:38:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T21:12:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-213-to-network-check-target-ip-10-0-132-192 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-213.ec2.internal uid: 49101a6e-4c88-4232-8d94-07a285270ccb resourceVersion: "55269" uid: fc50b7b5-7f6a-4fd7-b0bd-ac1217a956e5 spec: sourcePod: network-check-source-989f8b8dc-s5zz4 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T21:19:15Z" message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.406326ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:47:15Z" - latency: 2.264174ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:46:15Z" - latency: 2.534799ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:45:15Z" - latency: 2.272174ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:44:15Z" - latency: 2.053115ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:43:15Z" - latency: 2.117749ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:42:15Z" - latency: 2.67887ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:41:15Z" - latency: 1.876497ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:40:15Z" - latency: 2.275624ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:39:15Z" - latency: 2.318998ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:38:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T21:12:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-213-to-network-check-target-ip-10-0-142-255 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-213.ec2.internal uid: 49101a6e-4c88-4232-8d94-07a285270ccb resourceVersion: "55270" uid: 4bcc415b-e6e7-49e5-aa27-ff4e9c60de5d spec: sourcePod: network-check-source-989f8b8dc-s5zz4 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-08T21:19:15Z" message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.383826ms message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:47:15Z" - latency: 2.434505ms message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:46:15Z" - latency: 2.539167ms message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:45:15Z" - latency: 2.278926ms message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:44:15Z" - latency: 2.429791ms message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:43:15Z" - latency: 2.765809ms message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:42:15Z" - latency: 2.274274ms message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:41:15Z" - latency: 1.967771ms message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:40:15Z" - latency: 2.210534ms message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:39:15Z" - latency: 2.335849ms message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:38:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T21:12:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-213-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-213.ec2.internal uid: 49101a6e-4c88-4232-8d94-07a285270ccb resourceVersion: "56355" uid: 308e2f83-77b3-409d-bdac-9f2966ccdd87 spec: sourcePod: network-check-source-989f8b8dc-s5zz4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-08T21:18:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.151921ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:48:15Z" - latency: 1.789586ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T21:48:15Z" - latency: 1.210867ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:47:15Z" - latency: 2.358527ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T21:47:15Z" - latency: 889.798µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:46:15Z" - latency: 1.769241ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T21:46:15Z" - latency: 900.697µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:45:15Z" - latency: 1.927219ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T21:45:15Z" - latency: 1.179322ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T21:44:15Z" - latency: 1.876417ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T21:44:15Z" kind: List metadata: resourceVersion: ""