apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T21:01:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-146-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-146.ec2.internal uid: 88d0b125-a796-4e75-944d-c0f38e34b725 resourceVersion: "61462" uid: a78a18e9-b9b9-42f7-90d8-72deb8f8955d spec: sourcePod: network-check-source-869dcfcdcd-8b78v targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-13T21:08:38Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.08353ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:43:38Z" - latency: 841.082µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:42:38Z" - latency: 1.011173ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:41:38Z" - latency: 941.602µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:40:38Z" - latency: 1.056924ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:39:38Z" - latency: 930.426µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:38:38Z" - latency: 1.403647ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:37:38Z" - latency: 867.873µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:36:38Z" - latency: 1.193633ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:35:38Z" - latency: 996.946µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:34:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T21:01:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-146-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-146.ec2.internal uid: 88d0b125-a796-4e75-944d-c0f38e34b725 resourceVersion: "61464" uid: b0e9618a-b5c5-4469-8c41-07941f8df09c spec: sourcePod: network-check-source-869dcfcdcd-8b78v targetEndpoint: aa581cd58143e4d3bb7ebf761e7c9254-5adac0b4ea4325b3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T21:07:38Z" message: 'load-balancer-api-external: tcp connection to aa581cd58143e4d3bb7ebf761e7c9254-5adac0b4ea4325b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.919796ms message: 'load-balancer-api-external: tcp connection to aa581cd58143e4d3bb7ebf761e7c9254-5adac0b4ea4325b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:43:38Z" - latency: 9.389504ms message: 'load-balancer-api-external: resolved host name aa581cd58143e4d3bb7ebf761e7c9254-5adac0b4ea4325b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:43:38Z" - latency: 4.287281ms message: 'load-balancer-api-external: tcp connection to aa581cd58143e4d3bb7ebf761e7c9254-5adac0b4ea4325b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:42:38Z" - latency: 7.161994ms message: 'load-balancer-api-external: resolved host name aa581cd58143e4d3bb7ebf761e7c9254-5adac0b4ea4325b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:42:38Z" - latency: 5.852195ms message: 'load-balancer-api-external: tcp connection to aa581cd58143e4d3bb7ebf761e7c9254-5adac0b4ea4325b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:41:38Z" - latency: 10.886021ms message: 'load-balancer-api-external: resolved host name aa581cd58143e4d3bb7ebf761e7c9254-5adac0b4ea4325b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:41:38Z" - latency: 5.525506ms message: 'load-balancer-api-external: tcp connection to aa581cd58143e4d3bb7ebf761e7c9254-5adac0b4ea4325b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:40:38Z" - latency: 8.919881ms message: 'load-balancer-api-external: resolved host name aa581cd58143e4d3bb7ebf761e7c9254-5adac0b4ea4325b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:40:38Z" - latency: 4.318112ms message: 'load-balancer-api-external: tcp connection to aa581cd58143e4d3bb7ebf761e7c9254-5adac0b4ea4325b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:39:38Z" - latency: 6.560672ms message: 'load-balancer-api-external: resolved host name aa581cd58143e4d3bb7ebf761e7c9254-5adac0b4ea4325b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:39:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T21:01:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-146-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-146.ec2.internal uid: 88d0b125-a796-4e75-944d-c0f38e34b725 resourceVersion: "61463" uid: bd1f6e75-ed78-4b7f-8719-7f62334af447 spec: sourcePod: network-check-source-869dcfcdcd-8b78v targetEndpoint: aa581cd58143e4d3bb7ebf761e7c9254-5adac0b4ea4325b3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T21:07:38Z" message: 'load-balancer-api-internal: tcp connection to aa581cd58143e4d3bb7ebf761e7c9254-5adac0b4ea4325b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.389961ms message: 'load-balancer-api-internal: tcp connection to aa581cd58143e4d3bb7ebf761e7c9254-5adac0b4ea4325b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:43:38Z" - latency: 9.374375ms message: 'load-balancer-api-internal: resolved host name aa581cd58143e4d3bb7ebf761e7c9254-5adac0b4ea4325b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:43:38Z" - latency: 4.647428ms message: 'load-balancer-api-internal: tcp connection to aa581cd58143e4d3bb7ebf761e7c9254-5adac0b4ea4325b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:42:38Z" - latency: 7.208413ms message: 'load-balancer-api-internal: resolved host name aa581cd58143e4d3bb7ebf761e7c9254-5adac0b4ea4325b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:42:38Z" - latency: 5.881714ms message: 'load-balancer-api-internal: tcp connection to aa581cd58143e4d3bb7ebf761e7c9254-5adac0b4ea4325b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:41:38Z" - latency: 10.854646ms message: 'load-balancer-api-internal: resolved host name aa581cd58143e4d3bb7ebf761e7c9254-5adac0b4ea4325b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:41:38Z" - latency: 4.837193ms message: 'load-balancer-api-internal: tcp connection to aa581cd58143e4d3bb7ebf761e7c9254-5adac0b4ea4325b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:40:38Z" - latency: 8.991636ms message: 'load-balancer-api-internal: resolved host name aa581cd58143e4d3bb7ebf761e7c9254-5adac0b4ea4325b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:40:38Z" - latency: 4.35283ms message: 'load-balancer-api-internal: tcp connection to aa581cd58143e4d3bb7ebf761e7c9254-5adac0b4ea4325b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:39:38Z" - latency: 6.508697ms message: 'load-balancer-api-internal: resolved host name aa581cd58143e4d3bb7ebf761e7c9254-5adac0b4ea4325b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T21:39:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T21:01:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-146-to-network-check-target-ip-10-0-130-205 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-146.ec2.internal uid: 88d0b125-a796-4e75-944d-c0f38e34b725 resourceVersion: "61460" uid: 54337a9d-a32c-433a-83cf-d1ffcecd9cba spec: sourcePod: network-check-source-869dcfcdcd-8b78v targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-13T21:08:38Z" message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.139255ms message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:43:38Z" - latency: 2.192504ms message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:42:38Z" - latency: 1.789854ms message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:41:38Z" - latency: 1.842714ms message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:40:38Z" - latency: 1.970722ms message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:39:38Z" - latency: 1.878534ms message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:38:38Z" - latency: 2.01226ms message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:37:38Z" - latency: 1.918545ms message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:36:38Z" - latency: 2.040239ms message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:35:38Z" - latency: 1.805499ms message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:34:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T21:01:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-146-to-network-check-target-ip-10-0-137-162 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-146.ec2.internal uid: 88d0b125-a796-4e75-944d-c0f38e34b725 resourceVersion: "61459" uid: 9e4af296-52fd-428f-afe1-02fb2e792a94 spec: sourcePod: network-check-source-869dcfcdcd-8b78v targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-13T21:08:38Z" message: 'network-check-target-ip-10-0-137-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.108889ms message: 'network-check-target-ip-10-0-137-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:43:38Z" - latency: 1.801474ms message: 'network-check-target-ip-10-0-137-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:42:38Z" - latency: 2.154983ms message: 'network-check-target-ip-10-0-137-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:41:38Z" - latency: 2.003273ms message: 'network-check-target-ip-10-0-137-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:40:38Z" - latency: 2.267317ms message: 'network-check-target-ip-10-0-137-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:39:38Z" - latency: 2.044752ms message: 'network-check-target-ip-10-0-137-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:38:38Z" - latency: 2.040396ms message: 'network-check-target-ip-10-0-137-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:37:38Z" - latency: 1.780859ms message: 'network-check-target-ip-10-0-137-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:36:38Z" - latency: 2.025376ms message: 'network-check-target-ip-10-0-137-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:35:38Z" - latency: 2.263003ms message: 'network-check-target-ip-10-0-137-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:34:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T21:01:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-146-to-network-check-target-ip-10-0-138-146 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-146.ec2.internal uid: 88d0b125-a796-4e75-944d-c0f38e34b725 resourceVersion: "61458" uid: c9d8a895-08c3-4d5e-bf6e-5c6b7be47616 spec: sourcePod: network-check-source-869dcfcdcd-8b78v targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-13T21:08:38Z" message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 974.764µs message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:43:38Z" - latency: 1.080443ms message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:42:38Z" - latency: 825.368µs message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:41:38Z" - latency: 1.081613ms message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:40:38Z" - latency: 877.75µs message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:39:38Z" - latency: 1.247402ms message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:38:38Z" - latency: 818.583µs message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:37:38Z" - latency: 1.462895ms message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:36:38Z" - latency: 1.537298ms message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:35:38Z" - latency: 831.221µs message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:34:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T21:01:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-146-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-146.ec2.internal uid: 88d0b125-a796-4e75-944d-c0f38e34b725 resourceVersion: "61461" uid: a0f356dc-df60-4649-a838-fcc6fca42ae8 spec: sourcePod: network-check-source-869dcfcdcd-8b78v targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-13T21:07:38Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.0905ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:43:38Z" - latency: 2.1226ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T21:43:38Z" - latency: 1.016092ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:42:38Z" - latency: 1.972665ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T21:42:38Z" - latency: 887.575µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:41:38Z" - latency: 2.136518ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T21:41:38Z" - latency: 840.004µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:40:38Z" - latency: 2.008274ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T21:40:38Z" - latency: 1.051952ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T21:39:38Z" - latency: 1.916396ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T21:39:38Z" kind: List metadata: resourceVersion: ""