apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:39:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-102-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-102.ec2.internal uid: c18813de-3fa7-4d36-9b55-04e88fe7d746 resourceVersion: "31988" uid: a78f1065-7bba-41dd-b459-1ffc59672b63 spec: sourcePod: network-check-source-8894fc9bd-vrnns targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-23T16:46:39Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 931.574µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:21:39Z" - latency: 910.546µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:20:39Z" - latency: 822.638µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:19:39Z" - latency: 950.156µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:18:39Z" - latency: 946.422µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:17:39Z" - latency: 1.152641ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:16:39Z" - latency: 1.089568ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:15:39Z" - latency: 1.213456ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:14:39Z" - latency: 1.238663ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:13:39Z" - latency: 1.34838ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:12:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:39:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-102-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-102.ec2.internal uid: c18813de-3fa7-4d36-9b55-04e88fe7d746 resourceVersion: "31989" uid: 56c34d88-5cac-40e4-a70d-a4f600d0b063 spec: sourcePod: network-check-source-8894fc9bd-vrnns targetEndpoint: ad38285ad31fd412db4d4de2a15b9f5f-19f1c6c1737be57a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-23T16:45:39Z" message: 'load-balancer-api-external: tcp connection to ad38285ad31fd412db4d4de2a15b9f5f-19f1c6c1737be57a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.05578ms message: 'load-balancer-api-external: tcp connection to ad38285ad31fd412db4d4de2a15b9f5f-19f1c6c1737be57a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:21:39Z" - latency: 7.065276ms message: 'load-balancer-api-external: resolved host name ad38285ad31fd412db4d4de2a15b9f5f-19f1c6c1737be57a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:21:39Z" - latency: 4.757624ms message: 'load-balancer-api-external: tcp connection to ad38285ad31fd412db4d4de2a15b9f5f-19f1c6c1737be57a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:20:39Z" - latency: 7.698408ms message: 'load-balancer-api-external: resolved host name ad38285ad31fd412db4d4de2a15b9f5f-19f1c6c1737be57a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:20:39Z" - latency: 5.429793ms message: 'load-balancer-api-external: tcp connection to ad38285ad31fd412db4d4de2a15b9f5f-19f1c6c1737be57a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:19:39Z" - latency: 7.77225ms message: 'load-balancer-api-external: resolved host name ad38285ad31fd412db4d4de2a15b9f5f-19f1c6c1737be57a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:19:39Z" - latency: 4.974803ms message: 'load-balancer-api-external: tcp connection to ad38285ad31fd412db4d4de2a15b9f5f-19f1c6c1737be57a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:18:39Z" - latency: 6.036215ms message: 'load-balancer-api-external: resolved host name ad38285ad31fd412db4d4de2a15b9f5f-19f1c6c1737be57a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:18:39Z" - latency: 4.631453ms message: 'load-balancer-api-external: tcp connection to ad38285ad31fd412db4d4de2a15b9f5f-19f1c6c1737be57a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:17:39Z" - latency: 6.700581ms message: 'load-balancer-api-external: resolved host name ad38285ad31fd412db4d4de2a15b9f5f-19f1c6c1737be57a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:17:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:39:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-102-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-102.ec2.internal uid: c18813de-3fa7-4d36-9b55-04e88fe7d746 resourceVersion: "31990" uid: dfc51959-2703-45a8-bbdc-dac9a92a93b2 spec: sourcePod: network-check-source-8894fc9bd-vrnns targetEndpoint: ad38285ad31fd412db4d4de2a15b9f5f-19f1c6c1737be57a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-23T16:45:39Z" message: 'load-balancer-api-internal: tcp connection to ad38285ad31fd412db4d4de2a15b9f5f-19f1c6c1737be57a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.151731ms message: 'load-balancer-api-internal: tcp connection to ad38285ad31fd412db4d4de2a15b9f5f-19f1c6c1737be57a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:21:39Z" - latency: 7.035219ms message: 'load-balancer-api-internal: resolved host name ad38285ad31fd412db4d4de2a15b9f5f-19f1c6c1737be57a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:21:39Z" - latency: 4.891134ms message: 'load-balancer-api-internal: tcp connection to ad38285ad31fd412db4d4de2a15b9f5f-19f1c6c1737be57a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:20:39Z" - latency: 7.605828ms message: 'load-balancer-api-internal: resolved host name ad38285ad31fd412db4d4de2a15b9f5f-19f1c6c1737be57a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:20:39Z" - latency: 5.414954ms message: 'load-balancer-api-internal: tcp connection to ad38285ad31fd412db4d4de2a15b9f5f-19f1c6c1737be57a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:19:39Z" - latency: 7.717672ms message: 'load-balancer-api-internal: resolved host name ad38285ad31fd412db4d4de2a15b9f5f-19f1c6c1737be57a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:19:39Z" - latency: 4.990679ms message: 'load-balancer-api-internal: tcp connection to ad38285ad31fd412db4d4de2a15b9f5f-19f1c6c1737be57a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:18:39Z" - latency: 5.947535ms message: 'load-balancer-api-internal: resolved host name ad38285ad31fd412db4d4de2a15b9f5f-19f1c6c1737be57a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:18:39Z" - latency: 4.595626ms message: 'load-balancer-api-internal: tcp connection to ad38285ad31fd412db4d4de2a15b9f5f-19f1c6c1737be57a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:17:39Z" - latency: 6.734443ms message: 'load-balancer-api-internal: resolved host name ad38285ad31fd412db4d4de2a15b9f5f-19f1c6c1737be57a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:17:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:39:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-102-to-network-check-target-ip-10-0-128-102 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-102.ec2.internal uid: c18813de-3fa7-4d36-9b55-04e88fe7d746 resourceVersion: "31985" uid: c0f21025-d3af-417d-843b-cb2c09374dd4 spec: sourcePod: network-check-source-8894fc9bd-vrnns targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-23T16:46:39Z" message: 'network-check-target-ip-10-0-128-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.246973ms message: 'network-check-target-ip-10-0-128-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:21:39Z" - latency: 2.007083ms message: 'network-check-target-ip-10-0-128-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:20:39Z" - latency: 2.310416ms message: 'network-check-target-ip-10-0-128-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:19:39Z" - latency: 2.105058ms message: 'network-check-target-ip-10-0-128-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:18:39Z" - latency: 2.144956ms message: 'network-check-target-ip-10-0-128-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:17:39Z" - latency: 2.231923ms message: 'network-check-target-ip-10-0-128-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:16:39Z" - latency: 2.258885ms message: 'network-check-target-ip-10-0-128-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:15:39Z" - latency: 2.198893ms message: 'network-check-target-ip-10-0-128-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:14:39Z" - latency: 2.249595ms message: 'network-check-target-ip-10-0-128-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:13:39Z" - latency: 2.032841ms message: 'network-check-target-ip-10-0-128-102: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:12:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:39:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-102-to-network-check-target-ip-10-0-129-102 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-102.ec2.internal uid: c18813de-3fa7-4d36-9b55-04e88fe7d746 resourceVersion: "31984" uid: 273d98fd-1b9b-4ef6-bbeb-9e16fb4cfb3b spec: sourcePod: network-check-source-8894fc9bd-vrnns targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-23T16:46:39Z" message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.132323ms message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:21:39Z" - latency: 837.03µs message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:20:39Z" - latency: 812.864µs message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:19:39Z" - latency: 872.836µs message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:18:39Z" - latency: 893.274µs message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:17:39Z" - latency: 1.011265ms message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:16:39Z" - latency: 1.170738ms message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:15:39Z" - latency: 807.991µs message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:14:39Z" - latency: 868.011µs message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:13:39Z" - latency: 806.539µs message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:12:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:39:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-102-to-network-check-target-ip-10-0-141-189 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-102.ec2.internal uid: c18813de-3fa7-4d36-9b55-04e88fe7d746 resourceVersion: "31983" uid: 8c655d35-c088-444f-a045-34377aae54e7 spec: sourcePod: network-check-source-8894fc9bd-vrnns targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-23T16:46:39Z" message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.036889ms message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:21:39Z" - latency: 2.143968ms message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:20:39Z" - latency: 2.285165ms message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:19:39Z" - latency: 2.092507ms message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:18:39Z" - latency: 2.21569ms message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:17:39Z" - latency: 2.117268ms message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:16:39Z" - latency: 2.174686ms message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:15:39Z" - latency: 2.09675ms message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:14:39Z" - latency: 2.185738ms message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:13:39Z" - latency: 2.170843ms message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:12:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:39:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-102-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-102.ec2.internal uid: c18813de-3fa7-4d36-9b55-04e88fe7d746 resourceVersion: "31986" uid: d32761be-14d1-4ff1-92fc-855f39e80138 spec: sourcePod: network-check-source-8894fc9bd-vrnns targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-23T16:45:39Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.012975ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:21:39Z" - latency: 1.992735ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T17:21:39Z" - latency: 1.003131ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:20:39Z" - latency: 2.163578ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T17:20:39Z" - latency: 754.966µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:19:39Z" - latency: 1.961558ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T17:19:39Z" - latency: 1.131072ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:18:39Z" - latency: 1.771922ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T17:18:39Z" - latency: 739.059µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:17:39Z" - latency: 1.808117ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T17:17:39Z" kind: List metadata: resourceVersion: ""