apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T01:02:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-23-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-23.ec2.internal uid: 3cd7b3a6-0a6c-4646-817d-8b1d8648e336 resourceVersion: "30586" uid: 0a612b3c-8a14-4e1a-9776-0502810d8244 spec: sourcePod: network-check-source-6947749cfc-whh4d targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-13T01:09:40Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.157477ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:16:40Z" - latency: 1.203535ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:15:40Z" - latency: 758.354µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:14:40Z" - latency: 1.06137ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:13:40Z" - latency: 1.143688ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:12:40Z" - latency: 1.405617ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:11:40Z" - latency: 1.282455ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:10:40Z" - latency: 2.000928ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:09:40Z" - latency: 901.594µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:08:40Z" - latency: 957.393µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:07:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T01:02:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-23-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-23.ec2.internal uid: 3cd7b3a6-0a6c-4646-817d-8b1d8648e336 resourceVersion: "29290" uid: 38bf8af9-1dd1-42a0-b998-70166596d7a6 spec: sourcePod: network-check-source-6947749cfc-whh4d targetEndpoint: abf3ee3bc4b0f43be9f52d7547fa9a4c-9c415e828877fd16.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-13T01:08:40Z" message: 'load-balancer-api-external: tcp connection to abf3ee3bc4b0f43be9f52d7547fa9a4c-9c415e828877fd16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.303291ms message: 'load-balancer-api-external: tcp connection to abf3ee3bc4b0f43be9f52d7547fa9a4c-9c415e828877fd16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:14:40Z" - latency: 8.254049ms message: 'load-balancer-api-external: resolved host name abf3ee3bc4b0f43be9f52d7547fa9a4c-9c415e828877fd16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T01:14:40Z" - latency: 3.690109ms message: 'load-balancer-api-external: tcp connection to abf3ee3bc4b0f43be9f52d7547fa9a4c-9c415e828877fd16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:13:40Z" - latency: 8.509118ms message: 'load-balancer-api-external: resolved host name abf3ee3bc4b0f43be9f52d7547fa9a4c-9c415e828877fd16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T01:13:40Z" - latency: 4.385423ms message: 'load-balancer-api-external: tcp connection to abf3ee3bc4b0f43be9f52d7547fa9a4c-9c415e828877fd16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:12:40Z" - latency: 7.057815ms message: 'load-balancer-api-external: resolved host name abf3ee3bc4b0f43be9f52d7547fa9a4c-9c415e828877fd16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T01:12:40Z" - latency: 4.160135ms message: 'load-balancer-api-external: tcp connection to abf3ee3bc4b0f43be9f52d7547fa9a4c-9c415e828877fd16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:11:40Z" - latency: 6.558474ms message: 'load-balancer-api-external: resolved host name abf3ee3bc4b0f43be9f52d7547fa9a4c-9c415e828877fd16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T01:11:40Z" - latency: 6.070924ms message: 'load-balancer-api-external: tcp connection to abf3ee3bc4b0f43be9f52d7547fa9a4c-9c415e828877fd16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:10:40Z" - latency: 7.145292ms message: 'load-balancer-api-external: resolved host name abf3ee3bc4b0f43be9f52d7547fa9a4c-9c415e828877fd16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T01:10:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T01:02:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-23-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-23.ec2.internal uid: 3cd7b3a6-0a6c-4646-817d-8b1d8648e336 resourceVersion: "29289" uid: e57cd395-a124-4291-af5d-56411b014740 spec: sourcePod: network-check-source-6947749cfc-whh4d targetEndpoint: abf3ee3bc4b0f43be9f52d7547fa9a4c-9c415e828877fd16.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-13T01:08:40Z" message: 'load-balancer-api-internal: tcp connection to abf3ee3bc4b0f43be9f52d7547fa9a4c-9c415e828877fd16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.331785ms message: 'load-balancer-api-internal: tcp connection to abf3ee3bc4b0f43be9f52d7547fa9a4c-9c415e828877fd16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:14:40Z" - latency: 8.142522ms message: 'load-balancer-api-internal: resolved host name abf3ee3bc4b0f43be9f52d7547fa9a4c-9c415e828877fd16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T01:14:40Z" - latency: 4.22094ms message: 'load-balancer-api-internal: tcp connection to abf3ee3bc4b0f43be9f52d7547fa9a4c-9c415e828877fd16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:13:40Z" - latency: 8.456226ms message: 'load-balancer-api-internal: resolved host name abf3ee3bc4b0f43be9f52d7547fa9a4c-9c415e828877fd16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T01:13:40Z" - latency: 4.398057ms message: 'load-balancer-api-internal: tcp connection to abf3ee3bc4b0f43be9f52d7547fa9a4c-9c415e828877fd16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:12:40Z" - latency: 6.970419ms message: 'load-balancer-api-internal: resolved host name abf3ee3bc4b0f43be9f52d7547fa9a4c-9c415e828877fd16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T01:12:40Z" - latency: 4.361929ms message: 'load-balancer-api-internal: tcp connection to abf3ee3bc4b0f43be9f52d7547fa9a4c-9c415e828877fd16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:11:40Z" - latency: 6.52694ms message: 'load-balancer-api-internal: resolved host name abf3ee3bc4b0f43be9f52d7547fa9a4c-9c415e828877fd16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T01:11:40Z" - latency: 5.00403ms message: 'load-balancer-api-internal: tcp connection to abf3ee3bc4b0f43be9f52d7547fa9a4c-9c415e828877fd16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:10:40Z" - latency: 7.090074ms message: 'load-balancer-api-internal: resolved host name abf3ee3bc4b0f43be9f52d7547fa9a4c-9c415e828877fd16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T01:10:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T01:02:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-23-to-network-check-target-ip-10-0-130-214 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-23.ec2.internal uid: 3cd7b3a6-0a6c-4646-817d-8b1d8648e336 resourceVersion: "30584" uid: 0a1d2057-e337-40f7-8c5c-971d907531e9 spec: sourcePod: network-check-source-6947749cfc-whh4d targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-13T01:09:40Z" message: 'network-check-target-ip-10-0-130-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.26455ms message: 'network-check-target-ip-10-0-130-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:16:40Z" - latency: 1.979348ms message: 'network-check-target-ip-10-0-130-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:15:40Z" - latency: 2.148577ms message: 'network-check-target-ip-10-0-130-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:14:40Z" - latency: 2.109366ms message: 'network-check-target-ip-10-0-130-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:13:40Z" - latency: 2.183087ms message: 'network-check-target-ip-10-0-130-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:12:40Z" - latency: 2.295286ms message: 'network-check-target-ip-10-0-130-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:11:40Z" - latency: 2.199073ms message: 'network-check-target-ip-10-0-130-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:10:40Z" - latency: 2.454402ms message: 'network-check-target-ip-10-0-130-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:09:40Z" - latency: 2.157232ms message: 'network-check-target-ip-10-0-130-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:08:40Z" - latency: 2.108641ms message: 'network-check-target-ip-10-0-130-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:07:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T01:02:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-23-to-network-check-target-ip-10-0-138-143 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-23.ec2.internal uid: 3cd7b3a6-0a6c-4646-817d-8b1d8648e336 resourceVersion: "30585" uid: 01663282-3ff7-46e0-8187-aa2705d6d921 spec: sourcePod: network-check-source-6947749cfc-whh4d targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-13T01:09:40Z" message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.272707ms message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:16:40Z" - latency: 2.118528ms message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:15:40Z" - latency: 1.915376ms message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:14:40Z" - latency: 2.021607ms message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:13:40Z" - latency: 2.199125ms message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:12:40Z" - latency: 2.2218ms message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:11:40Z" - latency: 2.167251ms message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:10:40Z" - latency: 2.558038ms message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:09:40Z" - latency: 2.025459ms message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:08:40Z" - latency: 2.212485ms message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:07:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T01:02:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-23-to-network-check-target-ip-10-0-140-23 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-23.ec2.internal uid: 3cd7b3a6-0a6c-4646-817d-8b1d8648e336 resourceVersion: "30583" uid: 6210f587-eb4d-4b93-89a2-f149823e839a spec: sourcePod: network-check-source-6947749cfc-whh4d targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-13T01:09:40Z" message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.02244ms message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:16:40Z" - latency: 1.377521ms message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:15:40Z" - latency: 1.035564ms message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:14:40Z" - latency: 865.435µs message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:13:40Z" - latency: 823.689µs message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:12:40Z" - latency: 927.921µs message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:11:40Z" - latency: 1.11329ms message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:10:40Z" - latency: 1.130245ms message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:09:40Z" - latency: 781.424µs message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:08:40Z" - latency: 1.084642ms message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:07:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T01:02:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-23-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-23.ec2.internal uid: 3cd7b3a6-0a6c-4646-817d-8b1d8648e336 resourceVersion: "29288" uid: 4adf2952-47d6-4591-a9fe-370c75cdc18d spec: sourcePod: network-check-source-6947749cfc-whh4d targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-13T01:08:40Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 982.445µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:14:40Z" - latency: 1.737483ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-13T01:14:40Z" - latency: 832.784µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:13:40Z" - latency: 1.610438ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-13T01:13:40Z" - latency: 1.069107ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:12:40Z" - latency: 1.727737ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-13T01:12:40Z" - latency: 909.132µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:11:40Z" - latency: 1.901186ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-13T01:11:40Z" - latency: 991.202µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-13T01:10:40Z" - latency: 2.413314ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-13T01:10:40Z" kind: List metadata: resourceVersion: ""