apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T09:36:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-174-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-174.us-east-2.compute.internal uid: 23d2f141-5f64-4f47-ab33-f915bcef83ad resourceVersion: "133042" uid: f2d96ea0-e86f-4ec8-9cf5-3a2f427f1e69 spec: sourcePod: network-check-source-6f78d59f99-mvxdw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T09:43:53Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.077703ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:39:53Z" - latency: 854.606µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:38:53Z" - latency: 1.261884ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:37:53Z" - latency: 1.072063ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:36:53Z" - latency: 1.329735ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:35:53Z" - latency: 1.13046ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:34:53Z" - latency: 1.092703ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:33:53Z" - latency: 1.089219ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:32:53Z" - latency: 1.744595ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:31:53Z" - latency: 1.091474ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:30:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T09:36:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-174-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-174.us-east-2.compute.internal uid: 23d2f141-5f64-4f47-ab33-f915bcef83ad resourceVersion: "135746" uid: c44485f3-4473-4afb-b464-e4b372e88755 spec: sourcePod: network-check-source-6f78d59f99-mvxdw targetEndpoint: ad4411f792c444373b5fce9a117a6e94-e715514e0e40d6ed.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T09:42:53Z" message: 'load-balancer-api-external: tcp connection to ad4411f792c444373b5fce9a117a6e94-e715514e0e40d6ed.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.934331ms message: 'load-balancer-api-external: tcp connection to ad4411f792c444373b5fce9a117a6e94-e715514e0e40d6ed.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:42:53Z" - latency: 28.162796ms message: 'load-balancer-api-external: resolved host name ad4411f792c444373b5fce9a117a6e94-e715514e0e40d6ed.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T10:42:53Z" - latency: 5.45786ms message: 'load-balancer-api-external: tcp connection to ad4411f792c444373b5fce9a117a6e94-e715514e0e40d6ed.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:41:53Z" - latency: 29.450174ms message: 'load-balancer-api-external: resolved host name ad4411f792c444373b5fce9a117a6e94-e715514e0e40d6ed.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T10:41:53Z" - latency: 5.40449ms message: 'load-balancer-api-external: tcp connection to ad4411f792c444373b5fce9a117a6e94-e715514e0e40d6ed.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:40:53Z" - latency: 10.770525ms message: 'load-balancer-api-external: resolved host name ad4411f792c444373b5fce9a117a6e94-e715514e0e40d6ed.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T10:40:53Z" - latency: 5.276551ms message: 'load-balancer-api-external: tcp connection to ad4411f792c444373b5fce9a117a6e94-e715514e0e40d6ed.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:39:53Z" - latency: 9.318809ms message: 'load-balancer-api-external: resolved host name ad4411f792c444373b5fce9a117a6e94-e715514e0e40d6ed.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T10:39:53Z" - latency: 5.320714ms message: 'load-balancer-api-external: tcp connection to ad4411f792c444373b5fce9a117a6e94-e715514e0e40d6ed.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:38:53Z" - latency: 6.928356ms message: 'load-balancer-api-external: resolved host name ad4411f792c444373b5fce9a117a6e94-e715514e0e40d6ed.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T10:38:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T09:36:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-174-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-174.us-east-2.compute.internal uid: 23d2f141-5f64-4f47-ab33-f915bcef83ad resourceVersion: "135747" uid: b16f92d7-8ce1-4574-9230-1d67f84bc971 spec: sourcePod: network-check-source-6f78d59f99-mvxdw targetEndpoint: ad4411f792c444373b5fce9a117a6e94-e715514e0e40d6ed.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T09:42:53Z" message: 'load-balancer-api-internal: tcp connection to ad4411f792c444373b5fce9a117a6e94-e715514e0e40d6ed.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.250243ms message: 'load-balancer-api-internal: tcp connection to ad4411f792c444373b5fce9a117a6e94-e715514e0e40d6ed.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:42:53Z" - latency: 29.155914ms message: 'load-balancer-api-internal: resolved host name ad4411f792c444373b5fce9a117a6e94-e715514e0e40d6ed.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T10:42:53Z" - latency: 5.206358ms message: 'load-balancer-api-internal: tcp connection to ad4411f792c444373b5fce9a117a6e94-e715514e0e40d6ed.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:41:53Z" - latency: 28.395088ms message: 'load-balancer-api-internal: resolved host name ad4411f792c444373b5fce9a117a6e94-e715514e0e40d6ed.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T10:41:53Z" - latency: 5.497482ms message: 'load-balancer-api-internal: tcp connection to ad4411f792c444373b5fce9a117a6e94-e715514e0e40d6ed.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:40:53Z" - latency: 10.864204ms message: 'load-balancer-api-internal: resolved host name ad4411f792c444373b5fce9a117a6e94-e715514e0e40d6ed.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T10:40:53Z" - latency: 5.098037ms message: 'load-balancer-api-internal: tcp connection to ad4411f792c444373b5fce9a117a6e94-e715514e0e40d6ed.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:39:53Z" - latency: 9.351914ms message: 'load-balancer-api-internal: resolved host name ad4411f792c444373b5fce9a117a6e94-e715514e0e40d6ed.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T10:39:53Z" - latency: 5.34001ms message: 'load-balancer-api-internal: tcp connection to ad4411f792c444373b5fce9a117a6e94-e715514e0e40d6ed.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:38:53Z" - latency: 6.908377ms message: 'load-balancer-api-internal: resolved host name ad4411f792c444373b5fce9a117a6e94-e715514e0e40d6ed.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T10:38:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T09:36:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-174-to-network-check-target-ip-10-0-128-217 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-174.us-east-2.compute.internal uid: 23d2f141-5f64-4f47-ab33-f915bcef83ad resourceVersion: "133040" uid: 999139c0-c878-49b4-b6b4-ab82d088f560 spec: sourcePod: network-check-source-6f78d59f99-mvxdw targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T09:43:53Z" message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.312296ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:39:53Z" - latency: 1.849564ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:38:53Z" - latency: 2.945361ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:37:53Z" - latency: 2.242662ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:36:53Z" - latency: 2.073798ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:35:53Z" - latency: 1.857146ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:34:53Z" - latency: 1.881008ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:33:53Z" - latency: 1.951362ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:32:53Z" - latency: 2.007466ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:31:53Z" - latency: 1.886243ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:30:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T09:36:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-174-to-network-check-target-ip-10-0-134-174 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-174.us-east-2.compute.internal uid: 23d2f141-5f64-4f47-ab33-f915bcef83ad resourceVersion: "133039" uid: 290c721f-29f2-465d-8a7a-03985eb64567 spec: sourcePod: network-check-source-6f78d59f99-mvxdw targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T09:43:53Z" message: 'network-check-target-ip-10-0-134-174: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.495402ms message: 'network-check-target-ip-10-0-134-174: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:39:53Z" - latency: 848.904µs message: 'network-check-target-ip-10-0-134-174: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:38:53Z" - latency: 837.543µs message: 'network-check-target-ip-10-0-134-174: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:37:53Z" - latency: 977.415µs message: 'network-check-target-ip-10-0-134-174: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:36:53Z" - latency: 1.434977ms message: 'network-check-target-ip-10-0-134-174: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:35:53Z" - latency: 938.855µs message: 'network-check-target-ip-10-0-134-174: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:34:53Z" - latency: 762.866µs message: 'network-check-target-ip-10-0-134-174: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:33:53Z" - latency: 848.291µs message: 'network-check-target-ip-10-0-134-174: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:32:53Z" - latency: 1.285799ms message: 'network-check-target-ip-10-0-134-174: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:31:53Z" - latency: 1.087997ms message: 'network-check-target-ip-10-0-134-174: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:30:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T09:36:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-174-to-network-check-target-ip-10-0-138-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-174.us-east-2.compute.internal uid: 23d2f141-5f64-4f47-ab33-f915bcef83ad resourceVersion: "133041" uid: c64812b3-b629-476f-9dd3-9edb6ada9efa spec: sourcePod: network-check-source-6f78d59f99-mvxdw targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T09:43:53Z" message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.286804ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:39:53Z" - latency: 2.074759ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:38:53Z" - latency: 2.714635ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:37:53Z" - latency: 2.099995ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:36:53Z" - latency: 2.182009ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:35:53Z" - latency: 1.796422ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:34:53Z" - latency: 2.13485ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:33:53Z" - latency: 1.632277ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:32:53Z" - latency: 2.021392ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:31:53Z" - latency: 2.060675ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:30:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T09:36:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-174-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-174.us-east-2.compute.internal uid: 23d2f141-5f64-4f47-ab33-f915bcef83ad resourceVersion: "135744" uid: bd21d855-033d-4b14-ba68-9b5f87484723 spec: sourcePod: network-check-source-6f78d59f99-mvxdw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T09:42:53Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.91085ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:42:53Z" - latency: 16.409535ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T10:42:53Z" - latency: 8.135617ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:41:53Z" - latency: 10.385227ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T10:41:53Z" - latency: 982.201µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:40:53Z" - latency: 2.010232ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T10:40:53Z" - latency: 940.711µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:39:53Z" - latency: 2.342943ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T10:39:53Z" - latency: 1.268225ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:38:53Z" - latency: 1.96643ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T10:38:53Z" kind: List metadata: resourceVersion: ""