apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:50:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-58-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-58.ec2.internal uid: 5de32421-657f-4cf3-b1db-dc4e3bd15415 resourceVersion: "32994" uid: bf0511cd-aedd-4714-88a0-313c0bc02704 spec: sourcePod: network-check-source-7b678d77c7-2sdvm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T16:57:39Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.014178ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:11:39Z" - latency: 973.173µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:10:39Z" - latency: 717.868µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:09:39Z" - latency: 1.065929ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:08:39Z" - latency: 1.378829ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:07:39Z" - latency: 975.044µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:06:39Z" - latency: 1.01843ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:05:39Z" - latency: 1.73619ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:04:39Z" - latency: 895.681µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:03:39Z" - latency: 1.252248ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:02:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:50:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-58-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-58.ec2.internal uid: 5de32421-657f-4cf3-b1db-dc4e3bd15415 resourceVersion: "35655" uid: 04a226bc-c034-4313-b6d1-b9b9294616ea spec: sourcePod: network-check-source-7b678d77c7-2sdvm targetEndpoint: a331edfc6d7f747b3b01561fabb5f526-e8c835292b285b4a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T16:56:39Z" message: 'load-balancer-api-external: tcp connection to a331edfc6d7f747b3b01561fabb5f526-e8c835292b285b4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.163631ms message: 'load-balancer-api-external: tcp connection to a331edfc6d7f747b3b01561fabb5f526-e8c835292b285b4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:14:39Z" - latency: 6.549666ms message: 'load-balancer-api-external: resolved host name a331edfc6d7f747b3b01561fabb5f526-e8c835292b285b4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:14:39Z" - latency: 4.055994ms message: 'load-balancer-api-external: tcp connection to a331edfc6d7f747b3b01561fabb5f526-e8c835292b285b4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:13:39Z" - latency: 6.970753ms message: 'load-balancer-api-external: resolved host name a331edfc6d7f747b3b01561fabb5f526-e8c835292b285b4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:13:39Z" - latency: 5.896552ms message: 'load-balancer-api-external: tcp connection to a331edfc6d7f747b3b01561fabb5f526-e8c835292b285b4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:12:39Z" - latency: 6.81725ms message: 'load-balancer-api-external: resolved host name a331edfc6d7f747b3b01561fabb5f526-e8c835292b285b4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:12:39Z" - latency: 5.235278ms message: 'load-balancer-api-external: tcp connection to a331edfc6d7f747b3b01561fabb5f526-e8c835292b285b4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:11:39Z" - latency: 6.967045ms message: 'load-balancer-api-external: resolved host name a331edfc6d7f747b3b01561fabb5f526-e8c835292b285b4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:11:39Z" - latency: 4.971221ms message: 'load-balancer-api-external: tcp connection to a331edfc6d7f747b3b01561fabb5f526-e8c835292b285b4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:10:39Z" - latency: 8.076084ms message: 'load-balancer-api-external: resolved host name a331edfc6d7f747b3b01561fabb5f526-e8c835292b285b4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:10:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:50:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-58-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-58.ec2.internal uid: 5de32421-657f-4cf3-b1db-dc4e3bd15415 resourceVersion: "35654" uid: 89119dc4-dab9-495b-a55d-df44c3983089 spec: sourcePod: network-check-source-7b678d77c7-2sdvm targetEndpoint: a331edfc6d7f747b3b01561fabb5f526-e8c835292b285b4a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T16:56:39Z" message: 'load-balancer-api-internal: tcp connection to a331edfc6d7f747b3b01561fabb5f526-e8c835292b285b4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.602019ms message: 'load-balancer-api-internal: tcp connection to a331edfc6d7f747b3b01561fabb5f526-e8c835292b285b4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:14:39Z" - latency: 6.423868ms message: 'load-balancer-api-internal: resolved host name a331edfc6d7f747b3b01561fabb5f526-e8c835292b285b4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:14:39Z" - latency: 3.21131ms message: 'load-balancer-api-internal: tcp connection to a331edfc6d7f747b3b01561fabb5f526-e8c835292b285b4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:13:39Z" - latency: 7.031648ms message: 'load-balancer-api-internal: resolved host name a331edfc6d7f747b3b01561fabb5f526-e8c835292b285b4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:13:39Z" - latency: 5.197828ms message: 'load-balancer-api-internal: tcp connection to a331edfc6d7f747b3b01561fabb5f526-e8c835292b285b4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:12:39Z" - latency: 6.997359ms message: 'load-balancer-api-internal: resolved host name a331edfc6d7f747b3b01561fabb5f526-e8c835292b285b4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:12:39Z" - latency: 5.272508ms message: 'load-balancer-api-internal: tcp connection to a331edfc6d7f747b3b01561fabb5f526-e8c835292b285b4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:11:39Z" - latency: 7.061427ms message: 'load-balancer-api-internal: resolved host name a331edfc6d7f747b3b01561fabb5f526-e8c835292b285b4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:11:39Z" - latency: 4.860375ms message: 'load-balancer-api-internal: tcp connection to a331edfc6d7f747b3b01561fabb5f526-e8c835292b285b4a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:10:39Z" - latency: 8.284457ms message: 'load-balancer-api-internal: resolved host name a331edfc6d7f747b3b01561fabb5f526-e8c835292b285b4a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:10:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:50:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-58-to-network-check-target-ip-10-0-137-126 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-58.ec2.internal uid: 5de32421-657f-4cf3-b1db-dc4e3bd15415 resourceVersion: "32993" uid: 5d77ab81-934e-4b18-8aed-3d90932d8af2 spec: sourcePod: network-check-source-7b678d77c7-2sdvm targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T16:57:39Z" message: 'network-check-target-ip-10-0-137-126: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.195261ms message: 'network-check-target-ip-10-0-137-126: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:11:39Z" - latency: 3.221933ms message: 'network-check-target-ip-10-0-137-126: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:10:39Z" - latency: 1.531543ms message: 'network-check-target-ip-10-0-137-126: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:09:39Z" - latency: 2.387865ms message: 'network-check-target-ip-10-0-137-126: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:08:39Z" - latency: 2.353196ms message: 'network-check-target-ip-10-0-137-126: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:07:39Z" - latency: 2.213974ms message: 'network-check-target-ip-10-0-137-126: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:06:39Z" - latency: 1.890103ms message: 'network-check-target-ip-10-0-137-126: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:05:39Z" - latency: 2.073717ms message: 'network-check-target-ip-10-0-137-126: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:04:39Z" - latency: 2.143655ms message: 'network-check-target-ip-10-0-137-126: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:03:39Z" - latency: 2.216586ms message: 'network-check-target-ip-10-0-137-126: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:02:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:50:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-58-to-network-check-target-ip-10-0-138-58 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-58.ec2.internal uid: 5de32421-657f-4cf3-b1db-dc4e3bd15415 resourceVersion: "32992" uid: 79e79e91-695d-47d4-9263-58049d4f98bf spec: sourcePod: network-check-source-7b678d77c7-2sdvm targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T16:57:39Z" message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.037478ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:11:39Z" - latency: 894.697µs message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:10:39Z" - latency: 751.713µs message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:09:39Z" - latency: 942.314µs message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:08:39Z" - latency: 945.619µs message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:07:39Z" - latency: 1.527978ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:06:39Z" - latency: 743.312µs message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:05:39Z" - latency: 774.428µs message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:04:39Z" - latency: 713.429µs message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:03:39Z" - latency: 937.473µs message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:02:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:50:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-58-to-network-check-target-ip-10-0-143-10 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-58.ec2.internal uid: 5de32421-657f-4cf3-b1db-dc4e3bd15415 resourceVersion: "32991" uid: 292ff515-c1f5-4724-9f34-630b3eea0d56 spec: sourcePod: network-check-source-7b678d77c7-2sdvm targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T16:57:39Z" message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.906467ms message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:11:39Z" - latency: 2.003226ms message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:10:39Z" - latency: 1.425922ms message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:09:39Z" - latency: 1.817878ms message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:08:39Z" - latency: 1.919887ms message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:07:39Z" - latency: 1.463457ms message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:06:39Z" - latency: 1.928513ms message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:05:39Z" - latency: 1.671544ms message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:04:39Z" - latency: 6.897381ms message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:03:39Z" - latency: 1.89204ms message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:02:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:50:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-58-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-58.ec2.internal uid: 5de32421-657f-4cf3-b1db-dc4e3bd15415 resourceVersion: "35653" uid: 6f11ebd2-d021-43af-808d-34810e0db7db spec: sourcePod: network-check-source-7b678d77c7-2sdvm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T16:56:39Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.091283ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:14:39Z" - latency: 1.648817ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:14:39Z" - latency: 849.289µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:13:39Z" - latency: 1.780533ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:13:39Z" - latency: 948.89µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:12:39Z" - latency: 2.147367ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:12:39Z" - latency: 835.276µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:11:39Z" - latency: 1.981025ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:11:39Z" - latency: 976.383µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:10:39Z" - latency: 3.211021ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:10:39Z" kind: List metadata: resourceVersion: ""