apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:21:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-135-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-135.us-east-2.compute.internal uid: a214deb9-295e-488f-82ef-a5aa875334cf resourceVersion: "69503" uid: 69e4391e-97db-42f5-8c31-36788f89e225 spec: sourcePod: network-check-source-6f78d59f99-vkgxb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T19:28:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 912.215µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:49:02Z" - latency: 1.234798ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:48:02Z" - latency: 892.234µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:47:02Z" - latency: 1.259181ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:46:02Z" - latency: 997.584µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:45:02Z" - latency: 1.13178ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:44:02Z" - latency: 866.072µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:43:02Z" - latency: 1.12812ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:42:02Z" - latency: 1.177534ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:41:02Z" - latency: 967.656µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:40:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:21:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-135-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-135.us-east-2.compute.internal uid: a214deb9-295e-488f-82ef-a5aa875334cf resourceVersion: "70838" uid: c5de8df7-83a7-4767-8638-05c17c010097 spec: sourcePod: network-check-source-6f78d59f99-vkgxb targetEndpoint: a652b2e9a111d4566a54c89c285ff359-8cf20b6a957bdfa0.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T19:27:02Z" message: 'load-balancer-api-external: tcp connection to a652b2e9a111d4566a54c89c285ff359-8cf20b6a957bdfa0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.510507ms message: 'load-balancer-api-external: tcp connection to a652b2e9a111d4566a54c89c285ff359-8cf20b6a957bdfa0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:51:02Z" - latency: 9.74629ms message: 'load-balancer-api-external: resolved host name a652b2e9a111d4566a54c89c285ff359-8cf20b6a957bdfa0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:51:02Z" - latency: 5.052277ms message: 'load-balancer-api-external: tcp connection to a652b2e9a111d4566a54c89c285ff359-8cf20b6a957bdfa0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:50:02Z" - latency: 6.445994ms message: 'load-balancer-api-external: resolved host name a652b2e9a111d4566a54c89c285ff359-8cf20b6a957bdfa0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:50:02Z" - latency: 17.173434ms message: 'load-balancer-api-external: tcp connection to a652b2e9a111d4566a54c89c285ff359-8cf20b6a957bdfa0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:49:02Z" - latency: 6.457854ms message: 'load-balancer-api-external: resolved host name a652b2e9a111d4566a54c89c285ff359-8cf20b6a957bdfa0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:49:02Z" - latency: 5.484184ms message: 'load-balancer-api-external: tcp connection to a652b2e9a111d4566a54c89c285ff359-8cf20b6a957bdfa0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:48:02Z" - latency: 7.703968ms message: 'load-balancer-api-external: resolved host name a652b2e9a111d4566a54c89c285ff359-8cf20b6a957bdfa0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:48:02Z" - latency: 9.043042ms message: 'load-balancer-api-external: tcp connection to a652b2e9a111d4566a54c89c285ff359-8cf20b6a957bdfa0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:47:02Z" - latency: 7.562156ms message: 'load-balancer-api-external: resolved host name a652b2e9a111d4566a54c89c285ff359-8cf20b6a957bdfa0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:47:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:21:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-135-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-135.us-east-2.compute.internal uid: a214deb9-295e-488f-82ef-a5aa875334cf resourceVersion: "70839" uid: 7ad3b75d-9db4-41ff-8ef4-25d20b719e34 spec: sourcePod: network-check-source-6f78d59f99-vkgxb targetEndpoint: a652b2e9a111d4566a54c89c285ff359-8cf20b6a957bdfa0.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T19:27:02Z" message: 'load-balancer-api-internal: tcp connection to a652b2e9a111d4566a54c89c285ff359-8cf20b6a957bdfa0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.525641ms message: 'load-balancer-api-internal: tcp connection to a652b2e9a111d4566a54c89c285ff359-8cf20b6a957bdfa0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:51:02Z" - latency: 9.665991ms message: 'load-balancer-api-internal: resolved host name a652b2e9a111d4566a54c89c285ff359-8cf20b6a957bdfa0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:51:02Z" - latency: 5.063021ms message: 'load-balancer-api-internal: tcp connection to a652b2e9a111d4566a54c89c285ff359-8cf20b6a957bdfa0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:50:02Z" - latency: 6.516706ms message: 'load-balancer-api-internal: resolved host name a652b2e9a111d4566a54c89c285ff359-8cf20b6a957bdfa0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:50:02Z" - latency: 20.378695ms message: 'load-balancer-api-internal: tcp connection to a652b2e9a111d4566a54c89c285ff359-8cf20b6a957bdfa0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:49:02Z" - latency: 6.370668ms message: 'load-balancer-api-internal: resolved host name a652b2e9a111d4566a54c89c285ff359-8cf20b6a957bdfa0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:49:02Z" - latency: 6.335741ms message: 'load-balancer-api-internal: tcp connection to a652b2e9a111d4566a54c89c285ff359-8cf20b6a957bdfa0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:48:02Z" - latency: 7.737749ms message: 'load-balancer-api-internal: resolved host name a652b2e9a111d4566a54c89c285ff359-8cf20b6a957bdfa0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:48:02Z" - latency: 9.951716ms message: 'load-balancer-api-internal: tcp connection to a652b2e9a111d4566a54c89c285ff359-8cf20b6a957bdfa0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:47:02Z" - latency: 7.570749ms message: 'load-balancer-api-internal: resolved host name a652b2e9a111d4566a54c89c285ff359-8cf20b6a957bdfa0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:47:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:21:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-135-to-network-check-target-ip-10-0-132-153 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-135.us-east-2.compute.internal uid: a214deb9-295e-488f-82ef-a5aa875334cf resourceVersion: "69502" uid: 8273a172-c4a5-4894-9c45-5c7088255871 spec: sourcePod: network-check-source-6f78d59f99-vkgxb targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T19:28:02Z" message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.140875ms message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:49:02Z" - latency: 2.609952ms message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:48:02Z" - latency: 8.936518ms message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:47:02Z" - latency: 2.434038ms message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:46:02Z" - latency: 2.63647ms message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:45:02Z" - latency: 2.44993ms message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:44:02Z" - latency: 2.252439ms message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:43:02Z" - latency: 2.640952ms message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:42:02Z" - latency: 2.517824ms message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:41:02Z" - latency: 2.314144ms message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:40:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:21:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-135-to-network-check-target-ip-10-0-139-211 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-135.us-east-2.compute.internal uid: a214deb9-295e-488f-82ef-a5aa875334cf resourceVersion: "69501" uid: 25a2a876-1b93-49b3-a88a-1628b7794cc5 spec: sourcePod: network-check-source-6f78d59f99-vkgxb targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T19:28:02Z" message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.477031ms message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:49:02Z" - latency: 1.734856ms message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:48:02Z" - latency: 2.658514ms message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:47:02Z" - latency: 2.109717ms message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:46:02Z" - latency: 2.413066ms message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:45:02Z" - latency: 2.255689ms message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:44:02Z" - latency: 2.193074ms message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:43:02Z" - latency: 2.257609ms message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:42:02Z" - latency: 2.446458ms message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:41:02Z" - latency: 2.741493ms message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:40:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:21:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-135-to-network-check-target-ip-10-0-143-135 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-135.us-east-2.compute.internal uid: a214deb9-295e-488f-82ef-a5aa875334cf resourceVersion: "69500" uid: c5b0ef1e-e018-4daa-8baa-4ab00b6e8cd1 spec: sourcePod: network-check-source-6f78d59f99-vkgxb targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T19:28:02Z" message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 676.586µs message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:49:02Z" - latency: 813.016µs message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:48:02Z" - latency: 1.473895ms message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:47:02Z" - latency: 1.393275ms message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:46:02Z" - latency: 807.451µs message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:45:02Z" - latency: 828.77µs message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:44:02Z" - latency: 1.536262ms message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:43:02Z" - latency: 923.11µs message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:42:02Z" - latency: 859.883µs message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:41:02Z" - latency: 847.423µs message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:40:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:21:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-135-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-135.us-east-2.compute.internal uid: a214deb9-295e-488f-82ef-a5aa875334cf resourceVersion: "70837" uid: 7b65af0a-b0bf-47c7-9381-1be742383189 spec: sourcePod: network-check-source-6f78d59f99-vkgxb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T19:27:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.013617ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:51:02Z" - latency: 1.969419ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:51:02Z" - latency: 999.279µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:50:02Z" - latency: 1.7936ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:50:02Z" - latency: 916.229µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:49:02Z" - latency: 1.631033ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:49:02Z" - latency: 1.048297ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:48:02Z" - latency: 1.987203ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:48:02Z" - latency: 948.947µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:47:02Z" - latency: 2.243615ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:47:02Z" kind: List metadata: resourceVersion: ""