apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T12:33:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-41-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-41.us-east-2.compute.internal uid: 79037749-7124-47f8-aad9-636da0ae9fe6 resourceVersion: "233102" uid: 97412adf-0594-4e81-aa81-1e4987cae943 spec: sourcePod: network-check-source-6f78d59f99-62jh5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-31T12:40:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.300319ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:04:51Z" - latency: 1.316147ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:03:51Z" - latency: 2.161537ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:02:51Z" - latency: 1.120574ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:01:51Z" - latency: 1.107275ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:00:51Z" - latency: 16.242168ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:59:51Z" - latency: 1.371774ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:58:51Z" - latency: 1.190937ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:57:51Z" - latency: 1.22312ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:56:51Z" - latency: 1.231765ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:55:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T12:33:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-41-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-41.us-east-2.compute.internal uid: 79037749-7124-47f8-aad9-636da0ae9fe6 resourceVersion: "237142" uid: 411fa9dc-2337-4f48-8ca7-bebca28f1c9b spec: sourcePod: network-check-source-6f78d59f99-62jh5 targetEndpoint: a3868a2066fc74e75951cc94f05315f5-1a68c2abc67761e0.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T12:39:51Z" message: 'load-balancer-api-external: tcp connection to a3868a2066fc74e75951cc94f05315f5-1a68c2abc67761e0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.77582ms message: 'load-balancer-api-external: tcp connection to a3868a2066fc74e75951cc94f05315f5-1a68c2abc67761e0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:09:51Z" - latency: 22.036198ms message: 'load-balancer-api-external: resolved host name a3868a2066fc74e75951cc94f05315f5-1a68c2abc67761e0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T14:09:51Z" - latency: 5.217137ms message: 'load-balancer-api-external: tcp connection to a3868a2066fc74e75951cc94f05315f5-1a68c2abc67761e0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:08:51Z" - latency: 12.391812ms message: 'load-balancer-api-external: resolved host name a3868a2066fc74e75951cc94f05315f5-1a68c2abc67761e0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T14:08:51Z" - latency: 5.283405ms message: 'load-balancer-api-external: tcp connection to a3868a2066fc74e75951cc94f05315f5-1a68c2abc67761e0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:07:51Z" - latency: 7.304199ms message: 'load-balancer-api-external: resolved host name a3868a2066fc74e75951cc94f05315f5-1a68c2abc67761e0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T14:07:51Z" - latency: 6.574903ms message: 'load-balancer-api-external: tcp connection to a3868a2066fc74e75951cc94f05315f5-1a68c2abc67761e0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:06:51Z" - latency: 11.404092ms message: 'load-balancer-api-external: resolved host name a3868a2066fc74e75951cc94f05315f5-1a68c2abc67761e0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T14:06:51Z" - latency: 5.236138ms message: 'load-balancer-api-external: tcp connection to a3868a2066fc74e75951cc94f05315f5-1a68c2abc67761e0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:05:51Z" - latency: 8.311ms message: 'load-balancer-api-external: resolved host name a3868a2066fc74e75951cc94f05315f5-1a68c2abc67761e0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T14:05:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T12:33:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-41-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-41.us-east-2.compute.internal uid: 79037749-7124-47f8-aad9-636da0ae9fe6 resourceVersion: "237143" uid: e7840ea9-91bd-4e02-b68b-1d42e397a9ac spec: sourcePod: network-check-source-6f78d59f99-62jh5 targetEndpoint: a3868a2066fc74e75951cc94f05315f5-1a68c2abc67761e0.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T12:39:51Z" message: 'load-balancer-api-internal: tcp connection to a3868a2066fc74e75951cc94f05315f5-1a68c2abc67761e0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.736871ms message: 'load-balancer-api-internal: tcp connection to a3868a2066fc74e75951cc94f05315f5-1a68c2abc67761e0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:09:51Z" - latency: 21.43664ms message: 'load-balancer-api-internal: resolved host name a3868a2066fc74e75951cc94f05315f5-1a68c2abc67761e0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T14:09:51Z" - latency: 5.23018ms message: 'load-balancer-api-internal: tcp connection to a3868a2066fc74e75951cc94f05315f5-1a68c2abc67761e0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:08:51Z" - latency: 12.09033ms message: 'load-balancer-api-internal: resolved host name a3868a2066fc74e75951cc94f05315f5-1a68c2abc67761e0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T14:08:51Z" - latency: 5.660964ms message: 'load-balancer-api-internal: tcp connection to a3868a2066fc74e75951cc94f05315f5-1a68c2abc67761e0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:07:51Z" - latency: 7.384067ms message: 'load-balancer-api-internal: resolved host name a3868a2066fc74e75951cc94f05315f5-1a68c2abc67761e0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T14:07:51Z" - latency: 7.099298ms message: 'load-balancer-api-internal: tcp connection to a3868a2066fc74e75951cc94f05315f5-1a68c2abc67761e0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:06:51Z" - latency: 10.91008ms message: 'load-balancer-api-internal: resolved host name a3868a2066fc74e75951cc94f05315f5-1a68c2abc67761e0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T14:06:51Z" - latency: 5.197065ms message: 'load-balancer-api-internal: tcp connection to a3868a2066fc74e75951cc94f05315f5-1a68c2abc67761e0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:05:51Z" - latency: 8.408175ms message: 'load-balancer-api-internal: resolved host name a3868a2066fc74e75951cc94f05315f5-1a68c2abc67761e0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T14:05:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T12:33:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-41-to-network-check-target-ip-10-0-131-157 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-41.us-east-2.compute.internal uid: 79037749-7124-47f8-aad9-636da0ae9fe6 resourceVersion: "233101" uid: 9cd3bfd2-896f-4831-a4f6-b33c2ecfd149 spec: sourcePod: network-check-source-6f78d59f99-62jh5 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-31T12:40:51Z" message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.213257ms message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:04:51Z" - latency: 2.339734ms message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:03:51Z" - latency: 2.786908ms message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:02:51Z" - latency: 2.450631ms message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:01:51Z" - latency: 2.457999ms message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:00:51Z" - latency: 5.735003ms message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:59:51Z" - latency: 2.306832ms message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:58:51Z" - latency: 2.705902ms message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:57:51Z" - latency: 2.3961ms message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:56:51Z" - latency: 2.337773ms message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:55:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T12:33:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-41-to-network-check-target-ip-10-0-135-41 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-41.us-east-2.compute.internal uid: 79037749-7124-47f8-aad9-636da0ae9fe6 resourceVersion: "233099" uid: 53b3e151-dded-46ba-ab05-97226f64631f spec: sourcePod: network-check-source-6f78d59f99-62jh5 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-31T12:40:51Z" message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.044888ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:04:51Z" - latency: 1.498202ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:03:51Z" - latency: 1.829439ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:02:51Z" - latency: 1.639625ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:01:51Z" - latency: 1.039856ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:00:51Z" - latency: 5.107345ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:59:51Z" - latency: 1.175963ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:58:51Z" - latency: 1.109084ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:57:51Z" - latency: 1.512497ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:56:51Z" - latency: 1.013247ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:55:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T12:33:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-41-to-network-check-target-ip-10-0-138-70 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-41.us-east-2.compute.internal uid: 79037749-7124-47f8-aad9-636da0ae9fe6 resourceVersion: "233100" uid: 31a3bae9-2e8d-4360-a603-7b2832dd21bc spec: sourcePod: network-check-source-6f78d59f99-62jh5 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-31T12:40:51Z" message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.140861ms message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:04:51Z" - latency: 2.189853ms message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:03:51Z" - latency: 2.564564ms message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:02:51Z" - latency: 2.099279ms message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:01:51Z" - latency: 2.228639ms message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:00:51Z" - latency: 13.961049ms message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:59:51Z" - latency: 2.244997ms message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:58:51Z" - latency: 2.312128ms message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:57:51Z" - latency: 2.188605ms message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:56:51Z" - latency: 2.246544ms message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:55:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T12:33:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-41-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-41.us-east-2.compute.internal uid: 79037749-7124-47f8-aad9-636da0ae9fe6 resourceVersion: "237140" uid: a097eb59-350f-4518-b5c1-e1c92c96c969 spec: sourcePod: network-check-source-6f78d59f99-62jh5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-31T12:39:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.191526ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:09:51Z" - latency: 16.510756ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T14:09:51Z" - latency: 2.117646ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:08:51Z" - latency: 5.382571ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T14:08:51Z" - latency: 1.410141ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:07:51Z" - latency: 1.84175ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T14:07:51Z" - latency: 1.141822ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:06:51Z" - latency: 5.756739ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T14:06:51Z" - latency: 1.043369ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T14:05:51Z" - latency: 2.355276ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T14:05:51Z" kind: List metadata: resourceVersion: ""