apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:27:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-30-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-30.ec2.internal uid: a9aeb023-1047-44e0-912b-e3a22d7469f6 resourceVersion: "68843" uid: 159e241d-b238-420f-9ec5-9fb713ad3706 spec: sourcePod: network-check-source-7bc5b6bf85-kf252 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-17T17:34:55Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.419542ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:16:55Z" - latency: 1.211908ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:15:55Z" - latency: 1.326806ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:14:55Z" - latency: 1.263872ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:13:55Z" - latency: 1.312076ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:12:55Z" - latency: 1.505241ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:11:55Z" - latency: 1.22876ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:10:55Z" - latency: 1.333187ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:09:55Z" - latency: 1.197831ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:08:55Z" - latency: 1.090822ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:07:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:27:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-30-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-30.ec2.internal uid: a9aeb023-1047-44e0-912b-e3a22d7469f6 resourceVersion: "67870" uid: 9f3ee2f7-0368-470b-9562-7277c34ec233 spec: sourcePod: network-check-source-7bc5b6bf85-kf252 targetEndpoint: a7aecbc0ed44546b284bc7334697825f-a88d6f21feac2d71.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T17:33:55Z" message: 'load-balancer-api-external: tcp connection to a7aecbc0ed44546b284bc7334697825f-a88d6f21feac2d71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.493855ms message: 'load-balancer-api-external: tcp connection to a7aecbc0ed44546b284bc7334697825f-a88d6f21feac2d71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:15:55Z" - latency: 7.225ms message: 'load-balancer-api-external: resolved host name a7aecbc0ed44546b284bc7334697825f-a88d6f21feac2d71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:15:55Z" - latency: 3.512253ms message: 'load-balancer-api-external: tcp connection to a7aecbc0ed44546b284bc7334697825f-a88d6f21feac2d71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:14:55Z" - latency: 7.4114ms message: 'load-balancer-api-external: resolved host name a7aecbc0ed44546b284bc7334697825f-a88d6f21feac2d71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:14:55Z" - latency: 5.341979ms message: 'load-balancer-api-external: tcp connection to a7aecbc0ed44546b284bc7334697825f-a88d6f21feac2d71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:13:55Z" - latency: 7.186341ms message: 'load-balancer-api-external: resolved host name a7aecbc0ed44546b284bc7334697825f-a88d6f21feac2d71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:13:55Z" - latency: 5.386804ms message: 'load-balancer-api-external: tcp connection to a7aecbc0ed44546b284bc7334697825f-a88d6f21feac2d71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:12:55Z" - latency: 7.527354ms message: 'load-balancer-api-external: resolved host name a7aecbc0ed44546b284bc7334697825f-a88d6f21feac2d71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:12:55Z" - latency: 5.492865ms message: 'load-balancer-api-external: tcp connection to a7aecbc0ed44546b284bc7334697825f-a88d6f21feac2d71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:11:55Z" - latency: 9.371685ms message: 'load-balancer-api-external: resolved host name a7aecbc0ed44546b284bc7334697825f-a88d6f21feac2d71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:11:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:27:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-30-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-30.ec2.internal uid: a9aeb023-1047-44e0-912b-e3a22d7469f6 resourceVersion: "67871" uid: 7fa90f22-b560-4b58-a802-47858fad32f1 spec: sourcePod: network-check-source-7bc5b6bf85-kf252 targetEndpoint: a7aecbc0ed44546b284bc7334697825f-a88d6f21feac2d71.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T17:33:55Z" message: 'load-balancer-api-internal: tcp connection to a7aecbc0ed44546b284bc7334697825f-a88d6f21feac2d71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.50073ms message: 'load-balancer-api-internal: tcp connection to a7aecbc0ed44546b284bc7334697825f-a88d6f21feac2d71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:15:55Z" - latency: 7.150199ms message: 'load-balancer-api-internal: resolved host name a7aecbc0ed44546b284bc7334697825f-a88d6f21feac2d71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:15:55Z" - latency: 4.548845ms message: 'load-balancer-api-internal: tcp connection to a7aecbc0ed44546b284bc7334697825f-a88d6f21feac2d71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:14:55Z" - latency: 7.249904ms message: 'load-balancer-api-internal: resolved host name a7aecbc0ed44546b284bc7334697825f-a88d6f21feac2d71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:14:55Z" - latency: 5.355849ms message: 'load-balancer-api-internal: tcp connection to a7aecbc0ed44546b284bc7334697825f-a88d6f21feac2d71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:13:55Z" - latency: 7.217651ms message: 'load-balancer-api-internal: resolved host name a7aecbc0ed44546b284bc7334697825f-a88d6f21feac2d71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:13:55Z" - latency: 5.371921ms message: 'load-balancer-api-internal: tcp connection to a7aecbc0ed44546b284bc7334697825f-a88d6f21feac2d71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:12:55Z" - latency: 7.569061ms message: 'load-balancer-api-internal: resolved host name a7aecbc0ed44546b284bc7334697825f-a88d6f21feac2d71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:12:55Z" - latency: 4.534388ms message: 'load-balancer-api-internal: tcp connection to a7aecbc0ed44546b284bc7334697825f-a88d6f21feac2d71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:11:55Z" - latency: 9.279404ms message: 'load-balancer-api-internal: resolved host name a7aecbc0ed44546b284bc7334697825f-a88d6f21feac2d71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:11:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:27:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-30-to-network-check-target-ip-10-0-132-183 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-30.ec2.internal uid: a9aeb023-1047-44e0-912b-e3a22d7469f6 resourceVersion: "68841" uid: 87606312-232a-4906-b2c5-80b7c6600700 spec: sourcePod: network-check-source-7bc5b6bf85-kf252 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-17T17:34:55Z" message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.685235ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:16:55Z" - latency: 2.482625ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:15:55Z" - latency: 2.270408ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:14:55Z" - latency: 2.457537ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:13:55Z" - latency: 2.389106ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:12:55Z" - latency: 2.451102ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:11:55Z" - latency: 2.159713ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:10:55Z" - latency: 2.37117ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:09:55Z" - latency: 2.612889ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:08:55Z" - latency: 2.2095ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:07:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:27:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-30-to-network-check-target-ip-10-0-135-30 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-30.ec2.internal uid: a9aeb023-1047-44e0-912b-e3a22d7469f6 resourceVersion: "68840" uid: 1d5d7eea-1d2b-4078-85e3-85637a846d21 spec: sourcePod: network-check-source-7bc5b6bf85-kf252 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-17T17:34:55Z" message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.597851ms message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:16:55Z" - latency: 1.494636ms message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:15:55Z" - latency: 1.031611ms message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:14:55Z" - latency: 962.86µs message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:13:55Z" - latency: 945.459µs message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:12:55Z" - latency: 1.584642ms message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:11:55Z" - latency: 976.981µs message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:10:55Z" - latency: 981.102µs message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:09:55Z" - latency: 1.633933ms message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:08:55Z" - latency: 1.121478ms message: 'network-check-target-ip-10-0-135-30: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:07:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:27:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-30-to-network-check-target-ip-10-0-143-187 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-30.ec2.internal uid: a9aeb023-1047-44e0-912b-e3a22d7469f6 resourceVersion: "68842" uid: 0c8fed5d-ad9d-410b-af60-0a5443599372 spec: sourcePod: network-check-source-7bc5b6bf85-kf252 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-17T17:34:55Z" message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.656369ms message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:16:55Z" - latency: 2.621195ms message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:15:55Z" - latency: 2.407053ms message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:14:55Z" - latency: 2.502648ms message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:13:55Z" - latency: 2.303627ms message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:12:55Z" - latency: 2.699413ms message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:11:55Z" - latency: 2.417686ms message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:10:55Z" - latency: 2.562164ms message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:09:55Z" - latency: 2.828617ms message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:08:55Z" - latency: 2.345602ms message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:07:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:27:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-30-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-30.ec2.internal uid: a9aeb023-1047-44e0-912b-e3a22d7469f6 resourceVersion: "67869" uid: 3a082c39-676f-4d50-92d7-230d2cc780ca spec: sourcePod: network-check-source-7bc5b6bf85-kf252 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-17T17:33:55Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.059384ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:15:55Z" - latency: 2.177402ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:15:55Z" - latency: 991.112µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:14:55Z" - latency: 1.881156ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:14:55Z" - latency: 911.644µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:13:55Z" - latency: 1.796109ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:13:55Z" - latency: 1.154997ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:12:55Z" - latency: 2.24143ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:12:55Z" - latency: 982.691µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:11:55Z" - latency: 2.175817ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:11:55Z" kind: List metadata: resourceVersion: ""