apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T15:09:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-168-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-168.ec2.internal uid: 347fabb5-d399-4a3b-a5f0-c8cbc750baa9 resourceVersion: "25954" uid: 35478a08-d5be-4dc1-89dc-68c369c1e93d spec: sourcePod: network-check-source-8894fc9bd-nmq7h targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-22T15:17:00Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.329175ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:52:00Z" - latency: 1.497269ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:51:00Z" - latency: 921.281µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:50:00Z" - latency: 1.05685ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:49:00Z" - latency: 715.65µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:48:00Z" - latency: 868.306µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:47:00Z" - latency: 938.315µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:46:00Z" - latency: 950.074µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:45:00Z" - latency: 1.320415ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:44:00Z" - latency: 975.482µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:43:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T15:09:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-168-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-168.ec2.internal uid: 347fabb5-d399-4a3b-a5f0-c8cbc750baa9 resourceVersion: "25955" uid: d05b8bbf-c54b-4d71-bb6c-931eadd8127c spec: sourcePod: network-check-source-8894fc9bd-nmq7h targetEndpoint: af4be2b8e1ca6421f9c4b67f94b5d72b-81f45104c50f3fdf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T15:16:00Z" message: 'load-balancer-api-external: tcp connection to af4be2b8e1ca6421f9c4b67f94b5d72b-81f45104c50f3fdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.531784ms message: 'load-balancer-api-external: tcp connection to af4be2b8e1ca6421f9c4b67f94b5d72b-81f45104c50f3fdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:52:00Z" - latency: 8.974586ms message: 'load-balancer-api-external: resolved host name af4be2b8e1ca6421f9c4b67f94b5d72b-81f45104c50f3fdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T15:52:00Z" - latency: 5.515437ms message: 'load-balancer-api-external: tcp connection to af4be2b8e1ca6421f9c4b67f94b5d72b-81f45104c50f3fdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:51:00Z" - latency: 9.727574ms message: 'load-balancer-api-external: resolved host name af4be2b8e1ca6421f9c4b67f94b5d72b-81f45104c50f3fdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T15:51:00Z" - latency: 5.333611ms message: 'load-balancer-api-external: tcp connection to af4be2b8e1ca6421f9c4b67f94b5d72b-81f45104c50f3fdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:50:00Z" - latency: 8.690502ms message: 'load-balancer-api-external: resolved host name af4be2b8e1ca6421f9c4b67f94b5d72b-81f45104c50f3fdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T15:50:00Z" - latency: 5.092827ms message: 'load-balancer-api-external: tcp connection to af4be2b8e1ca6421f9c4b67f94b5d72b-81f45104c50f3fdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:49:00Z" - latency: 7.762694ms message: 'load-balancer-api-external: resolved host name af4be2b8e1ca6421f9c4b67f94b5d72b-81f45104c50f3fdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T15:49:00Z" - latency: 4.719873ms message: 'load-balancer-api-external: tcp connection to af4be2b8e1ca6421f9c4b67f94b5d72b-81f45104c50f3fdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:48:00Z" - latency: 6.631086ms message: 'load-balancer-api-external: resolved host name af4be2b8e1ca6421f9c4b67f94b5d72b-81f45104c50f3fdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T15:48:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T15:09:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-168-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-168.ec2.internal uid: 347fabb5-d399-4a3b-a5f0-c8cbc750baa9 resourceVersion: "25956" uid: dce25df7-df77-4862-ba46-a7cd2e4111fe spec: sourcePod: network-check-source-8894fc9bd-nmq7h targetEndpoint: af4be2b8e1ca6421f9c4b67f94b5d72b-81f45104c50f3fdf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T15:16:00Z" message: 'load-balancer-api-internal: tcp connection to af4be2b8e1ca6421f9c4b67f94b5d72b-81f45104c50f3fdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.592577ms message: 'load-balancer-api-internal: tcp connection to af4be2b8e1ca6421f9c4b67f94b5d72b-81f45104c50f3fdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:52:00Z" - latency: 8.884092ms message: 'load-balancer-api-internal: resolved host name af4be2b8e1ca6421f9c4b67f94b5d72b-81f45104c50f3fdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T15:52:00Z" - latency: 5.508488ms message: 'load-balancer-api-internal: tcp connection to af4be2b8e1ca6421f9c4b67f94b5d72b-81f45104c50f3fdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:51:00Z" - latency: 9.636181ms message: 'load-balancer-api-internal: resolved host name af4be2b8e1ca6421f9c4b67f94b5d72b-81f45104c50f3fdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T15:51:00Z" - latency: 5.330665ms message: 'load-balancer-api-internal: tcp connection to af4be2b8e1ca6421f9c4b67f94b5d72b-81f45104c50f3fdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:50:00Z" - latency: 8.784619ms message: 'load-balancer-api-internal: resolved host name af4be2b8e1ca6421f9c4b67f94b5d72b-81f45104c50f3fdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T15:50:00Z" - latency: 3.765679ms message: 'load-balancer-api-internal: tcp connection to af4be2b8e1ca6421f9c4b67f94b5d72b-81f45104c50f3fdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:49:00Z" - latency: 7.689957ms message: 'load-balancer-api-internal: resolved host name af4be2b8e1ca6421f9c4b67f94b5d72b-81f45104c50f3fdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T15:49:00Z" - latency: 4.512716ms message: 'load-balancer-api-internal: tcp connection to af4be2b8e1ca6421f9c4b67f94b5d72b-81f45104c50f3fdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:48:00Z" - latency: 6.844822ms message: 'load-balancer-api-internal: resolved host name af4be2b8e1ca6421f9c4b67f94b5d72b-81f45104c50f3fdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T15:48:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T15:09:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-168-to-network-check-target-ip-10-0-131-168 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-168.ec2.internal uid: 347fabb5-d399-4a3b-a5f0-c8cbc750baa9 resourceVersion: "25950" uid: 5dcfae49-e440-4202-b66d-8401d9ac9e0c spec: sourcePod: network-check-source-8894fc9bd-nmq7h targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-22T15:17:00Z" message: 'network-check-target-ip-10-0-131-168: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 774.47µs message: 'network-check-target-ip-10-0-131-168: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:52:00Z" - latency: 894.084µs message: 'network-check-target-ip-10-0-131-168: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:51:00Z" - latency: 1.098545ms message: 'network-check-target-ip-10-0-131-168: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:50:00Z" - latency: 821.701µs message: 'network-check-target-ip-10-0-131-168: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:49:00Z" - latency: 1.174744ms message: 'network-check-target-ip-10-0-131-168: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:48:00Z" - latency: 2.060255ms message: 'network-check-target-ip-10-0-131-168: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:47:00Z" - latency: 956.531µs message: 'network-check-target-ip-10-0-131-168: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:46:00Z" - latency: 841.047µs message: 'network-check-target-ip-10-0-131-168: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:45:00Z" - latency: 753.799µs message: 'network-check-target-ip-10-0-131-168: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:44:00Z" - latency: 767.836µs message: 'network-check-target-ip-10-0-131-168: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:43:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T15:09:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-168-to-network-check-target-ip-10-0-141-188 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-168.ec2.internal uid: 347fabb5-d399-4a3b-a5f0-c8cbc750baa9 resourceVersion: "25952" uid: ed53364a-6057-4de9-a26a-017802a6d8d5 spec: sourcePod: network-check-source-8894fc9bd-nmq7h targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T15:17:00Z" message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.111172ms message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:52:00Z" - latency: 2.022118ms message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:51:00Z" - latency: 2.075291ms message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:50:00Z" - latency: 2.045972ms message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:49:00Z" - latency: 2.230644ms message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:48:00Z" - latency: 2.269018ms message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:47:00Z" - latency: 1.823907ms message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:46:00Z" - latency: 1.890431ms message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:45:00Z" - latency: 1.987735ms message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:44:00Z" - latency: 1.939377ms message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:43:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T15:09:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-168-to-network-check-target-ip-10-0-141-246 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-168.ec2.internal uid: 347fabb5-d399-4a3b-a5f0-c8cbc750baa9 resourceVersion: "25951" uid: 945541c8-29f8-4925-a7a5-7771aafd1d26 spec: sourcePod: network-check-source-8894fc9bd-nmq7h targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T15:17:00Z" message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.185688ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:52:00Z" - latency: 2.227419ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:51:00Z" - latency: 2.055882ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:50:00Z" - latency: 1.996064ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:49:00Z" - latency: 1.934421ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:48:00Z" - latency: 2.652409ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:47:00Z" - latency: 2.085445ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:46:00Z" - latency: 1.960919ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:45:00Z" - latency: 2.242193ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:44:00Z" - latency: 1.885837ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:43:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T15:09:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-168-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-168.ec2.internal uid: 347fabb5-d399-4a3b-a5f0-c8cbc750baa9 resourceVersion: "25953" uid: 06e02409-8af8-4897-b1a8-f258732b7620 spec: sourcePod: network-check-source-8894fc9bd-nmq7h targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-22T15:16:00Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.012464ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:52:00Z" - latency: 2.123816ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T15:52:00Z" - latency: 1.342179ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:51:00Z" - latency: 2.505786ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T15:51:00Z" - latency: 931.102µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:50:00Z" - latency: 1.588619ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T15:50:00Z" - latency: 720.704µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:49:00Z" - latency: 1.626518ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T15:49:00Z" - latency: 962.861µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T15:48:00Z" - latency: 1.462609ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T15:48:00Z" kind: List metadata: resourceVersion: ""