apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:07:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-167-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-167.ec2.internal uid: bf1d313a-20fd-4639-8959-76d7c8626e29 resourceVersion: "39521" uid: 78547147-3d43-4915-a62a-769dd2ce27e9 spec: sourcePod: network-check-source-7b678d77c7-k687t targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T18:14:49Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 886.148µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:03:49Z" - latency: 871.246µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:02:49Z" - latency: 843.493µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:01:49Z" - latency: 1.008123ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:00:49Z" - latency: 905.11µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:59:49Z" - latency: 912.43µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:58:49Z" - latency: 1.283457ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:57:49Z" - latency: 878.703µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:56:49Z" - latency: 888.359µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:55:49Z" - latency: 853.253µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:54:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:07:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-167-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-167.ec2.internal uid: bf1d313a-20fd-4639-8959-76d7c8626e29 resourceVersion: "38481" uid: 7c5440bc-a840-49b0-b44a-3326bd60e08a spec: sourcePod: network-check-source-7b678d77c7-k687t targetEndpoint: a79512b2485c14e01b69d82d845bc227-c4c05346f00d0e36.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T18:13:49Z" message: 'load-balancer-api-external: tcp connection to a79512b2485c14e01b69d82d845bc227-c4c05346f00d0e36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.957697ms message: 'load-balancer-api-external: tcp connection to a79512b2485c14e01b69d82d845bc227-c4c05346f00d0e36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:01:49Z" - latency: 8.312189ms message: 'load-balancer-api-external: resolved host name a79512b2485c14e01b69d82d845bc227-c4c05346f00d0e36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:01:49Z" - latency: 4.606687ms message: 'load-balancer-api-external: tcp connection to a79512b2485c14e01b69d82d845bc227-c4c05346f00d0e36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:00:49Z" - latency: 8.325559ms message: 'load-balancer-api-external: resolved host name a79512b2485c14e01b69d82d845bc227-c4c05346f00d0e36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:00:49Z" - latency: 5.159519ms message: 'load-balancer-api-external: tcp connection to a79512b2485c14e01b69d82d845bc227-c4c05346f00d0e36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:59:49Z" - latency: 7.428764ms message: 'load-balancer-api-external: resolved host name a79512b2485c14e01b69d82d845bc227-c4c05346f00d0e36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:59:49Z" - latency: 5.626932ms message: 'load-balancer-api-external: tcp connection to a79512b2485c14e01b69d82d845bc227-c4c05346f00d0e36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:58:49Z" - latency: 7.981946ms message: 'load-balancer-api-external: resolved host name a79512b2485c14e01b69d82d845bc227-c4c05346f00d0e36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:58:49Z" - latency: 4.41499ms message: 'load-balancer-api-external: tcp connection to a79512b2485c14e01b69d82d845bc227-c4c05346f00d0e36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:57:49Z" - latency: 7.241585ms message: 'load-balancer-api-external: resolved host name a79512b2485c14e01b69d82d845bc227-c4c05346f00d0e36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:57:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:07:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-167-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-167.ec2.internal uid: bf1d313a-20fd-4639-8959-76d7c8626e29 resourceVersion: "38482" uid: e9a534e5-d66b-4204-8c30-6234243579ab spec: sourcePod: network-check-source-7b678d77c7-k687t targetEndpoint: a79512b2485c14e01b69d82d845bc227-c4c05346f00d0e36.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T18:13:49Z" message: 'load-balancer-api-internal: tcp connection to a79512b2485c14e01b69d82d845bc227-c4c05346f00d0e36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.943621ms message: 'load-balancer-api-internal: tcp connection to a79512b2485c14e01b69d82d845bc227-c4c05346f00d0e36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:01:49Z" - latency: 8.450834ms message: 'load-balancer-api-internal: resolved host name a79512b2485c14e01b69d82d845bc227-c4c05346f00d0e36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:01:49Z" - latency: 4.816698ms message: 'load-balancer-api-internal: tcp connection to a79512b2485c14e01b69d82d845bc227-c4c05346f00d0e36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:00:49Z" - latency: 8.366814ms message: 'load-balancer-api-internal: resolved host name a79512b2485c14e01b69d82d845bc227-c4c05346f00d0e36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:00:49Z" - latency: 5.145186ms message: 'load-balancer-api-internal: tcp connection to a79512b2485c14e01b69d82d845bc227-c4c05346f00d0e36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:59:49Z" - latency: 7.622475ms message: 'load-balancer-api-internal: resolved host name a79512b2485c14e01b69d82d845bc227-c4c05346f00d0e36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:59:49Z" - latency: 5.999522ms message: 'load-balancer-api-internal: tcp connection to a79512b2485c14e01b69d82d845bc227-c4c05346f00d0e36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:58:49Z" - latency: 7.956874ms message: 'load-balancer-api-internal: resolved host name a79512b2485c14e01b69d82d845bc227-c4c05346f00d0e36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:58:49Z" - latency: 3.697856ms message: 'load-balancer-api-internal: tcp connection to a79512b2485c14e01b69d82d845bc227-c4c05346f00d0e36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:57:49Z" - latency: 7.25309ms message: 'load-balancer-api-internal: resolved host name a79512b2485c14e01b69d82d845bc227-c4c05346f00d0e36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:57:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:07:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-167-to-network-check-target-ip-10-0-131-193 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-167.ec2.internal uid: bf1d313a-20fd-4639-8959-76d7c8626e29 resourceVersion: "39520" uid: 87dcca8f-6cfb-48e9-b694-cdd5fdd70373 spec: sourcePod: network-check-source-7b678d77c7-k687t targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:14:49Z" message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.056575ms message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:03:49Z" - latency: 2.152974ms message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:02:49Z" - latency: 2.288525ms message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:01:49Z" - latency: 2.202563ms message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:00:49Z" - latency: 1.918543ms message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:59:49Z" - latency: 2.1732ms message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:58:49Z" - latency: 2.261422ms message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:57:49Z" - latency: 2.275075ms message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:56:49Z" - latency: 2.329057ms message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:55:49Z" - latency: 1.921763ms message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:54:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:07:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-167-to-network-check-target-ip-10-0-139-88 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-167.ec2.internal uid: bf1d313a-20fd-4639-8959-76d7c8626e29 resourceVersion: "39519" uid: 6b93bf57-195b-4d8e-98c2-c97a0a17e5d9 spec: sourcePod: network-check-source-7b678d77c7-k687t targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:14:49Z" message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.675499ms message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:03:49Z" - latency: 2.611321ms message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:02:49Z" - latency: 2.090503ms message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:01:49Z" - latency: 1.761921ms message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:00:49Z" - latency: 1.788524ms message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:59:49Z" - latency: 1.719775ms message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:58:49Z" - latency: 1.917777ms message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:57:49Z" - latency: 1.527412ms message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:56:49Z" - latency: 2.051403ms message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:55:49Z" - latency: 1.727917ms message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:54:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:07:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-167-to-network-check-target-ip-10-0-142-167 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-167.ec2.internal uid: bf1d313a-20fd-4639-8959-76d7c8626e29 resourceVersion: "39518" uid: 552e97d9-91e9-4845-9a59-65ca5a8b2dfb spec: sourcePod: network-check-source-7b678d77c7-k687t targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:14:49Z" message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 839.196µs message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:03:49Z" - latency: 884.188µs message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:02:49Z" - latency: 927.838µs message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:01:49Z" - latency: 989.864µs message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:00:49Z" - latency: 791.103µs message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:59:49Z" - latency: 1.237836ms message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:58:49Z" - latency: 1.585853ms message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:57:49Z" - latency: 1.505728ms message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:56:49Z" - latency: 872.692µs message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:55:49Z" - latency: 856.024µs message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:54:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:07:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-167-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-167.ec2.internal uid: bf1d313a-20fd-4639-8959-76d7c8626e29 resourceVersion: "38480" uid: bf4e9bb3-24a4-4121-b090-90ed029a3f63 spec: sourcePod: network-check-source-7b678d77c7-k687t targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T18:13:49Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 696.247µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:01:49Z" - latency: 2.519328ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:01:49Z" - latency: 871.095µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:00:49Z" - latency: 1.700058ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:00:49Z" - latency: 1.002359ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:59:49Z" - latency: 1.528525ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:59:49Z" - latency: 1.008563ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:58:49Z" - latency: 1.543312ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:58:49Z" - latency: 1.149114ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:57:49Z" - latency: 1.744587ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:57:49Z" kind: List metadata: resourceVersion: ""