apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T09:30:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-244-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-244.ec2.internal uid: 4438760c-25ba-4cbe-a9b3-046637aed90e resourceVersion: "68843" uid: 61bc0690-92a4-486a-98be-2efbbdebfea7 spec: sourcePod: network-check-source-7bc5b6bf85-t977w targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-17T09:37:18Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.001839ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:19:18Z" - latency: 972.979µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:18:18Z" - latency: 1.065564ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:17:18Z" - latency: 1.106326ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:16:18Z" - latency: 982.848µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:15:18Z" - latency: 957.713µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:14:18Z" - latency: 971.711µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:13:18Z" - latency: 969.199µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:12:18Z" - latency: 1.687385ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:11:18Z" - latency: 924.575µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:10:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T09:30:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-244-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-244.ec2.internal uid: 4438760c-25ba-4cbe-a9b3-046637aed90e resourceVersion: "67886" uid: 53ad279d-5d90-47c3-bdb5-976e7d128ad9 spec: sourcePod: network-check-source-7bc5b6bf85-t977w targetEndpoint: ae7fc6018282245e29a8ef090744cc40-4c2b6d76ff4458a1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T09:36:18Z" message: 'load-balancer-api-external: tcp connection to ae7fc6018282245e29a8ef090744cc40-4c2b6d76ff4458a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.873636ms message: 'load-balancer-api-external: tcp connection to ae7fc6018282245e29a8ef090744cc40-4c2b6d76ff4458a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:18:18Z" - latency: 8.314901ms message: 'load-balancer-api-external: resolved host name ae7fc6018282245e29a8ef090744cc40-4c2b6d76ff4458a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T10:18:18Z" - latency: 5.482161ms message: 'load-balancer-api-external: tcp connection to ae7fc6018282245e29a8ef090744cc40-4c2b6d76ff4458a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:17:18Z" - latency: 7.466891ms message: 'load-balancer-api-external: resolved host name ae7fc6018282245e29a8ef090744cc40-4c2b6d76ff4458a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T10:17:18Z" - latency: 5.375604ms message: 'load-balancer-api-external: tcp connection to ae7fc6018282245e29a8ef090744cc40-4c2b6d76ff4458a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:16:18Z" - latency: 7.006034ms message: 'load-balancer-api-external: resolved host name ae7fc6018282245e29a8ef090744cc40-4c2b6d76ff4458a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T10:16:18Z" - latency: 4.46591ms message: 'load-balancer-api-external: tcp connection to ae7fc6018282245e29a8ef090744cc40-4c2b6d76ff4458a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:15:18Z" - latency: 8.907406ms message: 'load-balancer-api-external: resolved host name ae7fc6018282245e29a8ef090744cc40-4c2b6d76ff4458a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T10:15:18Z" - latency: 4.656437ms message: 'load-balancer-api-external: tcp connection to ae7fc6018282245e29a8ef090744cc40-4c2b6d76ff4458a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:14:18Z" - latency: 7.833077ms message: 'load-balancer-api-external: resolved host name ae7fc6018282245e29a8ef090744cc40-4c2b6d76ff4458a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T10:14:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T09:30:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-244-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-244.ec2.internal uid: 4438760c-25ba-4cbe-a9b3-046637aed90e resourceVersion: "67885" uid: a1e7fcb5-4878-48c0-8c28-5b9b2c19194d spec: sourcePod: network-check-source-7bc5b6bf85-t977w targetEndpoint: ae7fc6018282245e29a8ef090744cc40-4c2b6d76ff4458a1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T09:36:18Z" message: 'load-balancer-api-internal: tcp connection to ae7fc6018282245e29a8ef090744cc40-4c2b6d76ff4458a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.888571ms message: 'load-balancer-api-internal: tcp connection to ae7fc6018282245e29a8ef090744cc40-4c2b6d76ff4458a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:18:18Z" - latency: 8.257855ms message: 'load-balancer-api-internal: resolved host name ae7fc6018282245e29a8ef090744cc40-4c2b6d76ff4458a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T10:18:18Z" - latency: 5.461601ms message: 'load-balancer-api-internal: tcp connection to ae7fc6018282245e29a8ef090744cc40-4c2b6d76ff4458a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:17:18Z" - latency: 7.513918ms message: 'load-balancer-api-internal: resolved host name ae7fc6018282245e29a8ef090744cc40-4c2b6d76ff4458a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T10:17:18Z" - latency: 5.20569ms message: 'load-balancer-api-internal: tcp connection to ae7fc6018282245e29a8ef090744cc40-4c2b6d76ff4458a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:16:18Z" - latency: 7.147335ms message: 'load-balancer-api-internal: resolved host name ae7fc6018282245e29a8ef090744cc40-4c2b6d76ff4458a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T10:16:18Z" - latency: 4.494105ms message: 'load-balancer-api-internal: tcp connection to ae7fc6018282245e29a8ef090744cc40-4c2b6d76ff4458a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:15:18Z" - latency: 9.03622ms message: 'load-balancer-api-internal: resolved host name ae7fc6018282245e29a8ef090744cc40-4c2b6d76ff4458a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T10:15:18Z" - latency: 4.644867ms message: 'load-balancer-api-internal: tcp connection to ae7fc6018282245e29a8ef090744cc40-4c2b6d76ff4458a1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:14:18Z" - latency: 7.79644ms message: 'load-balancer-api-internal: resolved host name ae7fc6018282245e29a8ef090744cc40-4c2b6d76ff4458a1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T10:14:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T09:30:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-244-to-network-check-target-ip-10-0-133-236 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-244.ec2.internal uid: 4438760c-25ba-4cbe-a9b3-046637aed90e resourceVersion: "68842" uid: 12eb14dc-4cc1-40f6-92e2-eae5fdd19175 spec: sourcePod: network-check-source-7bc5b6bf85-t977w targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-17T09:37:18Z" message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.659445ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:19:18Z" - latency: 2.332182ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:18:18Z" - latency: 2.085757ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:17:18Z" - latency: 2.324568ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:16:18Z" - latency: 2.058142ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:15:18Z" - latency: 2.237824ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:14:18Z" - latency: 2.363238ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:13:18Z" - latency: 1.85775ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:12:18Z" - latency: 3.037997ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:11:18Z" - latency: 2.041976ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:10:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T09:30:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-244-to-network-check-target-ip-10-0-136-235 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-244.ec2.internal uid: 4438760c-25ba-4cbe-a9b3-046637aed90e resourceVersion: "68841" uid: a1a59623-aecc-4e7d-811c-12b63d8962c2 spec: sourcePod: network-check-source-7bc5b6bf85-t977w targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-17T09:37:18Z" message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.405717ms message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:19:18Z" - latency: 2.19483ms message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:18:18Z" - latency: 2.312796ms message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:17:18Z" - latency: 2.110992ms message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:16:18Z" - latency: 2.521057ms message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:15:18Z" - latency: 2.315312ms message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:14:18Z" - latency: 2.102066ms message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:13:18Z" - latency: 2.028958ms message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:12:18Z" - latency: 3.20393ms message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:11:18Z" - latency: 2.204074ms message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:10:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T09:30:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-244-to-network-check-target-ip-10-0-141-244 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-244.ec2.internal uid: 4438760c-25ba-4cbe-a9b3-046637aed90e resourceVersion: "68840" uid: cbabaf2d-bd74-4510-81fb-6965c45098b4 spec: sourcePod: network-check-source-7bc5b6bf85-t977w targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-17T09:37:18Z" message: 'network-check-target-ip-10-0-141-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.179538ms message: 'network-check-target-ip-10-0-141-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:19:18Z" - latency: 1.003229ms message: 'network-check-target-ip-10-0-141-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:18:18Z" - latency: 1.927404ms message: 'network-check-target-ip-10-0-141-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:17:18Z" - latency: 986.13µs message: 'network-check-target-ip-10-0-141-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:16:18Z" - latency: 965.827µs message: 'network-check-target-ip-10-0-141-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:15:18Z" - latency: 1.165366ms message: 'network-check-target-ip-10-0-141-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:14:18Z" - latency: 1.030579ms message: 'network-check-target-ip-10-0-141-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:13:18Z" - latency: 881.431µs message: 'network-check-target-ip-10-0-141-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:12:18Z" - latency: 1.421052ms message: 'network-check-target-ip-10-0-141-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:11:18Z" - latency: 833.817µs message: 'network-check-target-ip-10-0-141-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:10:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T09:30:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-244-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-244.ec2.internal uid: 4438760c-25ba-4cbe-a9b3-046637aed90e resourceVersion: "67884" uid: 4eb1c4e2-a3b6-43d8-8c42-8802860870b6 spec: sourcePod: network-check-source-7bc5b6bf85-t977w targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-17T09:36:18Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.056262ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:18:18Z" - latency: 1.692956ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T10:18:18Z" - latency: 1.120419ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:17:18Z" - latency: 2.292571ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T10:17:18Z" - latency: 876.477µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:16:18Z" - latency: 2.343946ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T10:16:18Z" - latency: 1.104686ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:15:18Z" - latency: 1.88062ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T10:15:18Z" - latency: 1.077564ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:14:18Z" - latency: 1.997623ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T10:14:18Z" kind: List metadata: resourceVersion: ""