apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:39:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-88-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-88.us-west-2.compute.internal uid: 301e4bfa-c8a1-4df3-898f-464a4cc3e70b resourceVersion: "64433" uid: 85da75f0-5e94-40c5-aa17-d3d39f7ad410 spec: sourcePod: network-check-source-6f78d59f99-wf52v targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T18:46:53Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 923.582µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:42:53Z" - latency: 1.599833ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:41:53Z" - latency: 1.076023ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:40:53Z" - latency: 1.260561ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:39:53Z" - latency: 1.093326ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:38:53Z" - latency: 1.19739ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:37:53Z" - latency: 1.335324ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:36:53Z" - latency: 1.206602ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:35:53Z" - latency: 1.13669ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:34:53Z" - latency: 1.413835ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:33:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:39:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-88-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-88.us-west-2.compute.internal uid: 301e4bfa-c8a1-4df3-898f-464a4cc3e70b resourceVersion: "66903" uid: d53656e5-aa87-4687-bead-a49bbb996870 spec: sourcePod: network-check-source-6f78d59f99-wf52v targetEndpoint: a000931687ba14c969afc60d3cadd041-7b43774db3a78fc8.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T18:45:53Z" message: 'load-balancer-api-external: tcp connection to a000931687ba14c969afc60d3cadd041-7b43774db3a78fc8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.84895ms message: 'load-balancer-api-external: tcp connection to a000931687ba14c969afc60d3cadd041-7b43774db3a78fc8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:45:53Z" - latency: 8.904276ms message: 'load-balancer-api-external: resolved host name a000931687ba14c969afc60d3cadd041-7b43774db3a78fc8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:45:53Z" - latency: 52.999228ms message: 'load-balancer-api-external: tcp connection to a000931687ba14c969afc60d3cadd041-7b43774db3a78fc8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:44:53Z" - latency: 6.420811ms message: 'load-balancer-api-external: resolved host name a000931687ba14c969afc60d3cadd041-7b43774db3a78fc8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:44:53Z" - latency: 55.168358ms message: 'load-balancer-api-external: tcp connection to a000931687ba14c969afc60d3cadd041-7b43774db3a78fc8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:43:53Z" - latency: 6.244262ms message: 'load-balancer-api-external: resolved host name a000931687ba14c969afc60d3cadd041-7b43774db3a78fc8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:43:53Z" - latency: 55.157014ms message: 'load-balancer-api-external: tcp connection to a000931687ba14c969afc60d3cadd041-7b43774db3a78fc8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:42:53Z" - latency: 10.200799ms message: 'load-balancer-api-external: resolved host name a000931687ba14c969afc60d3cadd041-7b43774db3a78fc8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:42:53Z" - latency: 57.251938ms message: 'load-balancer-api-external: tcp connection to a000931687ba14c969afc60d3cadd041-7b43774db3a78fc8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:41:53Z" - latency: 9.956417ms message: 'load-balancer-api-external: resolved host name a000931687ba14c969afc60d3cadd041-7b43774db3a78fc8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:41:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:39:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-88-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-88.us-west-2.compute.internal uid: 301e4bfa-c8a1-4df3-898f-464a4cc3e70b resourceVersion: "66902" uid: ea48e7b1-5018-4452-a963-5a0ee64a7f95 spec: sourcePod: network-check-source-6f78d59f99-wf52v targetEndpoint: a000931687ba14c969afc60d3cadd041-7b43774db3a78fc8.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T18:45:53Z" message: 'load-balancer-api-internal: tcp connection to a000931687ba14c969afc60d3cadd041-7b43774db3a78fc8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.864349ms message: 'load-balancer-api-internal: tcp connection to a000931687ba14c969afc60d3cadd041-7b43774db3a78fc8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:45:53Z" - latency: 8.893029ms message: 'load-balancer-api-internal: resolved host name a000931687ba14c969afc60d3cadd041-7b43774db3a78fc8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:45:53Z" - latency: 54.904192ms message: 'load-balancer-api-internal: tcp connection to a000931687ba14c969afc60d3cadd041-7b43774db3a78fc8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:44:53Z" - latency: 6.455232ms message: 'load-balancer-api-internal: resolved host name a000931687ba14c969afc60d3cadd041-7b43774db3a78fc8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:44:53Z" - latency: 51.086618ms message: 'load-balancer-api-internal: tcp connection to a000931687ba14c969afc60d3cadd041-7b43774db3a78fc8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:43:53Z" - latency: 6.276337ms message: 'load-balancer-api-internal: resolved host name a000931687ba14c969afc60d3cadd041-7b43774db3a78fc8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:43:53Z" - latency: 55.167422ms message: 'load-balancer-api-internal: tcp connection to a000931687ba14c969afc60d3cadd041-7b43774db3a78fc8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:42:53Z" - latency: 10.257732ms message: 'load-balancer-api-internal: resolved host name a000931687ba14c969afc60d3cadd041-7b43774db3a78fc8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:42:53Z" - latency: 57.293365ms message: 'load-balancer-api-internal: tcp connection to a000931687ba14c969afc60d3cadd041-7b43774db3a78fc8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:41:53Z" - latency: 9.738304ms message: 'load-balancer-api-internal: resolved host name a000931687ba14c969afc60d3cadd041-7b43774db3a78fc8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:41:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:39:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-88-to-network-check-target-ip-10-0-128-38 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-88.us-west-2.compute.internal uid: 301e4bfa-c8a1-4df3-898f-464a4cc3e70b resourceVersion: "64430" uid: 97428374-f3da-4499-a977-33e7d27a52ab spec: sourcePod: network-check-source-6f78d59f99-wf52v targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:46:53Z" message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.079722ms message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:42:53Z" - latency: 3.249745ms message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:41:53Z" - latency: 2.173874ms message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:40:53Z" - latency: 1.90848ms message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:39:53Z" - latency: 1.971072ms message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:38:53Z" - latency: 2.213996ms message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:37:53Z" - latency: 1.864402ms message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:36:53Z" - latency: 1.959413ms message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:35:53Z" - latency: 1.792326ms message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:34:53Z" - latency: 1.640441ms message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:33:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:39:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-88-to-network-check-target-ip-10-0-129-31 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-88.us-west-2.compute.internal uid: 301e4bfa-c8a1-4df3-898f-464a4cc3e70b resourceVersion: "64432" uid: cb39ed14-f4c1-4d8f-be82-1e64c289bdd1 spec: sourcePod: network-check-source-6f78d59f99-wf52v targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:46:53Z" message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.244725ms message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:42:53Z" - latency: 3.229997ms message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:41:53Z" - latency: 2.208682ms message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:40:53Z" - latency: 2.386689ms message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:39:53Z" - latency: 2.44442ms message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:38:53Z" - latency: 2.314935ms message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:37:53Z" - latency: 3.464534ms message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:36:53Z" - latency: 2.530882ms message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:35:53Z" - latency: 2.379735ms message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:34:53Z" - latency: 1.869619ms message: 'network-check-target-ip-10-0-129-31: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:33:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:39:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-88-to-network-check-target-ip-10-0-129-88 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-88.us-west-2.compute.internal uid: 301e4bfa-c8a1-4df3-898f-464a4cc3e70b resourceVersion: "64429" uid: d7c6a156-18c8-495b-90d3-a35a8d3f0f39 spec: sourcePod: network-check-source-6f78d59f99-wf52v targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:46:53Z" message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.181622ms message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:42:53Z" - latency: 2.358155ms message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:41:53Z" - latency: 1.605872ms message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:40:53Z" - latency: 907.156µs message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:39:53Z" - latency: 1.23233ms message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:38:53Z" - latency: 1.436021ms message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:37:53Z" - latency: 908.784µs message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:36:53Z" - latency: 883.37µs message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:35:53Z" - latency: 1.447504ms message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:34:53Z" - latency: 788.518µs message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:33:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:39:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-88-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-88.us-west-2.compute.internal uid: 301e4bfa-c8a1-4df3-898f-464a4cc3e70b resourceVersion: "66901" uid: 6fae0dc4-2d7e-4629-a2dd-5935d838e4f1 spec: sourcePod: network-check-source-6f78d59f99-wf52v targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T18:45:53Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 976.361µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:45:53Z" - latency: 539.355µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:45:53Z" - latency: 706.852µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:44:53Z" - latency: 506.886µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:44:53Z" - latency: 631.384µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:43:53Z" - latency: 577.659µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:43:53Z" - latency: 705.924µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:42:53Z" - latency: 551.144µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:42:53Z" - latency: 921.474µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:41:53Z" - latency: 530.255µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:41:53Z" kind: List metadata: resourceVersion: ""