apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T20:28:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-26-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-26.ec2.internal uid: d2f7e1d0-3d13-499d-9b01-ceb364762362 resourceVersion: "69446" uid: b90a3c50-07f8-4ad4-938b-c80fcc2388e3 spec: sourcePod: network-check-source-7d88cb55d8-tl5xq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T20:35:13Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.012547ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:17:13Z" - latency: 1.334155ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:16:13Z" - latency: 924.761µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:15:13Z" - latency: 841.437µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:14:13Z" - latency: 1.323968ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:13:13Z" - latency: 923.159µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:12:13Z" - latency: 1.138942ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:11:13Z" - latency: 973.442µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:10:13Z" - latency: 962.561µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:09:13Z" - latency: 1.241574ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:08:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T20:28:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-26-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-26.ec2.internal uid: d2f7e1d0-3d13-499d-9b01-ceb364762362 resourceVersion: "68258" uid: 65153033-a3dd-4d9d-9e63-828508a70595 spec: sourcePod: network-check-source-7d88cb55d8-tl5xq targetEndpoint: a094f9dba5a654f1f836c9dc2eaacd46-959f6a57cd1c64e5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T20:34:14Z" message: 'load-balancer-api-external: tcp connection to a094f9dba5a654f1f836c9dc2eaacd46-959f6a57cd1c64e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.014374ms message: 'load-balancer-api-external: tcp connection to a094f9dba5a654f1f836c9dc2eaacd46-959f6a57cd1c64e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:16:13Z" - latency: 7.187917ms message: 'load-balancer-api-external: resolved host name a094f9dba5a654f1f836c9dc2eaacd46-959f6a57cd1c64e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:16:13Z" - latency: 5.966092ms message: 'load-balancer-api-external: tcp connection to a094f9dba5a654f1f836c9dc2eaacd46-959f6a57cd1c64e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:15:13Z" - latency: 7.320747ms message: 'load-balancer-api-external: resolved host name a094f9dba5a654f1f836c9dc2eaacd46-959f6a57cd1c64e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:15:13Z" - latency: 3.8084ms message: 'load-balancer-api-external: tcp connection to a094f9dba5a654f1f836c9dc2eaacd46-959f6a57cd1c64e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:14:13Z" - latency: 6.978318ms message: 'load-balancer-api-external: resolved host name a094f9dba5a654f1f836c9dc2eaacd46-959f6a57cd1c64e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:14:13Z" - latency: 5.17426ms message: 'load-balancer-api-external: tcp connection to a094f9dba5a654f1f836c9dc2eaacd46-959f6a57cd1c64e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:13:13Z" - latency: 8.297913ms message: 'load-balancer-api-external: resolved host name a094f9dba5a654f1f836c9dc2eaacd46-959f6a57cd1c64e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:13:13Z" - latency: 6.367195ms message: 'load-balancer-api-external: tcp connection to a094f9dba5a654f1f836c9dc2eaacd46-959f6a57cd1c64e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:12:13Z" - latency: 7.254678ms message: 'load-balancer-api-external: resolved host name a094f9dba5a654f1f836c9dc2eaacd46-959f6a57cd1c64e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:12:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T20:28:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-26-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-26.ec2.internal uid: d2f7e1d0-3d13-499d-9b01-ceb364762362 resourceVersion: "68257" uid: cb0c34f4-20fc-47e3-868e-219d6318a586 spec: sourcePod: network-check-source-7d88cb55d8-tl5xq targetEndpoint: a094f9dba5a654f1f836c9dc2eaacd46-959f6a57cd1c64e5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T20:34:13Z" message: 'load-balancer-api-internal: tcp connection to a094f9dba5a654f1f836c9dc2eaacd46-959f6a57cd1c64e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.001465ms message: 'load-balancer-api-internal: tcp connection to a094f9dba5a654f1f836c9dc2eaacd46-959f6a57cd1c64e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:16:13Z" - latency: 7.260819ms message: 'load-balancer-api-internal: resolved host name a094f9dba5a654f1f836c9dc2eaacd46-959f6a57cd1c64e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:16:13Z" - latency: 5.564728ms message: 'load-balancer-api-internal: tcp connection to a094f9dba5a654f1f836c9dc2eaacd46-959f6a57cd1c64e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:15:13Z" - latency: 7.343743ms message: 'load-balancer-api-internal: resolved host name a094f9dba5a654f1f836c9dc2eaacd46-959f6a57cd1c64e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:15:13Z" - latency: 4.472211ms message: 'load-balancer-api-internal: tcp connection to a094f9dba5a654f1f836c9dc2eaacd46-959f6a57cd1c64e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:14:13Z" - latency: 7.05425ms message: 'load-balancer-api-internal: resolved host name a094f9dba5a654f1f836c9dc2eaacd46-959f6a57cd1c64e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:14:13Z" - latency: 5.105966ms message: 'load-balancer-api-internal: tcp connection to a094f9dba5a654f1f836c9dc2eaacd46-959f6a57cd1c64e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:13:13Z" - latency: 8.255004ms message: 'load-balancer-api-internal: resolved host name a094f9dba5a654f1f836c9dc2eaacd46-959f6a57cd1c64e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:13:13Z" - latency: 4.610346ms message: 'load-balancer-api-internal: tcp connection to a094f9dba5a654f1f836c9dc2eaacd46-959f6a57cd1c64e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:12:13Z" - latency: 7.067928ms message: 'load-balancer-api-internal: resolved host name a094f9dba5a654f1f836c9dc2eaacd46-959f6a57cd1c64e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:12:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T20:28:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-26-to-network-check-target-ip-10-0-136-118 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-26.ec2.internal uid: d2f7e1d0-3d13-499d-9b01-ceb364762362 resourceVersion: "69445" uid: 86d36d24-45dd-4a65-8033-a27ccc297865 spec: sourcePod: network-check-source-7d88cb55d8-tl5xq targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T20:35:13Z" message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.627961ms message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:17:13Z" - latency: 2.244523ms message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:16:13Z" - latency: 2.178753ms message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:15:13Z" - latency: 2.171466ms message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:14:13Z" - latency: 2.390664ms message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:13:13Z" - latency: 2.15235ms message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:12:13Z" - latency: 2.13755ms message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:11:13Z" - latency: 1.92431ms message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:10:13Z" - latency: 2.229373ms message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:09:13Z" - latency: 2.245043ms message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:08:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T20:28:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-26-to-network-check-target-ip-10-0-137-26 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-26.ec2.internal uid: d2f7e1d0-3d13-499d-9b01-ceb364762362 resourceVersion: "69443" uid: b74523a4-d2fc-4901-8fb5-010a8bd49370 spec: sourcePod: network-check-source-7d88cb55d8-tl5xq targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T20:35:13Z" message: 'network-check-target-ip-10-0-137-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 993.062µs message: 'network-check-target-ip-10-0-137-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:17:13Z" - latency: 1.024835ms message: 'network-check-target-ip-10-0-137-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:16:13Z" - latency: 1.142849ms message: 'network-check-target-ip-10-0-137-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:15:13Z" - latency: 1.057987ms message: 'network-check-target-ip-10-0-137-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:14:13Z" - latency: 1.106406ms message: 'network-check-target-ip-10-0-137-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:13:13Z" - latency: 1.359918ms message: 'network-check-target-ip-10-0-137-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:12:13Z" - latency: 953.735µs message: 'network-check-target-ip-10-0-137-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:11:13Z" - latency: 986.255µs message: 'network-check-target-ip-10-0-137-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:10:13Z" - latency: 900.481µs message: 'network-check-target-ip-10-0-137-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:09:13Z" - latency: 867.542µs message: 'network-check-target-ip-10-0-137-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:08:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T20:28:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-26-to-network-check-target-ip-10-0-139-131 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-26.ec2.internal uid: d2f7e1d0-3d13-499d-9b01-ceb364762362 resourceVersion: "69444" uid: d6882849-d96b-49e9-8669-960f1f498a85 spec: sourcePod: network-check-source-7d88cb55d8-tl5xq targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T20:35:13Z" message: 'network-check-target-ip-10-0-139-131: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.442001ms message: 'network-check-target-ip-10-0-139-131: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:17:13Z" - latency: 2.586563ms message: 'network-check-target-ip-10-0-139-131: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:16:13Z" - latency: 2.498823ms message: 'network-check-target-ip-10-0-139-131: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:15:13Z" - latency: 2.560489ms message: 'network-check-target-ip-10-0-139-131: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:14:13Z" - latency: 2.828694ms message: 'network-check-target-ip-10-0-139-131: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:13:13Z" - latency: 2.262951ms message: 'network-check-target-ip-10-0-139-131: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:12:13Z" - latency: 2.510591ms message: 'network-check-target-ip-10-0-139-131: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:11:13Z" - latency: 2.450437ms message: 'network-check-target-ip-10-0-139-131: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:10:13Z" - latency: 2.27952ms message: 'network-check-target-ip-10-0-139-131: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:09:13Z" - latency: 2.537131ms message: 'network-check-target-ip-10-0-139-131: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:08:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T20:28:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-26-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-26.ec2.internal uid: d2f7e1d0-3d13-499d-9b01-ceb364762362 resourceVersion: "68256" uid: 4b79bf7f-706f-4b85-9ee4-c88de27d550f spec: sourcePod: network-check-source-7d88cb55d8-tl5xq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T20:34:13Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.068261ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:16:13Z" - latency: 1.70981ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T21:16:13Z" - latency: 841.939µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:15:13Z" - latency: 1.770107ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T21:15:13Z" - latency: 1.200544ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:14:13Z" - latency: 1.771642ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T21:14:13Z" - latency: 1.099999ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:13:13Z" - latency: 1.906966ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T21:13:13Z" - latency: 966.534µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:12:13Z" - latency: 2.239062ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T21:12:13Z" kind: List metadata: resourceVersion: ""