apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T18:01:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-147-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-147.ec2.internal uid: e5c4d9ae-f5a8-4412-bc60-dae994eab1b6 resourceVersion: "63281" uid: 951f8084-b3ba-471f-a25f-b65f6a0ccd68 spec: sourcePod: network-check-source-7bc5b6bf85-lhjwd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-23T18:08:06Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.480927ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:43:06Z" - latency: 822.562µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:42:06Z" - latency: 985.067µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:41:06Z" - latency: 742.99µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:40:06Z" - latency: 918.512µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:39:06Z" - latency: 1.075726ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:38:06Z" - latency: 1.094607ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:37:06Z" - latency: 913.972µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:36:06Z" - latency: 1.247097ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:35:06Z" - latency: 1.199778ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:34:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T18:01:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-147-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-147.ec2.internal uid: e5c4d9ae-f5a8-4412-bc60-dae994eab1b6 resourceVersion: "63283" uid: 845b4b7c-04d4-4234-ac8b-d378a599a240 spec: sourcePod: network-check-source-7bc5b6bf85-lhjwd targetEndpoint: ae7bb08bc70a4477c953dcd137781703-aa524030cb99a9a5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T18:07:06Z" message: 'load-balancer-api-external: tcp connection to ae7bb08bc70a4477c953dcd137781703-aa524030cb99a9a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.801316ms message: 'load-balancer-api-external: tcp connection to ae7bb08bc70a4477c953dcd137781703-aa524030cb99a9a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:43:06Z" - latency: 10.61643ms message: 'load-balancer-api-external: resolved host name ae7bb08bc70a4477c953dcd137781703-aa524030cb99a9a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T18:43:06Z" - latency: 4.568388ms message: 'load-balancer-api-external: tcp connection to ae7bb08bc70a4477c953dcd137781703-aa524030cb99a9a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:42:06Z" - latency: 6.554977ms message: 'load-balancer-api-external: resolved host name ae7bb08bc70a4477c953dcd137781703-aa524030cb99a9a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T18:42:06Z" - latency: 5.115736ms message: 'load-balancer-api-external: tcp connection to ae7bb08bc70a4477c953dcd137781703-aa524030cb99a9a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:41:06Z" - latency: 6.950205ms message: 'load-balancer-api-external: resolved host name ae7bb08bc70a4477c953dcd137781703-aa524030cb99a9a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T18:41:06Z" - latency: 4.217034ms message: 'load-balancer-api-external: tcp connection to ae7bb08bc70a4477c953dcd137781703-aa524030cb99a9a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:40:06Z" - latency: 7.168193ms message: 'load-balancer-api-external: resolved host name ae7bb08bc70a4477c953dcd137781703-aa524030cb99a9a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T18:40:06Z" - latency: 3.504216ms message: 'load-balancer-api-external: tcp connection to ae7bb08bc70a4477c953dcd137781703-aa524030cb99a9a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:39:06Z" - latency: 6.786154ms message: 'load-balancer-api-external: resolved host name ae7bb08bc70a4477c953dcd137781703-aa524030cb99a9a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T18:39:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T18:01:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-147-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-147.ec2.internal uid: e5c4d9ae-f5a8-4412-bc60-dae994eab1b6 resourceVersion: "63282" uid: 46116356-a499-4aa0-a285-d2042bbaf6dd spec: sourcePod: network-check-source-7bc5b6bf85-lhjwd targetEndpoint: ae7bb08bc70a4477c953dcd137781703-aa524030cb99a9a5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T18:07:06Z" message: 'load-balancer-api-internal: tcp connection to ae7bb08bc70a4477c953dcd137781703-aa524030cb99a9a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.832647ms message: 'load-balancer-api-internal: tcp connection to ae7bb08bc70a4477c953dcd137781703-aa524030cb99a9a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:43:06Z" - latency: 10.547387ms message: 'load-balancer-api-internal: resolved host name ae7bb08bc70a4477c953dcd137781703-aa524030cb99a9a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T18:43:06Z" - latency: 4.952807ms message: 'load-balancer-api-internal: tcp connection to ae7bb08bc70a4477c953dcd137781703-aa524030cb99a9a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:42:06Z" - latency: 6.532234ms message: 'load-balancer-api-internal: resolved host name ae7bb08bc70a4477c953dcd137781703-aa524030cb99a9a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T18:42:06Z" - latency: 3.831004ms message: 'load-balancer-api-internal: tcp connection to ae7bb08bc70a4477c953dcd137781703-aa524030cb99a9a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:41:06Z" - latency: 6.903286ms message: 'load-balancer-api-internal: resolved host name ae7bb08bc70a4477c953dcd137781703-aa524030cb99a9a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T18:41:06Z" - latency: 4.737147ms message: 'load-balancer-api-internal: tcp connection to ae7bb08bc70a4477c953dcd137781703-aa524030cb99a9a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:40:06Z" - latency: 7.111198ms message: 'load-balancer-api-internal: resolved host name ae7bb08bc70a4477c953dcd137781703-aa524030cb99a9a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T18:40:06Z" - latency: 3.409089ms message: 'load-balancer-api-internal: tcp connection to ae7bb08bc70a4477c953dcd137781703-aa524030cb99a9a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:39:06Z" - latency: 6.656052ms message: 'load-balancer-api-internal: resolved host name ae7bb08bc70a4477c953dcd137781703-aa524030cb99a9a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T18:39:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T18:01:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-147-to-network-check-target-ip-10-0-129-70 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-147.ec2.internal uid: e5c4d9ae-f5a8-4412-bc60-dae994eab1b6 resourceVersion: "63278" uid: 4ab72686-b6f8-4702-9887-2b234db047d7 spec: sourcePod: network-check-source-7bc5b6bf85-lhjwd targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-23T18:08:06Z" message: 'network-check-target-ip-10-0-129-70: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.502716ms message: 'network-check-target-ip-10-0-129-70: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:43:06Z" - latency: 2.235856ms message: 'network-check-target-ip-10-0-129-70: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:42:06Z" - latency: 2.346332ms message: 'network-check-target-ip-10-0-129-70: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:41:06Z" - latency: 2.286177ms message: 'network-check-target-ip-10-0-129-70: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:40:06Z" - latency: 2.280317ms message: 'network-check-target-ip-10-0-129-70: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:39:06Z" - latency: 2.706167ms message: 'network-check-target-ip-10-0-129-70: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:38:06Z" - latency: 2.383936ms message: 'network-check-target-ip-10-0-129-70: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:37:06Z" - latency: 2.281173ms message: 'network-check-target-ip-10-0-129-70: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:36:06Z" - latency: 2.362853ms message: 'network-check-target-ip-10-0-129-70: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:35:06Z" - latency: 2.271317ms message: 'network-check-target-ip-10-0-129-70: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:34:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T18:01:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-147-to-network-check-target-ip-10-0-129-71 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-147.ec2.internal uid: e5c4d9ae-f5a8-4412-bc60-dae994eab1b6 resourceVersion: "63277" uid: 1e230506-77ae-46e3-b56b-482ab5b850ed spec: sourcePod: network-check-source-7bc5b6bf85-lhjwd targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-23T18:08:06Z" message: 'network-check-target-ip-10-0-129-71: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.148862ms message: 'network-check-target-ip-10-0-129-71: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:43:06Z" - latency: 2.231031ms message: 'network-check-target-ip-10-0-129-71: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:42:06Z" - latency: 2.301758ms message: 'network-check-target-ip-10-0-129-71: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:41:06Z" - latency: 1.782363ms message: 'network-check-target-ip-10-0-129-71: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:40:06Z" - latency: 1.920006ms message: 'network-check-target-ip-10-0-129-71: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:39:06Z" - latency: 2.206261ms message: 'network-check-target-ip-10-0-129-71: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:38:06Z" - latency: 2.349142ms message: 'network-check-target-ip-10-0-129-71: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:37:06Z" - latency: 2.136892ms message: 'network-check-target-ip-10-0-129-71: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:36:06Z" - latency: 2.469306ms message: 'network-check-target-ip-10-0-129-71: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:35:06Z" - latency: 2.077206ms message: 'network-check-target-ip-10-0-129-71: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:34:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T18:01:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-147-to-network-check-target-ip-10-0-142-147 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-147.ec2.internal uid: e5c4d9ae-f5a8-4412-bc60-dae994eab1b6 resourceVersion: "63279" uid: 00c73680-fa0c-4813-ae05-c26c00db8664 spec: sourcePod: network-check-source-7bc5b6bf85-lhjwd targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-23T18:08:06Z" message: 'network-check-target-ip-10-0-142-147: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.756985ms message: 'network-check-target-ip-10-0-142-147: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:43:06Z" - latency: 1.124209ms message: 'network-check-target-ip-10-0-142-147: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:42:06Z" - latency: 1.379814ms message: 'network-check-target-ip-10-0-142-147: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:41:06Z" - latency: 774.665µs message: 'network-check-target-ip-10-0-142-147: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:40:06Z" - latency: 809.214µs message: 'network-check-target-ip-10-0-142-147: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:39:06Z" - latency: 992.996µs message: 'network-check-target-ip-10-0-142-147: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:38:06Z" - latency: 899.412µs message: 'network-check-target-ip-10-0-142-147: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:37:06Z" - latency: 889.227µs message: 'network-check-target-ip-10-0-142-147: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:36:06Z" - latency: 827.747µs message: 'network-check-target-ip-10-0-142-147: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:35:06Z" - latency: 873.268µs message: 'network-check-target-ip-10-0-142-147: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:34:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T18:01:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-147-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-147.ec2.internal uid: e5c4d9ae-f5a8-4412-bc60-dae994eab1b6 resourceVersion: "63280" uid: aad2e79c-a55f-4251-bc80-21d99891275a spec: sourcePod: network-check-source-7bc5b6bf85-lhjwd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-23T18:07:06Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 877.238µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:43:06Z" - latency: 1.669615ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T18:43:06Z" - latency: 858.21µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:42:06Z" - latency: 1.811553ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T18:42:06Z" - latency: 999.234µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:41:06Z" - latency: 1.534715ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T18:41:06Z" - latency: 890.245µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:40:06Z" - latency: 2.397192ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T18:40:06Z" - latency: 916.167µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:39:06Z" - latency: 1.768404ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T18:39:06Z" kind: List metadata: resourceVersion: ""