apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T13:11:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-73-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-73.ec2.internal uid: aca94dc3-a6de-458f-a319-a4ac10cb987e resourceVersion: "62921" uid: 29ceafaa-9839-41d0-a786-b19de028ae8b spec: sourcePod: network-check-source-7bc5b6bf85-89t96 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-23T13:18:44Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 889.83µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:53:44Z" - latency: 1.399477ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:52:44Z" - latency: 1.435135ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:51:44Z" - latency: 969.43µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:50:44Z" - latency: 997.124µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:49:44Z" - latency: 998.298µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:48:44Z" - latency: 836.902µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:47:44Z" - latency: 1.03987ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:46:44Z" - latency: 1.060805ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:45:44Z" - latency: 1.231796ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:44:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T13:11:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-73-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-73.ec2.internal uid: aca94dc3-a6de-458f-a319-a4ac10cb987e resourceVersion: "62923" uid: bad96316-fbc3-40f1-b832-0e36c5aaeacb spec: sourcePod: network-check-source-7bc5b6bf85-89t96 targetEndpoint: a332b9f589345449c99d4f7cc3cb5bde-41f5b731469d784c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T13:17:44Z" message: 'load-balancer-api-external: tcp connection to a332b9f589345449c99d4f7cc3cb5bde-41f5b731469d784c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.471715ms message: 'load-balancer-api-external: tcp connection to a332b9f589345449c99d4f7cc3cb5bde-41f5b731469d784c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:53:44Z" - latency: 10.128829ms message: 'load-balancer-api-external: resolved host name a332b9f589345449c99d4f7cc3cb5bde-41f5b731469d784c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T13:53:44Z" - latency: 4.077696ms message: 'load-balancer-api-external: tcp connection to a332b9f589345449c99d4f7cc3cb5bde-41f5b731469d784c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:52:44Z" - latency: 8.105288ms message: 'load-balancer-api-external: resolved host name a332b9f589345449c99d4f7cc3cb5bde-41f5b731469d784c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T13:52:44Z" - latency: 4.636035ms message: 'load-balancer-api-external: tcp connection to a332b9f589345449c99d4f7cc3cb5bde-41f5b731469d784c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:51:44Z" - latency: 8.803904ms message: 'load-balancer-api-external: resolved host name a332b9f589345449c99d4f7cc3cb5bde-41f5b731469d784c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T13:51:44Z" - latency: 6.362068ms message: 'load-balancer-api-external: tcp connection to a332b9f589345449c99d4f7cc3cb5bde-41f5b731469d784c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:50:44Z" - latency: 8.370148ms message: 'load-balancer-api-external: resolved host name a332b9f589345449c99d4f7cc3cb5bde-41f5b731469d784c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T13:50:44Z" - latency: 3.619419ms message: 'load-balancer-api-external: tcp connection to a332b9f589345449c99d4f7cc3cb5bde-41f5b731469d784c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:49:44Z" - latency: 10.283087ms message: 'load-balancer-api-external: resolved host name a332b9f589345449c99d4f7cc3cb5bde-41f5b731469d784c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T13:49:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T13:11:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-73-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-73.ec2.internal uid: aca94dc3-a6de-458f-a319-a4ac10cb987e resourceVersion: "62922" uid: 6f81763b-239b-4ccb-8534-6de55681a029 spec: sourcePod: network-check-source-7bc5b6bf85-89t96 targetEndpoint: a332b9f589345449c99d4f7cc3cb5bde-41f5b731469d784c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T13:17:44Z" message: 'load-balancer-api-internal: tcp connection to a332b9f589345449c99d4f7cc3cb5bde-41f5b731469d784c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.395359ms message: 'load-balancer-api-internal: tcp connection to a332b9f589345449c99d4f7cc3cb5bde-41f5b731469d784c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:53:44Z" - latency: 10.141806ms message: 'load-balancer-api-internal: resolved host name a332b9f589345449c99d4f7cc3cb5bde-41f5b731469d784c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T13:53:44Z" - latency: 4.078508ms message: 'load-balancer-api-internal: tcp connection to a332b9f589345449c99d4f7cc3cb5bde-41f5b731469d784c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:52:44Z" - latency: 8.134893ms message: 'load-balancer-api-internal: resolved host name a332b9f589345449c99d4f7cc3cb5bde-41f5b731469d784c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T13:52:44Z" - latency: 4.665434ms message: 'load-balancer-api-internal: tcp connection to a332b9f589345449c99d4f7cc3cb5bde-41f5b731469d784c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:51:44Z" - latency: 8.767981ms message: 'load-balancer-api-internal: resolved host name a332b9f589345449c99d4f7cc3cb5bde-41f5b731469d784c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T13:51:44Z" - latency: 5.643092ms message: 'load-balancer-api-internal: tcp connection to a332b9f589345449c99d4f7cc3cb5bde-41f5b731469d784c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:50:44Z" - latency: 8.47118ms message: 'load-balancer-api-internal: resolved host name a332b9f589345449c99d4f7cc3cb5bde-41f5b731469d784c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T13:50:44Z" - latency: 4.800092ms message: 'load-balancer-api-internal: tcp connection to a332b9f589345449c99d4f7cc3cb5bde-41f5b731469d784c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:49:44Z" - latency: 10.300025ms message: 'load-balancer-api-internal: resolved host name a332b9f589345449c99d4f7cc3cb5bde-41f5b731469d784c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T13:49:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T13:11:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-73-to-network-check-target-ip-10-0-128-48 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-73.ec2.internal uid: aca94dc3-a6de-458f-a319-a4ac10cb987e resourceVersion: "62916" uid: 4a743f74-af3c-44e7-9a1a-f752fff8259e spec: sourcePod: network-check-source-7bc5b6bf85-89t96 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-23T13:18:44Z" message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.249808ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:53:44Z" - latency: 2.614871ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:52:44Z" - latency: 2.103133ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:51:44Z" - latency: 2.152365ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:50:44Z" - latency: 2.278743ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:49:44Z" - latency: 2.403886ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:48:44Z" - latency: 1.876084ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:47:44Z" - latency: 2.55111ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:46:44Z" - latency: 2.274775ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:45:44Z" - latency: 2.182351ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:44:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T13:11:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-73-to-network-check-target-ip-10-0-130-1 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-73.ec2.internal uid: aca94dc3-a6de-458f-a319-a4ac10cb987e resourceVersion: "62917" uid: e6d0d761-c260-4025-bfd6-cf95d430d3a7 spec: sourcePod: network-check-source-7bc5b6bf85-89t96 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-23T13:18:44Z" message: 'network-check-target-ip-10-0-130-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.425444ms message: 'network-check-target-ip-10-0-130-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:53:44Z" - latency: 2.377122ms message: 'network-check-target-ip-10-0-130-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:52:44Z" - latency: 2.438874ms message: 'network-check-target-ip-10-0-130-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:51:44Z" - latency: 2.393104ms message: 'network-check-target-ip-10-0-130-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:50:44Z" - latency: 2.413281ms message: 'network-check-target-ip-10-0-130-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:49:44Z" - latency: 2.34218ms message: 'network-check-target-ip-10-0-130-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:48:44Z" - latency: 2.317759ms message: 'network-check-target-ip-10-0-130-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:47:44Z" - latency: 2.558571ms message: 'network-check-target-ip-10-0-130-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:46:44Z" - latency: 2.369137ms message: 'network-check-target-ip-10-0-130-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:45:44Z" - latency: 2.794004ms message: 'network-check-target-ip-10-0-130-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:44:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T13:11:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-73-to-network-check-target-ip-10-0-132-73 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-73.ec2.internal uid: aca94dc3-a6de-458f-a319-a4ac10cb987e resourceVersion: "62918" uid: 6d99a730-0128-40c3-acdc-980d00d80330 spec: sourcePod: network-check-source-7bc5b6bf85-89t96 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-23T13:18:44Z" message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.118744ms message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:53:44Z" - latency: 1.076393ms message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:52:44Z" - latency: 1.651821ms message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:51:44Z" - latency: 1.056974ms message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:50:44Z" - latency: 1.10933ms message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:49:44Z" - latency: 1.045861ms message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:48:44Z" - latency: 972.714µs message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:47:44Z" - latency: 940.364µs message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:46:44Z" - latency: 1.200128ms message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:45:44Z" - latency: 1.397267ms message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:44:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T13:11:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-73-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-73.ec2.internal uid: aca94dc3-a6de-458f-a319-a4ac10cb987e resourceVersion: "62920" uid: c4965628-ce6f-4871-be83-f46fee580f17 spec: sourcePod: network-check-source-7bc5b6bf85-89t96 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-23T13:17:44Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.008772ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:53:44Z" - latency: 2.489477ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T13:53:44Z" - latency: 974.512µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:52:44Z" - latency: 1.784196ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T13:52:44Z" - latency: 989.512µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:51:44Z" - latency: 1.906331ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T13:51:44Z" - latency: 1.203968ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:50:44Z" - latency: 2.076656ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T13:50:44Z" - latency: 1.210231ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T13:49:44Z" - latency: 1.997387ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T13:49:44Z" kind: List metadata: resourceVersion: ""