apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T15:08:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-198-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-198.ec2.internal uid: 699c6dd6-4b4d-4b92-af9f-99429bf9fdae resourceVersion: "43966" uid: f66d28ff-eee6-4eb4-a840-1dbde18ddd26 spec: sourcePod: network-check-source-8894fc9bd-qpn6s targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-20T15:15:05Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.343091ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:36:05Z" - latency: 771.545µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:35:05Z" - latency: 989.625µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:34:05Z" - latency: 832.192µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:33:05Z" - latency: 869.09µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:32:05Z" - latency: 1.031503ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:31:05Z" - latency: 772.91µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:30:05Z" - latency: 830.095µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:29:05Z" - latency: 764.526µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:28:05Z" - latency: 813.328µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:27:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T15:08:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-198-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-198.ec2.internal uid: 699c6dd6-4b4d-4b92-af9f-99429bf9fdae resourceVersion: "46051" uid: f8b1c7a7-6c40-4fb8-a081-ffcd895e235c spec: sourcePod: network-check-source-8894fc9bd-qpn6s targetEndpoint: ac106f8770b4c4f3facba2ebd3dc32b2-9cb2f21fbf22731e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-20T15:14:05Z" message: 'load-balancer-api-external: tcp connection to ac106f8770b4c4f3facba2ebd3dc32b2-9cb2f21fbf22731e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.084498ms message: 'load-balancer-api-external: tcp connection to ac106f8770b4c4f3facba2ebd3dc32b2-9cb2f21fbf22731e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:38:05Z" - latency: 13.146658ms message: 'load-balancer-api-external: resolved host name ac106f8770b4c4f3facba2ebd3dc32b2-9cb2f21fbf22731e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T15:38:05Z" - latency: 4.661589ms message: 'load-balancer-api-external: tcp connection to ac106f8770b4c4f3facba2ebd3dc32b2-9cb2f21fbf22731e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:37:05Z" - latency: 8.543002ms message: 'load-balancer-api-external: resolved host name ac106f8770b4c4f3facba2ebd3dc32b2-9cb2f21fbf22731e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T15:37:05Z" - latency: 4.882703ms message: 'load-balancer-api-external: tcp connection to ac106f8770b4c4f3facba2ebd3dc32b2-9cb2f21fbf22731e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:36:05Z" - latency: 8.632229ms message: 'load-balancer-api-external: resolved host name ac106f8770b4c4f3facba2ebd3dc32b2-9cb2f21fbf22731e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T15:36:05Z" - latency: 4.189549ms message: 'load-balancer-api-external: tcp connection to ac106f8770b4c4f3facba2ebd3dc32b2-9cb2f21fbf22731e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:35:05Z" - latency: 8.150656ms message: 'load-balancer-api-external: resolved host name ac106f8770b4c4f3facba2ebd3dc32b2-9cb2f21fbf22731e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T15:35:05Z" - latency: 3.824598ms message: 'load-balancer-api-external: tcp connection to ac106f8770b4c4f3facba2ebd3dc32b2-9cb2f21fbf22731e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:34:05Z" - latency: 18.973025ms message: 'load-balancer-api-external: resolved host name ac106f8770b4c4f3facba2ebd3dc32b2-9cb2f21fbf22731e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T15:34:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T15:08:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-198-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-198.ec2.internal uid: 699c6dd6-4b4d-4b92-af9f-99429bf9fdae resourceVersion: "46052" uid: bb2c6a7f-a825-47e3-8172-46b2e53a5e3c spec: sourcePod: network-check-source-8894fc9bd-qpn6s targetEndpoint: ac106f8770b4c4f3facba2ebd3dc32b2-9cb2f21fbf22731e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-20T15:14:05Z" message: 'load-balancer-api-internal: tcp connection to ac106f8770b4c4f3facba2ebd3dc32b2-9cb2f21fbf22731e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.067633ms message: 'load-balancer-api-internal: tcp connection to ac106f8770b4c4f3facba2ebd3dc32b2-9cb2f21fbf22731e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:38:05Z" - latency: 13.090728ms message: 'load-balancer-api-internal: resolved host name ac106f8770b4c4f3facba2ebd3dc32b2-9cb2f21fbf22731e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T15:38:05Z" - latency: 4.84339ms message: 'load-balancer-api-internal: tcp connection to ac106f8770b4c4f3facba2ebd3dc32b2-9cb2f21fbf22731e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:37:05Z" - latency: 8.456274ms message: 'load-balancer-api-internal: resolved host name ac106f8770b4c4f3facba2ebd3dc32b2-9cb2f21fbf22731e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T15:37:05Z" - latency: 4.854688ms message: 'load-balancer-api-internal: tcp connection to ac106f8770b4c4f3facba2ebd3dc32b2-9cb2f21fbf22731e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:36:05Z" - latency: 8.586601ms message: 'load-balancer-api-internal: resolved host name ac106f8770b4c4f3facba2ebd3dc32b2-9cb2f21fbf22731e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T15:36:05Z" - latency: 4.19352ms message: 'load-balancer-api-internal: tcp connection to ac106f8770b4c4f3facba2ebd3dc32b2-9cb2f21fbf22731e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:35:05Z" - latency: 8.077436ms message: 'load-balancer-api-internal: resolved host name ac106f8770b4c4f3facba2ebd3dc32b2-9cb2f21fbf22731e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T15:35:05Z" - latency: 4.946323ms message: 'load-balancer-api-internal: tcp connection to ac106f8770b4c4f3facba2ebd3dc32b2-9cb2f21fbf22731e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:34:05Z" - latency: 18.940888ms message: 'load-balancer-api-internal: resolved host name ac106f8770b4c4f3facba2ebd3dc32b2-9cb2f21fbf22731e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T15:34:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T15:08:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-198-to-network-check-target-ip-10-0-129-115 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-198.ec2.internal uid: 699c6dd6-4b4d-4b92-af9f-99429bf9fdae resourceVersion: "43965" uid: 2e873757-b558-43d3-a138-b5e2f196d32e spec: sourcePod: network-check-source-8894fc9bd-qpn6s targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-20T15:15:05Z" message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.809946ms message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:36:05Z" - latency: 2.785133ms message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:35:05Z" - latency: 2.248603ms message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:34:05Z" - latency: 2.355056ms message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:33:05Z" - latency: 1.931081ms message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:32:05Z" - latency: 2.47219ms message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:31:05Z" - latency: 2.209533ms message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:30:05Z" - latency: 2.102462ms message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:29:05Z" - latency: 2.17932ms message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:28:05Z" - latency: 2.049229ms message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:27:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T15:08:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-198-to-network-check-target-ip-10-0-133-198 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-198.ec2.internal uid: 699c6dd6-4b4d-4b92-af9f-99429bf9fdae resourceVersion: "43963" uid: 4e0ff07e-a9ed-4e30-bfc3-714608c1f206 spec: sourcePod: network-check-source-8894fc9bd-qpn6s targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-20T15:15:05Z" message: 'network-check-target-ip-10-0-133-198: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.928277ms message: 'network-check-target-ip-10-0-133-198: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:36:05Z" - latency: 729.925µs message: 'network-check-target-ip-10-0-133-198: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:35:05Z" - latency: 868.233µs message: 'network-check-target-ip-10-0-133-198: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:34:05Z" - latency: 871.629µs message: 'network-check-target-ip-10-0-133-198: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:33:05Z" - latency: 926.332µs message: 'network-check-target-ip-10-0-133-198: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:32:05Z" - latency: 1.228515ms message: 'network-check-target-ip-10-0-133-198: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:31:05Z" - latency: 809.187µs message: 'network-check-target-ip-10-0-133-198: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:30:05Z" - latency: 862.847µs message: 'network-check-target-ip-10-0-133-198: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:29:05Z" - latency: 1.17143ms message: 'network-check-target-ip-10-0-133-198: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:28:05Z" - latency: 874.86µs message: 'network-check-target-ip-10-0-133-198: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:27:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T15:08:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-198-to-network-check-target-ip-10-0-134-230 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-198.ec2.internal uid: 699c6dd6-4b4d-4b92-af9f-99429bf9fdae resourceVersion: "43964" uid: 54e63134-68cd-445c-ba97-15b6dd2e5134 spec: sourcePod: network-check-source-8894fc9bd-qpn6s targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-20T15:15:05Z" message: 'network-check-target-ip-10-0-134-230: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.232876ms message: 'network-check-target-ip-10-0-134-230: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:36:05Z" - latency: 2.809112ms message: 'network-check-target-ip-10-0-134-230: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:35:05Z" - latency: 2.223014ms message: 'network-check-target-ip-10-0-134-230: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:34:05Z" - latency: 2.98763ms message: 'network-check-target-ip-10-0-134-230: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:33:05Z" - latency: 2.030645ms message: 'network-check-target-ip-10-0-134-230: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:32:05Z" - latency: 2.356761ms message: 'network-check-target-ip-10-0-134-230: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:31:05Z" - latency: 2.142231ms message: 'network-check-target-ip-10-0-134-230: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:30:05Z" - latency: 2.279075ms message: 'network-check-target-ip-10-0-134-230: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:29:05Z" - latency: 2.211164ms message: 'network-check-target-ip-10-0-134-230: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:28:05Z" - latency: 1.997395ms message: 'network-check-target-ip-10-0-134-230: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:27:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T15:08:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-198-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-198.ec2.internal uid: 699c6dd6-4b4d-4b92-af9f-99429bf9fdae resourceVersion: "46050" uid: 76dfcc62-9bfc-49ff-975d-2f9e62fd316d spec: sourcePod: network-check-source-8894fc9bd-qpn6s targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-20T15:14:05Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 871.026µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:38:05Z" - latency: 2.440006ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T15:38:05Z" - latency: 905.04µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:37:05Z" - latency: 1.684128ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T15:37:05Z" - latency: 859.253µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:36:05Z" - latency: 2.086837ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T15:36:05Z" - latency: 635.157µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:35:05Z" - latency: 1.501498ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T15:35:05Z" - latency: 722.684µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:34:05Z" - latency: 1.714194ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T15:34:05Z" kind: List metadata: resourceVersion: ""