apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-18T02:51:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-103-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-103.ec2.internal uid: ca62c75f-98b8-4643-aaf0-76c2a41abc17 resourceVersion: "44574" uid: 0e08184b-04d5-47f8-9bc4-b2cb3691c157 spec: sourcePod: network-check-source-8894fc9bd-96n6r targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-18T02:59:00Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 930.238µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:20:00Z" - latency: 933.413µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:19:00Z" - latency: 1.03793ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:18:00Z" - latency: 846.009µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:17:00Z" - latency: 1.114553ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:16:00Z" - latency: 847.112µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:15:00Z" - latency: 871.228µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:14:00Z" - latency: 987.948µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:13:00Z" - latency: 1.205741ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:12:00Z" - latency: 685.934µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:11:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-18T02:51:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-103-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-103.ec2.internal uid: ca62c75f-98b8-4643-aaf0-76c2a41abc17 resourceVersion: "40025" uid: c10c61aa-cd17-403e-9dd6-600426a48d8d spec: sourcePod: network-check-source-8894fc9bd-96n6r targetEndpoint: a8d4e7d843c88452bbcb1a46d1fc9012-13d1a685a76c21e8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-18T02:58:00Z" message: 'load-balancer-api-external: tcp connection to a8d4e7d843c88452bbcb1a46d1fc9012-13d1a685a76c21e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.050448ms message: 'load-balancer-api-external: tcp connection to a8d4e7d843c88452bbcb1a46d1fc9012-13d1a685a76c21e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:16:00Z" - latency: 7.157408ms message: 'load-balancer-api-external: resolved host name a8d4e7d843c88452bbcb1a46d1fc9012-13d1a685a76c21e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-18T03:16:00Z" - latency: 4.240525ms message: 'load-balancer-api-external: tcp connection to a8d4e7d843c88452bbcb1a46d1fc9012-13d1a685a76c21e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:15:00Z" - latency: 8.118614ms message: 'load-balancer-api-external: resolved host name a8d4e7d843c88452bbcb1a46d1fc9012-13d1a685a76c21e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-18T03:15:00Z" - latency: 4.23252ms message: 'load-balancer-api-external: tcp connection to a8d4e7d843c88452bbcb1a46d1fc9012-13d1a685a76c21e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:14:00Z" - latency: 9.269307ms message: 'load-balancer-api-external: resolved host name a8d4e7d843c88452bbcb1a46d1fc9012-13d1a685a76c21e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-18T03:14:00Z" - latency: 5.191055ms message: 'load-balancer-api-external: tcp connection to a8d4e7d843c88452bbcb1a46d1fc9012-13d1a685a76c21e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:13:00Z" - latency: 5.908346ms message: 'load-balancer-api-external: resolved host name a8d4e7d843c88452bbcb1a46d1fc9012-13d1a685a76c21e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-18T03:13:00Z" - latency: 4.289103ms message: 'load-balancer-api-external: tcp connection to a8d4e7d843c88452bbcb1a46d1fc9012-13d1a685a76c21e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:12:00Z" - latency: 8.58009ms message: 'load-balancer-api-external: resolved host name a8d4e7d843c88452bbcb1a46d1fc9012-13d1a685a76c21e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-18T03:12:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-18T02:51:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-103-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-103.ec2.internal uid: ca62c75f-98b8-4643-aaf0-76c2a41abc17 resourceVersion: "40026" uid: 516c1efb-90cb-4a99-ab53-6c4536b7a8c4 spec: sourcePod: network-check-source-8894fc9bd-96n6r targetEndpoint: a8d4e7d843c88452bbcb1a46d1fc9012-13d1a685a76c21e8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-18T02:58:00Z" message: 'load-balancer-api-internal: tcp connection to a8d4e7d843c88452bbcb1a46d1fc9012-13d1a685a76c21e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.03676ms message: 'load-balancer-api-internal: tcp connection to a8d4e7d843c88452bbcb1a46d1fc9012-13d1a685a76c21e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:16:00Z" - latency: 7.100844ms message: 'load-balancer-api-internal: resolved host name a8d4e7d843c88452bbcb1a46d1fc9012-13d1a685a76c21e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-18T03:16:00Z" - latency: 4.361473ms message: 'load-balancer-api-internal: tcp connection to a8d4e7d843c88452bbcb1a46d1fc9012-13d1a685a76c21e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:15:00Z" - latency: 8.082562ms message: 'load-balancer-api-internal: resolved host name a8d4e7d843c88452bbcb1a46d1fc9012-13d1a685a76c21e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-18T03:15:00Z" - latency: 4.231656ms message: 'load-balancer-api-internal: tcp connection to a8d4e7d843c88452bbcb1a46d1fc9012-13d1a685a76c21e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:14:00Z" - latency: 9.227519ms message: 'load-balancer-api-internal: resolved host name a8d4e7d843c88452bbcb1a46d1fc9012-13d1a685a76c21e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-18T03:14:00Z" - latency: 5.199693ms message: 'load-balancer-api-internal: tcp connection to a8d4e7d843c88452bbcb1a46d1fc9012-13d1a685a76c21e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:13:00Z" - latency: 5.807724ms message: 'load-balancer-api-internal: resolved host name a8d4e7d843c88452bbcb1a46d1fc9012-13d1a685a76c21e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-18T03:13:00Z" - latency: 4.290931ms message: 'load-balancer-api-internal: tcp connection to a8d4e7d843c88452bbcb1a46d1fc9012-13d1a685a76c21e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:12:00Z" - latency: 8.506063ms message: 'load-balancer-api-internal: resolved host name a8d4e7d843c88452bbcb1a46d1fc9012-13d1a685a76c21e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-18T03:12:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-18T02:51:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-103-to-network-check-target-ip-10-0-128-79 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-103.ec2.internal uid: ca62c75f-98b8-4643-aaf0-76c2a41abc17 resourceVersion: "44573" uid: 0911442b-805d-458f-8dd4-9faadf0d888a spec: sourcePod: network-check-source-8894fc9bd-96n6r targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-18T02:59:00Z" message: 'network-check-target-ip-10-0-128-79: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.164481ms message: 'network-check-target-ip-10-0-128-79: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:20:00Z" - latency: 2.282394ms message: 'network-check-target-ip-10-0-128-79: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:19:00Z" - latency: 2.170036ms message: 'network-check-target-ip-10-0-128-79: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:18:00Z" - latency: 2.247569ms message: 'network-check-target-ip-10-0-128-79: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:17:00Z" - latency: 2.417979ms message: 'network-check-target-ip-10-0-128-79: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:16:00Z" - latency: 2.050003ms message: 'network-check-target-ip-10-0-128-79: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:15:00Z" - latency: 2.303282ms message: 'network-check-target-ip-10-0-128-79: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:14:00Z" - latency: 2.37267ms message: 'network-check-target-ip-10-0-128-79: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:13:00Z" - latency: 2.003881ms message: 'network-check-target-ip-10-0-128-79: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:12:00Z" - latency: 1.706425ms message: 'network-check-target-ip-10-0-128-79: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:11:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-18T02:51:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-103-to-network-check-target-ip-10-0-129-229 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-103.ec2.internal uid: ca62c75f-98b8-4643-aaf0-76c2a41abc17 resourceVersion: "44572" uid: 6f475277-3cba-421b-9c28-441eed30094b spec: sourcePod: network-check-source-8894fc9bd-96n6r targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-18T02:59:00Z" message: 'network-check-target-ip-10-0-129-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.016004ms message: 'network-check-target-ip-10-0-129-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:20:00Z" - latency: 2.013898ms message: 'network-check-target-ip-10-0-129-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:19:00Z" - latency: 2.122677ms message: 'network-check-target-ip-10-0-129-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:18:00Z" - latency: 1.990138ms message: 'network-check-target-ip-10-0-129-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:17:00Z" - latency: 2.027033ms message: 'network-check-target-ip-10-0-129-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:16:00Z" - latency: 2.011644ms message: 'network-check-target-ip-10-0-129-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:15:00Z" - latency: 2.324993ms message: 'network-check-target-ip-10-0-129-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:14:00Z" - latency: 2.250779ms message: 'network-check-target-ip-10-0-129-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:13:00Z" - latency: 2.285637ms message: 'network-check-target-ip-10-0-129-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:12:00Z" - latency: 1.842303ms message: 'network-check-target-ip-10-0-129-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:11:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-18T02:52:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-103-to-network-check-target-ip-10-0-140-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-103.ec2.internal uid: ca62c75f-98b8-4643-aaf0-76c2a41abc17 resourceVersion: "44571" uid: f32d4655-e672-4492-a747-84a28904fe25 spec: sourcePod: network-check-source-8894fc9bd-96n6r targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-18T02:59:00Z" message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.184562ms message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:20:00Z" - latency: 1.52429ms message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:19:00Z" - latency: 845.773µs message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:18:00Z" - latency: 1.313586ms message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:17:00Z" - latency: 1.442657ms message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:16:00Z" - latency: 1.633971ms message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:15:00Z" - latency: 1.029879ms message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:14:00Z" - latency: 1.120137ms message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:13:00Z" - latency: 877.624µs message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:12:00Z" - latency: 1.381769ms message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:11:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-18T02:51:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-103-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-103.ec2.internal uid: ca62c75f-98b8-4643-aaf0-76c2a41abc17 resourceVersion: "40024" uid: d88c70d3-6659-4814-90a1-f742b81eaee5 spec: sourcePod: network-check-source-8894fc9bd-96n6r targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-18T02:58:00Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 773.47µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:16:00Z" - latency: 2.087389ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-18T03:16:00Z" - latency: 935.68µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:15:00Z" - latency: 1.687056ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-18T03:15:00Z" - latency: 796.763µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:14:00Z" - latency: 1.679997ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-18T03:14:00Z" - latency: 858.672µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:13:00Z" - latency: 1.435682ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-18T03:13:00Z" - latency: 1.12282ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-18T03:12:00Z" - latency: 1.833063ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-18T03:12:00Z" kind: List metadata: resourceVersion: ""