apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T21:16:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-43-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-43.us-west-1.compute.internal uid: fcb22f1e-864f-42a7-af16-3bee11111324 resourceVersion: "110988" uid: f866bcc5-cbd4-45ef-952b-0cb92787e018 spec: sourcePod: network-check-source-6f78d59f99-sb5xl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T21:23:11Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.85903ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:19:11Z" - latency: 10.28716ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:18:11Z" - latency: 2.189583ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:17:11Z" - latency: 1.177018ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:16:11Z" - latency: 1.56304ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:15:11Z" - latency: 1.175116ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:14:11Z" - latency: 1.91438ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:13:11Z" - latency: 983.868µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:12:11Z" - latency: 1.272098ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:11:11Z" - latency: 1.055407ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:10:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T21:16:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-43-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-43.us-west-1.compute.internal uid: fcb22f1e-864f-42a7-af16-3bee11111324 resourceVersion: "116098" uid: dfaafec1-7869-45c0-9ab1-199e75060f69 spec: sourcePod: network-check-source-6f78d59f99-sb5xl targetEndpoint: a272bc74d03104c58bb06e21328e27dc-41a6df2b1383438f.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T21:22:11Z" message: 'load-balancer-api-external: tcp connection to a272bc74d03104c58bb06e21328e27dc-41a6df2b1383438f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.613861ms message: 'load-balancer-api-external: tcp connection to a272bc74d03104c58bb06e21328e27dc-41a6df2b1383438f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:22:11Z" - latency: 7.559913ms message: 'load-balancer-api-external: resolved host name a272bc74d03104c58bb06e21328e27dc-41a6df2b1383438f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T22:22:11Z" - latency: 53.714299ms message: 'load-balancer-api-external: tcp connection to a272bc74d03104c58bb06e21328e27dc-41a6df2b1383438f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:21:11Z" - latency: 7.173465ms message: 'load-balancer-api-external: resolved host name a272bc74d03104c58bb06e21328e27dc-41a6df2b1383438f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T22:21:11Z" - latency: 53.319604ms message: 'load-balancer-api-external: tcp connection to a272bc74d03104c58bb06e21328e27dc-41a6df2b1383438f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:20:11Z" - latency: 7.014481ms message: 'load-balancer-api-external: resolved host name a272bc74d03104c58bb06e21328e27dc-41a6df2b1383438f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T22:20:11Z" - latency: 52.971371ms message: 'load-balancer-api-external: tcp connection to a272bc74d03104c58bb06e21328e27dc-41a6df2b1383438f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:19:11Z" - latency: 6.500508ms message: 'load-balancer-api-external: resolved host name a272bc74d03104c58bb06e21328e27dc-41a6df2b1383438f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T22:19:11Z" - latency: 57.510007ms message: 'load-balancer-api-external: tcp connection to a272bc74d03104c58bb06e21328e27dc-41a6df2b1383438f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:18:11Z" - latency: 65.752038ms message: 'load-balancer-api-external: resolved host name a272bc74d03104c58bb06e21328e27dc-41a6df2b1383438f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T22:18:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T21:16:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-43-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-43.us-west-1.compute.internal uid: fcb22f1e-864f-42a7-af16-3bee11111324 resourceVersion: "116099" uid: f4aa9fe8-9435-405e-a40c-90204f6a6442 spec: sourcePod: network-check-source-6f78d59f99-sb5xl targetEndpoint: a272bc74d03104c58bb06e21328e27dc-41a6df2b1383438f.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T21:22:11Z" message: 'load-balancer-api-internal: tcp connection to a272bc74d03104c58bb06e21328e27dc-41a6df2b1383438f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.622954ms message: 'load-balancer-api-internal: tcp connection to a272bc74d03104c58bb06e21328e27dc-41a6df2b1383438f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:22:11Z" - latency: 7.502841ms message: 'load-balancer-api-internal: resolved host name a272bc74d03104c58bb06e21328e27dc-41a6df2b1383438f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T22:22:11Z" - latency: 52.748879ms message: 'load-balancer-api-internal: tcp connection to a272bc74d03104c58bb06e21328e27dc-41a6df2b1383438f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:21:11Z" - latency: 7.150332ms message: 'load-balancer-api-internal: resolved host name a272bc74d03104c58bb06e21328e27dc-41a6df2b1383438f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T22:21:11Z" - latency: 53.28816ms message: 'load-balancer-api-internal: tcp connection to a272bc74d03104c58bb06e21328e27dc-41a6df2b1383438f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:20:11Z" - latency: 6.96331ms message: 'load-balancer-api-internal: resolved host name a272bc74d03104c58bb06e21328e27dc-41a6df2b1383438f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T22:20:11Z" - latency: 52.738984ms message: 'load-balancer-api-internal: tcp connection to a272bc74d03104c58bb06e21328e27dc-41a6df2b1383438f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:19:11Z" - latency: 6.445263ms message: 'load-balancer-api-internal: resolved host name a272bc74d03104c58bb06e21328e27dc-41a6df2b1383438f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T22:19:11Z" - latency: 57.154512ms message: 'load-balancer-api-internal: tcp connection to a272bc74d03104c58bb06e21328e27dc-41a6df2b1383438f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:18:11Z" - latency: 65.399836ms message: 'load-balancer-api-internal: resolved host name a272bc74d03104c58bb06e21328e27dc-41a6df2b1383438f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T22:18:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T21:16:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-43-to-network-check-target-ip-10-0-128-179 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-43.us-west-1.compute.internal uid: fcb22f1e-864f-42a7-af16-3bee11111324 resourceVersion: "110985" uid: c744f056-bf35-465b-8d34-ef175332e66f spec: sourcePod: network-check-source-6f78d59f99-sb5xl targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T21:23:11Z" message: 'network-check-target-ip-10-0-128-179: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.715744ms message: 'network-check-target-ip-10-0-128-179: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:19:11Z" - latency: 10.249428ms message: 'network-check-target-ip-10-0-128-179: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:18:11Z" - latency: 4.010729ms message: 'network-check-target-ip-10-0-128-179: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:17:11Z" - latency: 2.70563ms message: 'network-check-target-ip-10-0-128-179: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:16:11Z" - latency: 2.445922ms message: 'network-check-target-ip-10-0-128-179: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:15:11Z" - latency: 2.049658ms message: 'network-check-target-ip-10-0-128-179: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:14:11Z" - latency: 2.839091ms message: 'network-check-target-ip-10-0-128-179: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:13:11Z" - latency: 3.243631ms message: 'network-check-target-ip-10-0-128-179: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:12:11Z" - latency: 2.279111ms message: 'network-check-target-ip-10-0-128-179: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:11:11Z" - latency: 6.415165ms message: 'network-check-target-ip-10-0-128-179: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:10:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T21:16:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-43-to-network-check-target-ip-10-0-128-43 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-43.us-west-1.compute.internal uid: fcb22f1e-864f-42a7-af16-3bee11111324 resourceVersion: "110984" uid: 87e913d4-0c88-4cc8-b509-89dab8a9972d spec: sourcePod: network-check-source-6f78d59f99-sb5xl targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T21:23:11Z" message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 958.513µs message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:19:11Z" - latency: 9.574635ms message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:18:11Z" - latency: 2.715325ms message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:17:11Z" - latency: 2.297489ms message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:16:11Z" - latency: 1.41024ms message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:15:11Z" - latency: 1.083114ms message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:14:11Z" - latency: 1.610066ms message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:13:11Z" - latency: 1.009257ms message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:12:11Z" - latency: 1.494821ms message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:11:11Z" - latency: 1.063502ms message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:10:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T21:16:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-43-to-network-check-target-ip-10-0-129-65 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-43.us-west-1.compute.internal uid: fcb22f1e-864f-42a7-af16-3bee11111324 resourceVersion: "110987" uid: 0f728c52-6a14-4fff-9f16-753d2b1ad10b spec: sourcePod: network-check-source-6f78d59f99-sb5xl targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T21:23:11Z" message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.761555ms message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:19:11Z" - latency: 17.427951ms message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:18:11Z" - latency: 4.032997ms message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:17:11Z" - latency: 2.99468ms message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:16:11Z" - latency: 2.325654ms message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:15:11Z" - latency: 2.562637ms message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:14:11Z" - latency: 2.617787ms message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:13:11Z" - latency: 3.694976ms message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:12:11Z" - latency: 2.50235ms message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:11:11Z" - latency: 2.290541ms message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:10:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T21:16:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-43-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-43.us-west-1.compute.internal uid: fcb22f1e-864f-42a7-af16-3bee11111324 resourceVersion: "116096" uid: 7a8eaecb-94c2-4383-b447-99a0114e7e1a spec: sourcePod: network-check-source-6f78d59f99-sb5xl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T21:22:11Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.029165ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:22:11Z" - latency: 597.581µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T22:22:11Z" - latency: 1.131961ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:21:11Z" - latency: 714.792µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T22:21:11Z" - latency: 1.113136ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:20:11Z" - latency: 652.374µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T22:20:11Z" - latency: 928.347µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:19:11Z" - latency: 564.302µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T22:19:11Z" - latency: 5.882922ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:18:11Z" - latency: 7.085344ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T22:18:11Z" kind: List metadata: resourceVersion: ""