apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T21:51:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-36-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-36.ec2.internal uid: 3e01583f-47f8-4b8d-b26e-870571c21206 resourceVersion: "63256" uid: 41295050-0ce4-4ffb-8c10-801186e49323 spec: sourcePod: network-check-source-7bc5b6bf85-59mpt targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-21T21:58:33Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.264906ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:33:33Z" - latency: 1.081909ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:32:33Z" - latency: 1.128142ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:31:33Z" - latency: 1.244838ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:30:33Z" - latency: 1.377442ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:29:33Z" - latency: 1.050776ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:28:33Z" - latency: 1.281001ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:27:33Z" - latency: 1.110303ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:26:33Z" - latency: 996.018µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:25:33Z" - latency: 959.58µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:24:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T21:51:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-36-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-36.ec2.internal uid: 3e01583f-47f8-4b8d-b26e-870571c21206 resourceVersion: "63257" uid: f64c7058-9ab8-48ff-8a65-a09662264838 spec: sourcePod: network-check-source-7bc5b6bf85-59mpt targetEndpoint: a72c3effbfa184f9a9fec3cc7f824417-a3e29288559cf186.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T21:57:33Z" message: 'load-balancer-api-external: tcp connection to a72c3effbfa184f9a9fec3cc7f824417-a3e29288559cf186.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.197331ms message: 'load-balancer-api-external: tcp connection to a72c3effbfa184f9a9fec3cc7f824417-a3e29288559cf186.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:33:33Z" - latency: 7.577337ms message: 'load-balancer-api-external: resolved host name a72c3effbfa184f9a9fec3cc7f824417-a3e29288559cf186.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T22:33:33Z" - latency: 4.463757ms message: 'load-balancer-api-external: tcp connection to a72c3effbfa184f9a9fec3cc7f824417-a3e29288559cf186.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:32:33Z" - latency: 6.997936ms message: 'load-balancer-api-external: resolved host name a72c3effbfa184f9a9fec3cc7f824417-a3e29288559cf186.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T22:32:33Z" - latency: 4.221978ms message: 'load-balancer-api-external: tcp connection to a72c3effbfa184f9a9fec3cc7f824417-a3e29288559cf186.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:31:33Z" - latency: 8.8637ms message: 'load-balancer-api-external: resolved host name a72c3effbfa184f9a9fec3cc7f824417-a3e29288559cf186.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T22:31:33Z" - latency: 5.217272ms message: 'load-balancer-api-external: tcp connection to a72c3effbfa184f9a9fec3cc7f824417-a3e29288559cf186.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:30:33Z" - latency: 6.158633ms message: 'load-balancer-api-external: resolved host name a72c3effbfa184f9a9fec3cc7f824417-a3e29288559cf186.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T22:30:33Z" - latency: 5.028061ms message: 'load-balancer-api-external: tcp connection to a72c3effbfa184f9a9fec3cc7f824417-a3e29288559cf186.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:29:33Z" - latency: 7.240069ms message: 'load-balancer-api-external: resolved host name a72c3effbfa184f9a9fec3cc7f824417-a3e29288559cf186.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T22:29:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T21:51:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-36-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-36.ec2.internal uid: 3e01583f-47f8-4b8d-b26e-870571c21206 resourceVersion: "63258" uid: abf41db6-5114-42f6-bd2f-e97d117d066d spec: sourcePod: network-check-source-7bc5b6bf85-59mpt targetEndpoint: a72c3effbfa184f9a9fec3cc7f824417-a3e29288559cf186.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T21:57:33Z" message: 'load-balancer-api-internal: tcp connection to a72c3effbfa184f9a9fec3cc7f824417-a3e29288559cf186.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.189063ms message: 'load-balancer-api-internal: tcp connection to a72c3effbfa184f9a9fec3cc7f824417-a3e29288559cf186.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:33:33Z" - latency: 7.52092ms message: 'load-balancer-api-internal: resolved host name a72c3effbfa184f9a9fec3cc7f824417-a3e29288559cf186.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T22:33:33Z" - latency: 3.474594ms message: 'load-balancer-api-internal: tcp connection to a72c3effbfa184f9a9fec3cc7f824417-a3e29288559cf186.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:32:33Z" - latency: 7.070405ms message: 'load-balancer-api-internal: resolved host name a72c3effbfa184f9a9fec3cc7f824417-a3e29288559cf186.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T22:32:33Z" - latency: 4.249453ms message: 'load-balancer-api-internal: tcp connection to a72c3effbfa184f9a9fec3cc7f824417-a3e29288559cf186.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:31:33Z" - latency: 8.80903ms message: 'load-balancer-api-internal: resolved host name a72c3effbfa184f9a9fec3cc7f824417-a3e29288559cf186.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T22:31:33Z" - latency: 5.181018ms message: 'load-balancer-api-internal: tcp connection to a72c3effbfa184f9a9fec3cc7f824417-a3e29288559cf186.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:30:33Z" - latency: 6.224549ms message: 'load-balancer-api-internal: resolved host name a72c3effbfa184f9a9fec3cc7f824417-a3e29288559cf186.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T22:30:33Z" - latency: 5.100045ms message: 'load-balancer-api-internal: tcp connection to a72c3effbfa184f9a9fec3cc7f824417-a3e29288559cf186.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:29:33Z" - latency: 7.146237ms message: 'load-balancer-api-internal: resolved host name a72c3effbfa184f9a9fec3cc7f824417-a3e29288559cf186.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T22:29:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T21:51:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-36-to-network-check-target-ip-10-0-130-224 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-36.ec2.internal uid: 3e01583f-47f8-4b8d-b26e-870571c21206 resourceVersion: "63254" uid: ba865373-8478-4df2-b7a4-c55464ea371a spec: sourcePod: network-check-source-7bc5b6bf85-59mpt targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T21:58:33Z" message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.237249ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:33:33Z" - latency: 2.337472ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:32:33Z" - latency: 2.044323ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:31:33Z" - latency: 1.721139ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:30:33Z" - latency: 1.953081ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:29:33Z" - latency: 2.019256ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:28:33Z" - latency: 1.954841ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:27:33Z" - latency: 2.074727ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:26:33Z" - latency: 1.850557ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:25:33Z" - latency: 2.209154ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:24:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T21:51:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-36-to-network-check-target-ip-10-0-135-158 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-36.ec2.internal uid: 3e01583f-47f8-4b8d-b26e-870571c21206 resourceVersion: "63252" uid: eb8af5b7-4fdf-4178-81fe-b7dd68b813e7 spec: sourcePod: network-check-source-7bc5b6bf85-59mpt targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T21:58:33Z" message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.779197ms message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:33:33Z" - latency: 2.144242ms message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:32:33Z" - latency: 1.857168ms message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:31:33Z" - latency: 1.932946ms message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:30:33Z" - latency: 1.831841ms message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:29:33Z" - latency: 2.098938ms message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:28:33Z" - latency: 1.81362ms message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:27:33Z" - latency: 1.980841ms message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:26:33Z" - latency: 2.078877ms message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:25:33Z" - latency: 2.105408ms message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:24:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T21:51:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-36-to-network-check-target-ip-10-0-138-36 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-36.ec2.internal uid: 3e01583f-47f8-4b8d-b26e-870571c21206 resourceVersion: "63253" uid: dd27e988-8c3f-4666-929c-9a21744bba3d spec: sourcePod: network-check-source-7bc5b6bf85-59mpt targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-21T21:58:33Z" message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.022144ms message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:33:33Z" - latency: 896.886µs message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:32:33Z" - latency: 962.718µs message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:31:33Z" - latency: 1.115427ms message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:30:33Z" - latency: 885.542µs message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:29:33Z" - latency: 1.375669ms message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:28:33Z" - latency: 835.523µs message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:27:33Z" - latency: 961.683µs message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:26:33Z" - latency: 1.021016ms message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:25:33Z" - latency: 840.998µs message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:24:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T21:51:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-36-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-36.ec2.internal uid: 3e01583f-47f8-4b8d-b26e-870571c21206 resourceVersion: "63255" uid: 127237c4-98d3-4fec-832a-3081967c9f73 spec: sourcePod: network-check-source-7bc5b6bf85-59mpt targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-21T21:57:33Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.421037ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:33:33Z" - latency: 1.742321ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T22:33:33Z" - latency: 902.49µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:32:33Z" - latency: 1.716186ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T22:32:33Z" - latency: 772.679µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:31:33Z" - latency: 1.827662ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T22:31:33Z" - latency: 768.834µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:30:33Z" - latency: 1.882752ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T22:30:33Z" - latency: 1.069652ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T22:29:33Z" - latency: 1.947667ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T22:29:33Z" kind: List metadata: resourceVersion: ""