apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T02:02:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-250-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-250.ec2.internal uid: 990e59c7-fd61-42ca-912e-f5b82850542b resourceVersion: "19601" uid: 414c9d0d-eae6-4fd5-a114-26a8535df906 spec: sourcePod: network-check-source-7f44b6dd87-x6vdm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-29T02:09:39Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.713171ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:23:39Z" - latency: 807.728µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:22:39Z" - latency: 1.070396ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:21:39Z" - latency: 892.953µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:20:39Z" - latency: 937.05µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:19:39Z" - latency: 965.511µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:18:39Z" - latency: 1.268324ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:17:39Z" - latency: 1.050153ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:16:39Z" - latency: 862.529µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:15:39Z" - latency: 844.592µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:14:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T02:02:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-250-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-250.ec2.internal uid: 990e59c7-fd61-42ca-912e-f5b82850542b resourceVersion: "20840" uid: 0b03a978-853e-4db7-86bb-075cb1744755 spec: sourcePod: network-check-source-7f44b6dd87-x6vdm targetEndpoint: aa1f1c289c6364ca8904c770dc1120e9-89b46a52aec321ba.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-29T02:08:39Z" message: 'load-balancer-api-external: tcp connection to aa1f1c289c6364ca8904c770dc1120e9-89b46a52aec321ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.030163ms message: 'load-balancer-api-external: tcp connection to aa1f1c289c6364ca8904c770dc1120e9-89b46a52aec321ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:26:39Z" - latency: 6.589225ms message: 'load-balancer-api-external: resolved host name aa1f1c289c6364ca8904c770dc1120e9-89b46a52aec321ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T02:26:39Z" - latency: 18.366903ms message: 'load-balancer-api-external: tcp connection to aa1f1c289c6364ca8904c770dc1120e9-89b46a52aec321ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:25:39Z" - latency: 6.847704ms message: 'load-balancer-api-external: resolved host name aa1f1c289c6364ca8904c770dc1120e9-89b46a52aec321ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T02:25:39Z" - latency: 4.492959ms message: 'load-balancer-api-external: tcp connection to aa1f1c289c6364ca8904c770dc1120e9-89b46a52aec321ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:24:39Z" - latency: 6.370405ms message: 'load-balancer-api-external: resolved host name aa1f1c289c6364ca8904c770dc1120e9-89b46a52aec321ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T02:24:39Z" - latency: 4.476359ms message: 'load-balancer-api-external: tcp connection to aa1f1c289c6364ca8904c770dc1120e9-89b46a52aec321ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:23:39Z" - latency: 7.038468ms message: 'load-balancer-api-external: resolved host name aa1f1c289c6364ca8904c770dc1120e9-89b46a52aec321ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T02:23:39Z" - latency: 3.819402ms message: 'load-balancer-api-external: tcp connection to aa1f1c289c6364ca8904c770dc1120e9-89b46a52aec321ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:22:39Z" - latency: 6.250251ms message: 'load-balancer-api-external: resolved host name aa1f1c289c6364ca8904c770dc1120e9-89b46a52aec321ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T02:22:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T02:02:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-250-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-250.ec2.internal uid: 990e59c7-fd61-42ca-912e-f5b82850542b resourceVersion: "20839" uid: 0d89b77d-a022-48f6-a80d-c31d459af19a spec: sourcePod: network-check-source-7f44b6dd87-x6vdm targetEndpoint: aa1f1c289c6364ca8904c770dc1120e9-89b46a52aec321ba.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-29T02:08:39Z" message: 'load-balancer-api-internal: tcp connection to aa1f1c289c6364ca8904c770dc1120e9-89b46a52aec321ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.046714ms message: 'load-balancer-api-internal: tcp connection to aa1f1c289c6364ca8904c770dc1120e9-89b46a52aec321ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:26:39Z" - latency: 6.553832ms message: 'load-balancer-api-internal: resolved host name aa1f1c289c6364ca8904c770dc1120e9-89b46a52aec321ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T02:26:39Z" - latency: 5.108806ms message: 'load-balancer-api-internal: tcp connection to aa1f1c289c6364ca8904c770dc1120e9-89b46a52aec321ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:25:39Z" - latency: 6.825751ms message: 'load-balancer-api-internal: resolved host name aa1f1c289c6364ca8904c770dc1120e9-89b46a52aec321ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T02:25:39Z" - latency: 4.524023ms message: 'load-balancer-api-internal: tcp connection to aa1f1c289c6364ca8904c770dc1120e9-89b46a52aec321ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:24:39Z" - latency: 6.336084ms message: 'load-balancer-api-internal: resolved host name aa1f1c289c6364ca8904c770dc1120e9-89b46a52aec321ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T02:24:39Z" - latency: 4.884645ms message: 'load-balancer-api-internal: tcp connection to aa1f1c289c6364ca8904c770dc1120e9-89b46a52aec321ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:23:39Z" - latency: 7.003931ms message: 'load-balancer-api-internal: resolved host name aa1f1c289c6364ca8904c770dc1120e9-89b46a52aec321ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T02:23:39Z" - latency: 3.887289ms message: 'load-balancer-api-internal: tcp connection to aa1f1c289c6364ca8904c770dc1120e9-89b46a52aec321ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:22:39Z" - latency: 6.198545ms message: 'load-balancer-api-internal: resolved host name aa1f1c289c6364ca8904c770dc1120e9-89b46a52aec321ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T02:22:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T02:02:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-250-to-network-check-target-ip-10-0-129-62 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-250.ec2.internal uid: 990e59c7-fd61-42ca-912e-f5b82850542b resourceVersion: "19599" uid: e93fa2cb-71af-44ac-a4d1-63d10c6419ce spec: sourcePod: network-check-source-7f44b6dd87-x6vdm targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-29T02:09:39Z" message: 'network-check-target-ip-10-0-129-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.043192ms message: 'network-check-target-ip-10-0-129-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:23:39Z" - latency: 2.405916ms message: 'network-check-target-ip-10-0-129-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:22:39Z" - latency: 2.24585ms message: 'network-check-target-ip-10-0-129-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:21:39Z" - latency: 1.973478ms message: 'network-check-target-ip-10-0-129-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:20:39Z" - latency: 2.577395ms message: 'network-check-target-ip-10-0-129-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:19:39Z" - latency: 2.154858ms message: 'network-check-target-ip-10-0-129-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:18:39Z" - latency: 2.185901ms message: 'network-check-target-ip-10-0-129-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:17:39Z" - latency: 2.054076ms message: 'network-check-target-ip-10-0-129-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:16:39Z" - latency: 2.502381ms message: 'network-check-target-ip-10-0-129-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:15:39Z" - latency: 2.097187ms message: 'network-check-target-ip-10-0-129-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:14:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T02:02:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-250-to-network-check-target-ip-10-0-130-154 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-250.ec2.internal uid: 990e59c7-fd61-42ca-912e-f5b82850542b resourceVersion: "19600" uid: c17f63ff-d1b4-40cd-beb1-2a5c7ea61fa0 spec: sourcePod: network-check-source-7f44b6dd87-x6vdm targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-29T02:09:39Z" message: 'network-check-target-ip-10-0-130-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.290218ms message: 'network-check-target-ip-10-0-130-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:23:39Z" - latency: 2.10673ms message: 'network-check-target-ip-10-0-130-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:22:39Z" - latency: 2.214942ms message: 'network-check-target-ip-10-0-130-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:21:39Z" - latency: 2.192504ms message: 'network-check-target-ip-10-0-130-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:20:39Z" - latency: 1.855211ms message: 'network-check-target-ip-10-0-130-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:19:39Z" - latency: 2.460089ms message: 'network-check-target-ip-10-0-130-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:18:39Z" - latency: 2.094334ms message: 'network-check-target-ip-10-0-130-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:17:39Z" - latency: 2.324262ms message: 'network-check-target-ip-10-0-130-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:16:39Z" - latency: 2.126118ms message: 'network-check-target-ip-10-0-130-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:15:39Z" - latency: 1.991553ms message: 'network-check-target-ip-10-0-130-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:14:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T02:02:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-250-to-network-check-target-ip-10-0-141-250 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-250.ec2.internal uid: 990e59c7-fd61-42ca-912e-f5b82850542b resourceVersion: "19598" uid: 37abae4b-7831-4f5c-b152-8bff99ef7e97 spec: sourcePod: network-check-source-7f44b6dd87-x6vdm targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-29T02:09:39Z" message: 'network-check-target-ip-10-0-141-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 863.663µs message: 'network-check-target-ip-10-0-141-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:23:39Z" - latency: 920.087µs message: 'network-check-target-ip-10-0-141-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:22:39Z" - latency: 1.61095ms message: 'network-check-target-ip-10-0-141-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:21:39Z" - latency: 925.083µs message: 'network-check-target-ip-10-0-141-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:20:39Z" - latency: 1.456126ms message: 'network-check-target-ip-10-0-141-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:19:39Z" - latency: 1.339833ms message: 'network-check-target-ip-10-0-141-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:18:39Z" - latency: 1.058266ms message: 'network-check-target-ip-10-0-141-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:17:39Z" - latency: 787.139µs message: 'network-check-target-ip-10-0-141-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:16:39Z" - latency: 921.312µs message: 'network-check-target-ip-10-0-141-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:15:39Z" - latency: 1.048246ms message: 'network-check-target-ip-10-0-141-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:14:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T02:02:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-250-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-250.ec2.internal uid: 990e59c7-fd61-42ca-912e-f5b82850542b resourceVersion: "20838" uid: 77a00572-cbc9-45eb-88d1-811c5d713a0b spec: sourcePod: network-check-source-7f44b6dd87-x6vdm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-29T02:08:39Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.099713ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:26:39Z" - latency: 1.914802ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T02:26:39Z" - latency: 991.835µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:25:39Z" - latency: 2.161488ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T02:25:39Z" - latency: 779.227µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:24:39Z" - latency: 1.923679ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T02:24:39Z" - latency: 919.326µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:23:39Z" - latency: 2.243445ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T02:23:39Z" - latency: 830.095µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:22:39Z" - latency: 1.651337ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T02:22:39Z" kind: List metadata: resourceVersion: ""