apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T07:59:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-45-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-45.ec2.internal uid: ab8b9e0d-a695-4f9c-bb10-ea93f9ca3275 resourceVersion: "19519" uid: ecb0cb85-7425-4af5-a01f-63e1567ac6eb spec: sourcePod: network-check-source-8894fc9bd-4d2hp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-17T08:06:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 852.792µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:13:51Z" - latency: 1.237933ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:12:51Z" - latency: 853.957µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:11:51Z" - latency: 955.092µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:10:51Z" - latency: 883.584µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:09:51Z" - latency: 953.704µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:08:51Z" - latency: 1.346189ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:07:51Z" - latency: 766.93µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:06:51Z" - latency: 915.058µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:05:51Z" - latency: 969.899µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:04:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T07:59:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-45-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-45.ec2.internal uid: ab8b9e0d-a695-4f9c-bb10-ea93f9ca3275 resourceVersion: "21560" uid: 3b7d6d8c-c5c5-4314-adb7-4ac20e12c0ca spec: sourcePod: network-check-source-8894fc9bd-4d2hp targetEndpoint: a9d41ff4a38f84d1f98155c28e0a0441-8a6f4b07a1cbeddc.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T08:05:51Z" message: 'load-balancer-api-external: tcp connection to a9d41ff4a38f84d1f98155c28e0a0441-8a6f4b07a1cbeddc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.844441ms message: 'load-balancer-api-external: tcp connection to a9d41ff4a38f84d1f98155c28e0a0441-8a6f4b07a1cbeddc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:17:51Z" - latency: 9.823881ms message: 'load-balancer-api-external: resolved host name a9d41ff4a38f84d1f98155c28e0a0441-8a6f4b07a1cbeddc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:17:51Z" - latency: 4.618947ms message: 'load-balancer-api-external: tcp connection to a9d41ff4a38f84d1f98155c28e0a0441-8a6f4b07a1cbeddc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:16:51Z" - latency: 11.662995ms message: 'load-balancer-api-external: resolved host name a9d41ff4a38f84d1f98155c28e0a0441-8a6f4b07a1cbeddc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:16:51Z" - latency: 5.092874ms message: 'load-balancer-api-external: tcp connection to a9d41ff4a38f84d1f98155c28e0a0441-8a6f4b07a1cbeddc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:15:51Z" - latency: 6.90465ms message: 'load-balancer-api-external: resolved host name a9d41ff4a38f84d1f98155c28e0a0441-8a6f4b07a1cbeddc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:15:51Z" - latency: 4.746133ms message: 'load-balancer-api-external: tcp connection to a9d41ff4a38f84d1f98155c28e0a0441-8a6f4b07a1cbeddc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:14:51Z" - latency: 10.28133ms message: 'load-balancer-api-external: resolved host name a9d41ff4a38f84d1f98155c28e0a0441-8a6f4b07a1cbeddc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:14:51Z" - latency: 4.948372ms message: 'load-balancer-api-external: tcp connection to a9d41ff4a38f84d1f98155c28e0a0441-8a6f4b07a1cbeddc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:13:51Z" - latency: 16.561105ms message: 'load-balancer-api-external: resolved host name a9d41ff4a38f84d1f98155c28e0a0441-8a6f4b07a1cbeddc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:13:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T07:59:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-45-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-45.ec2.internal uid: ab8b9e0d-a695-4f9c-bb10-ea93f9ca3275 resourceVersion: "21561" uid: 965c4d9c-9905-41b8-b390-3a7c67560684 spec: sourcePod: network-check-source-8894fc9bd-4d2hp targetEndpoint: a9d41ff4a38f84d1f98155c28e0a0441-8a6f4b07a1cbeddc.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T08:05:51Z" message: 'load-balancer-api-internal: tcp connection to a9d41ff4a38f84d1f98155c28e0a0441-8a6f4b07a1cbeddc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.681751ms message: 'load-balancer-api-internal: tcp connection to a9d41ff4a38f84d1f98155c28e0a0441-8a6f4b07a1cbeddc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:17:51Z" - latency: 9.7484ms message: 'load-balancer-api-internal: resolved host name a9d41ff4a38f84d1f98155c28e0a0441-8a6f4b07a1cbeddc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:17:51Z" - latency: 4.632991ms message: 'load-balancer-api-internal: tcp connection to a9d41ff4a38f84d1f98155c28e0a0441-8a6f4b07a1cbeddc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:16:51Z" - latency: 11.639924ms message: 'load-balancer-api-internal: resolved host name a9d41ff4a38f84d1f98155c28e0a0441-8a6f4b07a1cbeddc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:16:51Z" - latency: 5.103822ms message: 'load-balancer-api-internal: tcp connection to a9d41ff4a38f84d1f98155c28e0a0441-8a6f4b07a1cbeddc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:15:51Z" - latency: 6.932396ms message: 'load-balancer-api-internal: resolved host name a9d41ff4a38f84d1f98155c28e0a0441-8a6f4b07a1cbeddc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:15:51Z" - latency: 3.19967ms message: 'load-balancer-api-internal: tcp connection to a9d41ff4a38f84d1f98155c28e0a0441-8a6f4b07a1cbeddc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:14:51Z" - latency: 10.248007ms message: 'load-balancer-api-internal: resolved host name a9d41ff4a38f84d1f98155c28e0a0441-8a6f4b07a1cbeddc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:14:51Z" - latency: 4.966276ms message: 'load-balancer-api-internal: tcp connection to a9d41ff4a38f84d1f98155c28e0a0441-8a6f4b07a1cbeddc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:13:51Z" - latency: 16.449277ms message: 'load-balancer-api-internal: resolved host name a9d41ff4a38f84d1f98155c28e0a0441-8a6f4b07a1cbeddc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:13:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T07:59:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-45-to-network-check-target-ip-10-0-132-178 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-45.ec2.internal uid: ab8b9e0d-a695-4f9c-bb10-ea93f9ca3275 resourceVersion: "19517" uid: 96228268-2ca1-4cb4-ae47-8c031f5ed0f6 spec: sourcePod: network-check-source-8894fc9bd-4d2hp targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-17T08:06:51Z" message: 'network-check-target-ip-10-0-132-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.108725ms message: 'network-check-target-ip-10-0-132-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:13:51Z" - latency: 1.811616ms message: 'network-check-target-ip-10-0-132-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:12:51Z" - latency: 2.126676ms message: 'network-check-target-ip-10-0-132-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:11:51Z" - latency: 2.343987ms message: 'network-check-target-ip-10-0-132-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:10:51Z" - latency: 2.208191ms message: 'network-check-target-ip-10-0-132-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:09:51Z" - latency: 2.027694ms message: 'network-check-target-ip-10-0-132-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:08:51Z" - latency: 2.636627ms message: 'network-check-target-ip-10-0-132-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:07:51Z" - latency: 2.029273ms message: 'network-check-target-ip-10-0-132-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:06:51Z" - latency: 1.950218ms message: 'network-check-target-ip-10-0-132-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:05:51Z" - latency: 2.104601ms message: 'network-check-target-ip-10-0-132-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:04:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T07:59:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-45-to-network-check-target-ip-10-0-133-228 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-45.ec2.internal uid: ab8b9e0d-a695-4f9c-bb10-ea93f9ca3275 resourceVersion: "19518" uid: c324b6ce-3b3f-49fa-a153-33f433bfcdad spec: sourcePod: network-check-source-8894fc9bd-4d2hp targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-17T08:06:51Z" message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.060485ms message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:13:51Z" - latency: 2.532538ms message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:12:51Z" - latency: 2.34883ms message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:11:51Z" - latency: 2.256599ms message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:10:51Z" - latency: 2.180483ms message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:09:51Z" - latency: 1.984969ms message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:08:51Z" - latency: 1.929244ms message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:07:51Z" - latency: 2.333621ms message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:06:51Z" - latency: 2.485152ms message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:05:51Z" - latency: 2.181023ms message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:04:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T07:59:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-45-to-network-check-target-ip-10-0-142-45 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-45.ec2.internal uid: ab8b9e0d-a695-4f9c-bb10-ea93f9ca3275 resourceVersion: "19516" uid: 58299a1f-0f7d-459e-985d-2dea0a88442b spec: sourcePod: network-check-source-8894fc9bd-4d2hp targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-17T08:06:51Z" message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 781.165µs message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:13:51Z" - latency: 752.367µs message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:12:51Z" - latency: 911.824µs message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:11:51Z" - latency: 870.322µs message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:10:51Z" - latency: 810.189µs message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:09:51Z" - latency: 945.688µs message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:08:51Z" - latency: 738.123µs message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:07:51Z" - latency: 910.994µs message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:06:51Z" - latency: 827.014µs message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:05:51Z" - latency: 1.021605ms message: 'network-check-target-ip-10-0-142-45: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:04:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T07:59:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-45-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-45.ec2.internal uid: ab8b9e0d-a695-4f9c-bb10-ea93f9ca3275 resourceVersion: "21559" uid: 1acdc9e1-fbc0-47ad-be74-19874cdbba76 spec: sourcePod: network-check-source-8894fc9bd-4d2hp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-17T08:05:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.553241ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:17:51Z" - latency: 1.758109ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T08:17:51Z" - latency: 782.583µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:16:51Z" - latency: 1.656199ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T08:16:51Z" - latency: 1.081086ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:15:51Z" - latency: 1.765778ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T08:15:51Z" - latency: 867.324µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:14:51Z" - latency: 1.640204ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T08:14:51Z" - latency: 902.901µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:13:51Z" - latency: 1.841861ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T08:13:51Z" kind: List metadata: resourceVersion: ""