apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:23:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-149-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-149.ec2.internal uid: 004361ae-8e7c-472a-b969-b5714e146582 resourceVersion: "63262" uid: 425762db-eec7-4e89-a50e-8eecd59a49db spec: sourcePod: network-check-source-7bc5b6bf85-4jw55 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-22T02:30:58Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.099665ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:05:58Z" - latency: 1.169998ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:04:58Z" - latency: 1.203122ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:03:58Z" - latency: 1.150543ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:02:58Z" - latency: 1.209073ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:01:58Z" - latency: 1.0163ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:00:58Z" - latency: 992.45µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:59:58Z" - latency: 989.063µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:58:58Z" - latency: 1.295222ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:57:58Z" - latency: 1.3417ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:56:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:23:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-149-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-149.ec2.internal uid: 004361ae-8e7c-472a-b969-b5714e146582 resourceVersion: "63263" uid: d7ab7e52-d797-4904-b290-df4007a809e7 spec: sourcePod: network-check-source-7bc5b6bf85-4jw55 targetEndpoint: abbc7502dac3a453d84b9fd56c229126-fb9077bed44fabb0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T02:29:58Z" message: 'load-balancer-api-external: tcp connection to abbc7502dac3a453d84b9fd56c229126-fb9077bed44fabb0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.423908ms message: 'load-balancer-api-external: tcp connection to abbc7502dac3a453d84b9fd56c229126-fb9077bed44fabb0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:05:58Z" - latency: 9.591172ms message: 'load-balancer-api-external: resolved host name abbc7502dac3a453d84b9fd56c229126-fb9077bed44fabb0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:05:58Z" - latency: 5.632395ms message: 'load-balancer-api-external: tcp connection to abbc7502dac3a453d84b9fd56c229126-fb9077bed44fabb0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:04:58Z" - latency: 6.718473ms message: 'load-balancer-api-external: resolved host name abbc7502dac3a453d84b9fd56c229126-fb9077bed44fabb0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:04:58Z" - latency: 4.475287ms message: 'load-balancer-api-external: tcp connection to abbc7502dac3a453d84b9fd56c229126-fb9077bed44fabb0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:03:58Z" - latency: 10.00234ms message: 'load-balancer-api-external: resolved host name abbc7502dac3a453d84b9fd56c229126-fb9077bed44fabb0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:03:58Z" - latency: 4.298315ms message: 'load-balancer-api-external: tcp connection to abbc7502dac3a453d84b9fd56c229126-fb9077bed44fabb0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:02:58Z" - latency: 10.522405ms message: 'load-balancer-api-external: resolved host name abbc7502dac3a453d84b9fd56c229126-fb9077bed44fabb0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:02:58Z" - latency: 5.43346ms message: 'load-balancer-api-external: tcp connection to abbc7502dac3a453d84b9fd56c229126-fb9077bed44fabb0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:01:58Z" - latency: 7.247349ms message: 'load-balancer-api-external: resolved host name abbc7502dac3a453d84b9fd56c229126-fb9077bed44fabb0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:01:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:23:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-149-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-149.ec2.internal uid: 004361ae-8e7c-472a-b969-b5714e146582 resourceVersion: "63264" uid: 7d87f5f0-e836-4c2f-88d8-0c70f18f3493 spec: sourcePod: network-check-source-7bc5b6bf85-4jw55 targetEndpoint: abbc7502dac3a453d84b9fd56c229126-fb9077bed44fabb0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T02:29:58Z" message: 'load-balancer-api-internal: tcp connection to abbc7502dac3a453d84b9fd56c229126-fb9077bed44fabb0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.979564ms message: 'load-balancer-api-internal: tcp connection to abbc7502dac3a453d84b9fd56c229126-fb9077bed44fabb0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:05:58Z" - latency: 9.619687ms message: 'load-balancer-api-internal: resolved host name abbc7502dac3a453d84b9fd56c229126-fb9077bed44fabb0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:05:58Z" - latency: 5.847664ms message: 'load-balancer-api-internal: tcp connection to abbc7502dac3a453d84b9fd56c229126-fb9077bed44fabb0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:04:58Z" - latency: 6.595019ms message: 'load-balancer-api-internal: resolved host name abbc7502dac3a453d84b9fd56c229126-fb9077bed44fabb0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:04:58Z" - latency: 4.467877ms message: 'load-balancer-api-internal: tcp connection to abbc7502dac3a453d84b9fd56c229126-fb9077bed44fabb0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:03:58Z" - latency: 10.141926ms message: 'load-balancer-api-internal: resolved host name abbc7502dac3a453d84b9fd56c229126-fb9077bed44fabb0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:03:58Z" - latency: 4.308491ms message: 'load-balancer-api-internal: tcp connection to abbc7502dac3a453d84b9fd56c229126-fb9077bed44fabb0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:02:58Z" - latency: 10.423788ms message: 'load-balancer-api-internal: resolved host name abbc7502dac3a453d84b9fd56c229126-fb9077bed44fabb0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:02:58Z" - latency: 5.424234ms message: 'load-balancer-api-internal: tcp connection to abbc7502dac3a453d84b9fd56c229126-fb9077bed44fabb0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:01:58Z" - latency: 7.212634ms message: 'load-balancer-api-internal: resolved host name abbc7502dac3a453d84b9fd56c229126-fb9077bed44fabb0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:01:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:23:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-149-to-network-check-target-ip-10-0-132-119 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-149.ec2.internal uid: 004361ae-8e7c-472a-b969-b5714e146582 resourceVersion: "63261" uid: d1534b2b-3c3a-4284-9862-3d22a95e9247 spec: sourcePod: network-check-source-7bc5b6bf85-4jw55 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-22T02:30:58Z" message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.369304ms message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:05:58Z" - latency: 2.441023ms message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:04:58Z" - latency: 2.521447ms message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:03:58Z" - latency: 2.309649ms message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:02:58Z" - latency: 2.464855ms message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:01:58Z" - latency: 2.477444ms message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:00:58Z" - latency: 2.369513ms message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:59:58Z" - latency: 2.127398ms message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:58:58Z" - latency: 2.378811ms message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:57:58Z" - latency: 2.243434ms message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:56:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:23:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-149-to-network-check-target-ip-10-0-138-202 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-149.ec2.internal uid: 004361ae-8e7c-472a-b969-b5714e146582 resourceVersion: "63258" uid: 1ba607c3-28b1-443d-84fb-505ee998a8ec spec: sourcePod: network-check-source-7bc5b6bf85-4jw55 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-22T02:30:58Z" message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.234763ms message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:05:58Z" - latency: 2.325149ms message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:04:58Z" - latency: 2.511228ms message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:03:58Z" - latency: 2.406424ms message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:02:58Z" - latency: 2.468902ms message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:01:58Z" - latency: 2.232613ms message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:00:58Z" - latency: 2.184382ms message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:59:58Z" - latency: 2.364647ms message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:58:58Z" - latency: 2.477527ms message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:57:58Z" - latency: 2.66113ms message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:56:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:23:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-149-to-network-check-target-ip-10-0-142-149 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-149.ec2.internal uid: 004361ae-8e7c-472a-b969-b5714e146582 resourceVersion: "63259" uid: d8626e7a-fa00-46e1-921f-01194e79984e spec: sourcePod: network-check-source-7bc5b6bf85-4jw55 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-22T02:30:58Z" message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 925.309µs message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:05:58Z" - latency: 962.321µs message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:04:58Z" - latency: 1.031511ms message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:03:58Z" - latency: 1.017449ms message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:02:58Z" - latency: 978.55µs message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:01:58Z" - latency: 922.816µs message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:00:58Z" - latency: 1.050522ms message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:59:58Z" - latency: 888.625µs message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:58:58Z" - latency: 1.070495ms message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:57:58Z" - latency: 1.463211ms message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:56:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:23:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-149-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-149.ec2.internal uid: 004361ae-8e7c-472a-b969-b5714e146582 resourceVersion: "63260" uid: b297766e-4208-400f-80b1-da152ed1b07d spec: sourcePod: network-check-source-7bc5b6bf85-4jw55 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-22T02:29:58Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 891.365µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:05:58Z" - latency: 2.123146ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T03:05:58Z" - latency: 1.182138ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:04:58Z" - latency: 1.779166ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T03:04:58Z" - latency: 899.213µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:03:58Z" - latency: 2.94249ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T03:03:58Z" - latency: 1.068625ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:02:58Z" - latency: 1.748273ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T03:02:58Z" - latency: 1.176302ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:01:58Z" - latency: 1.787059ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T03:01:58Z" kind: List metadata: resourceVersion: ""