apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T13:10:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-36-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-36.us-east-2.compute.internal uid: b17c75fc-1164-4495-8b45-8de7754ca484 resourceVersion: "153740" uid: ff99583b-4c17-4d58-ac63-6d1af1b5a453 spec: sourcePod: network-check-source-6f78d59f99-jws95 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T13:18:00Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.103177ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:14:00Z" - latency: 1.467345ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:13:00Z" - latency: 904.155µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:12:00Z" - latency: 1.41623ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:11:00Z" - latency: 1.005411ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:10:00Z" - latency: 1.159059ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:09:00Z" - latency: 1.198377ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:08:00Z" - latency: 1.880789ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:07:00Z" - latency: 1.008115ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:06:00Z" - latency: 1.853979ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:05:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T13:10:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-36-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-36.us-east-2.compute.internal uid: b17c75fc-1164-4495-8b45-8de7754ca484 resourceVersion: "151154" uid: b585c233-b9b0-48dc-b4f4-90ed2bd974ea spec: sourcePod: network-check-source-6f78d59f99-jws95 targetEndpoint: a960f62e074784bac833fa1214e5ce3f-2ccd16abeeaffec3.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T13:17:00Z" message: 'load-balancer-api-external: tcp connection to a960f62e074784bac833fa1214e5ce3f-2ccd16abeeaffec3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.391801ms message: 'load-balancer-api-external: tcp connection to a960f62e074784bac833fa1214e5ce3f-2ccd16abeeaffec3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:11:00Z" - latency: 7.296228ms message: 'load-balancer-api-external: resolved host name a960f62e074784bac833fa1214e5ce3f-2ccd16abeeaffec3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T14:11:00Z" - latency: 4.78373ms message: 'load-balancer-api-external: tcp connection to a960f62e074784bac833fa1214e5ce3f-2ccd16abeeaffec3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:10:00Z" - latency: 8.365614ms message: 'load-balancer-api-external: resolved host name a960f62e074784bac833fa1214e5ce3f-2ccd16abeeaffec3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T14:10:00Z" - latency: 5.747865ms message: 'load-balancer-api-external: tcp connection to a960f62e074784bac833fa1214e5ce3f-2ccd16abeeaffec3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:09:00Z" - latency: 10.545867ms message: 'load-balancer-api-external: resolved host name a960f62e074784bac833fa1214e5ce3f-2ccd16abeeaffec3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T14:09:00Z" - latency: 5.883083ms message: 'load-balancer-api-external: tcp connection to a960f62e074784bac833fa1214e5ce3f-2ccd16abeeaffec3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:08:00Z" - latency: 6.241472ms message: 'load-balancer-api-external: resolved host name a960f62e074784bac833fa1214e5ce3f-2ccd16abeeaffec3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T14:08:00Z" - latency: 5.821786ms message: 'load-balancer-api-external: tcp connection to a960f62e074784bac833fa1214e5ce3f-2ccd16abeeaffec3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:07:00Z" - latency: 7.301282ms message: 'load-balancer-api-external: resolved host name a960f62e074784bac833fa1214e5ce3f-2ccd16abeeaffec3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T14:07:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T13:10:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-36-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-36.us-east-2.compute.internal uid: b17c75fc-1164-4495-8b45-8de7754ca484 resourceVersion: "151156" uid: 75d922b0-5066-492a-b6a1-2c280677477b spec: sourcePod: network-check-source-6f78d59f99-jws95 targetEndpoint: a960f62e074784bac833fa1214e5ce3f-2ccd16abeeaffec3.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T13:17:00Z" message: 'load-balancer-api-internal: tcp connection to a960f62e074784bac833fa1214e5ce3f-2ccd16abeeaffec3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 16.48362ms message: 'load-balancer-api-internal: tcp connection to a960f62e074784bac833fa1214e5ce3f-2ccd16abeeaffec3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:11:00Z" - latency: 7.21878ms message: 'load-balancer-api-internal: resolved host name a960f62e074784bac833fa1214e5ce3f-2ccd16abeeaffec3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T14:11:00Z" - latency: 4.739035ms message: 'load-balancer-api-internal: tcp connection to a960f62e074784bac833fa1214e5ce3f-2ccd16abeeaffec3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:10:00Z" - latency: 8.398849ms message: 'load-balancer-api-internal: resolved host name a960f62e074784bac833fa1214e5ce3f-2ccd16abeeaffec3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T14:10:00Z" - latency: 5.778338ms message: 'load-balancer-api-internal: tcp connection to a960f62e074784bac833fa1214e5ce3f-2ccd16abeeaffec3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:09:00Z" - latency: 10.462075ms message: 'load-balancer-api-internal: resolved host name a960f62e074784bac833fa1214e5ce3f-2ccd16abeeaffec3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T14:09:00Z" - latency: 5.936659ms message: 'load-balancer-api-internal: tcp connection to a960f62e074784bac833fa1214e5ce3f-2ccd16abeeaffec3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:08:00Z" - latency: 6.200033ms message: 'load-balancer-api-internal: resolved host name a960f62e074784bac833fa1214e5ce3f-2ccd16abeeaffec3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T14:08:00Z" - latency: 5.816597ms message: 'load-balancer-api-internal: tcp connection to a960f62e074784bac833fa1214e5ce3f-2ccd16abeeaffec3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:07:00Z" - latency: 7.347131ms message: 'load-balancer-api-internal: resolved host name a960f62e074784bac833fa1214e5ce3f-2ccd16abeeaffec3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T14:07:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T13:10:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-36-to-network-check-target-ip-10-0-131-36 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-36.us-east-2.compute.internal uid: b17c75fc-1164-4495-8b45-8de7754ca484 resourceVersion: "153739" uid: 4a3ffc60-e906-45f1-bcc7-3339b6d06a48 spec: sourcePod: network-check-source-6f78d59f99-jws95 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T13:18:00Z" message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.057096ms message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:14:00Z" - latency: 1.195301ms message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:13:00Z" - latency: 1.36002ms message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:12:00Z" - latency: 916.07µs message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:11:00Z" - latency: 1.059751ms message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:10:00Z" - latency: 1.575428ms message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:09:00Z" - latency: 1.665972ms message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:08:00Z" - latency: 880.251µs message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:07:00Z" - latency: 1.253985ms message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:06:00Z" - latency: 2.59188ms message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:05:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T13:10:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-36-to-network-check-target-ip-10-0-132-167 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-36.us-east-2.compute.internal uid: b17c75fc-1164-4495-8b45-8de7754ca484 resourceVersion: "153738" uid: 99c8a810-f80f-4e33-b85d-e473bb1dbf97 spec: sourcePod: network-check-source-6f78d59f99-jws95 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T13:18:00Z" message: 'network-check-target-ip-10-0-132-167: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.507591ms message: 'network-check-target-ip-10-0-132-167: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:14:00Z" - latency: 2.452346ms message: 'network-check-target-ip-10-0-132-167: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:13:00Z" - latency: 2.331755ms message: 'network-check-target-ip-10-0-132-167: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:12:00Z" - latency: 2.45361ms message: 'network-check-target-ip-10-0-132-167: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:11:00Z" - latency: 2.236622ms message: 'network-check-target-ip-10-0-132-167: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:10:00Z" - latency: 2.359562ms message: 'network-check-target-ip-10-0-132-167: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:09:00Z" - latency: 2.440078ms message: 'network-check-target-ip-10-0-132-167: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:08:00Z" - latency: 1.855045ms message: 'network-check-target-ip-10-0-132-167: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:07:00Z" - latency: 2.310763ms message: 'network-check-target-ip-10-0-132-167: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:06:00Z" - latency: 2.881951ms message: 'network-check-target-ip-10-0-132-167: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:05:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T13:10:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-36-to-network-check-target-ip-10-0-139-248 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-36.us-east-2.compute.internal uid: b17c75fc-1164-4495-8b45-8de7754ca484 resourceVersion: "153737" uid: abdc06b8-3911-4c73-a08d-88549a7a4d62 spec: sourcePod: network-check-source-6f78d59f99-jws95 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T13:18:00Z" message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.073764ms message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:14:00Z" - latency: 2.392736ms message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:13:00Z" - latency: 2.212709ms message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:12:00Z" - latency: 2.427658ms message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:11:00Z" - latency: 2.242574ms message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:10:00Z" - latency: 1.875608ms message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:09:00Z" - latency: 2.211415ms message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:08:00Z" - latency: 2.386806ms message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:07:00Z" - latency: 2.12404ms message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:06:00Z" - latency: 2.944175ms message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:05:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T13:10:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-36-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-36.us-east-2.compute.internal uid: b17c75fc-1164-4495-8b45-8de7754ca484 resourceVersion: "151153" uid: 9fc68ae4-8d92-45b6-bc53-0a9426c4b869 spec: sourcePod: network-check-source-6f78d59f99-jws95 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T13:17:00Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 866.113µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:11:00Z" - latency: 2.086791ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T14:11:00Z" - latency: 1.39085ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:10:00Z" - latency: 1.979998ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T14:10:00Z" - latency: 943.303µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:09:00Z" - latency: 2.008641ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T14:09:00Z" - latency: 958.298µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:08:00Z" - latency: 1.843758ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T14:08:00Z" - latency: 933.483µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:07:00Z" - latency: 2.272954ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T14:07:00Z" kind: List metadata: resourceVersion: ""