apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T03:31:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-19-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-19.us-west-2.compute.internal uid: c7ec8608-0ac9-4d0d-80f4-be6b09ac1792 resourceVersion: "102596" uid: b36f8775-ce65-45ac-8793-9e3aa7004f51 spec: sourcePod: network-check-source-6f78d59f99-5jgbv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-31T03:38:56Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.167016ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:41:56Z" - latency: 1.223275ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:40:56Z" - latency: 1.586416ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:39:56Z" - latency: 996.877µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:38:56Z" - latency: 1.388832ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:37:56Z" - latency: 1.280119ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:36:56Z" - latency: 947.733µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:35:56Z" - latency: 1.230321ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:34:56Z" - latency: 785.924µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:33:56Z" - latency: 1.255561ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:32:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T03:31:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-19-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-19.us-west-2.compute.internal uid: c7ec8608-0ac9-4d0d-80f4-be6b09ac1792 resourceVersion: "100515" uid: f2ccce71-798b-491e-9f62-a1a1a6db6e3f spec: sourcePod: network-check-source-6f78d59f99-5jgbv targetEndpoint: aad67609fd0bc481f905aa31524c4d83-10f2963fa6f7f4fa.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T03:37:56Z" message: 'load-balancer-api-external: tcp connection to aad67609fd0bc481f905aa31524c4d83-10f2963fa6f7f4fa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 56.505971ms message: 'load-balancer-api-external: tcp connection to aad67609fd0bc481f905aa31524c4d83-10f2963fa6f7f4fa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:37:56Z" - latency: 8.909368ms message: 'load-balancer-api-external: resolved host name aad67609fd0bc481f905aa31524c4d83-10f2963fa6f7f4fa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:37:56Z" - latency: 55.967898ms message: 'load-balancer-api-external: tcp connection to aad67609fd0bc481f905aa31524c4d83-10f2963fa6f7f4fa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:36:56Z" - latency: 7.354498ms message: 'load-balancer-api-external: resolved host name aad67609fd0bc481f905aa31524c4d83-10f2963fa6f7f4fa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:36:56Z" - latency: 55.630031ms message: 'load-balancer-api-external: tcp connection to aad67609fd0bc481f905aa31524c4d83-10f2963fa6f7f4fa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:35:56Z" - latency: 7.1391ms message: 'load-balancer-api-external: resolved host name aad67609fd0bc481f905aa31524c4d83-10f2963fa6f7f4fa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:35:56Z" - latency: 55.704837ms message: 'load-balancer-api-external: tcp connection to aad67609fd0bc481f905aa31524c4d83-10f2963fa6f7f4fa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:34:56Z" - latency: 7.726181ms message: 'load-balancer-api-external: resolved host name aad67609fd0bc481f905aa31524c4d83-10f2963fa6f7f4fa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:34:56Z" - latency: 51.206807ms message: 'load-balancer-api-external: tcp connection to aad67609fd0bc481f905aa31524c4d83-10f2963fa6f7f4fa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:33:56Z" - latency: 6.496317ms message: 'load-balancer-api-external: resolved host name aad67609fd0bc481f905aa31524c4d83-10f2963fa6f7f4fa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:33:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T03:31:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-19-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-19.us-west-2.compute.internal uid: c7ec8608-0ac9-4d0d-80f4-be6b09ac1792 resourceVersion: "100514" uid: f6b1d0ca-e585-4006-bed0-0a557ff4b46e spec: sourcePod: network-check-source-6f78d59f99-5jgbv targetEndpoint: aad67609fd0bc481f905aa31524c4d83-10f2963fa6f7f4fa.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T03:37:56Z" message: 'load-balancer-api-internal: tcp connection to aad67609fd0bc481f905aa31524c4d83-10f2963fa6f7f4fa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 52.322659ms message: 'load-balancer-api-internal: tcp connection to aad67609fd0bc481f905aa31524c4d83-10f2963fa6f7f4fa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:37:56Z" - latency: 8.870373ms message: 'load-balancer-api-internal: resolved host name aad67609fd0bc481f905aa31524c4d83-10f2963fa6f7f4fa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:37:56Z" - latency: 53.428715ms message: 'load-balancer-api-internal: tcp connection to aad67609fd0bc481f905aa31524c4d83-10f2963fa6f7f4fa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:36:56Z" - latency: 7.405831ms message: 'load-balancer-api-internal: resolved host name aad67609fd0bc481f905aa31524c4d83-10f2963fa6f7f4fa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:36:56Z" - latency: 3.38397405s message: 'load-balancer-api-internal: tcp connection to aad67609fd0bc481f905aa31524c4d83-10f2963fa6f7f4fa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:35:56Z" - latency: 7.077353ms message: 'load-balancer-api-internal: resolved host name aad67609fd0bc481f905aa31524c4d83-10f2963fa6f7f4fa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:35:56Z" - latency: 55.760712ms message: 'load-balancer-api-internal: tcp connection to aad67609fd0bc481f905aa31524c4d83-10f2963fa6f7f4fa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:34:56Z" - latency: 7.802506ms message: 'load-balancer-api-internal: resolved host name aad67609fd0bc481f905aa31524c4d83-10f2963fa6f7f4fa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:34:56Z" - latency: 57.081603ms message: 'load-balancer-api-internal: tcp connection to aad67609fd0bc481f905aa31524c4d83-10f2963fa6f7f4fa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:33:56Z" - latency: 6.410764ms message: 'load-balancer-api-internal: resolved host name aad67609fd0bc481f905aa31524c4d83-10f2963fa6f7f4fa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:33:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T03:31:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-19-to-network-check-target-ip-10-0-129-108 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-19.us-west-2.compute.internal uid: c7ec8608-0ac9-4d0d-80f4-be6b09ac1792 resourceVersion: "102592" uid: 08b72248-a989-473b-acbe-821252e91053 spec: sourcePod: network-check-source-6f78d59f99-5jgbv targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-31T03:38:56Z" message: 'network-check-target-ip-10-0-129-108: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.15548ms message: 'network-check-target-ip-10-0-129-108: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:41:56Z" - latency: 2.221994ms message: 'network-check-target-ip-10-0-129-108: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:40:56Z" - latency: 2.33007ms message: 'network-check-target-ip-10-0-129-108: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:39:56Z" - latency: 2.341049ms message: 'network-check-target-ip-10-0-129-108: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:38:56Z" - latency: 2.2325ms message: 'network-check-target-ip-10-0-129-108: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:37:56Z" - latency: 1.932993ms message: 'network-check-target-ip-10-0-129-108: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:36:56Z" - latency: 2.111119ms message: 'network-check-target-ip-10-0-129-108: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:35:56Z" - latency: 2.011108ms message: 'network-check-target-ip-10-0-129-108: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:34:56Z" - latency: 2.067373ms message: 'network-check-target-ip-10-0-129-108: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:33:56Z" - latency: 2.298641ms message: 'network-check-target-ip-10-0-129-108: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:32:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T03:31:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-19-to-network-check-target-ip-10-0-130-19 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-19.us-west-2.compute.internal uid: c7ec8608-0ac9-4d0d-80f4-be6b09ac1792 resourceVersion: "102591" uid: a5152435-a638-4f7e-ba07-ab767a58fb38 spec: sourcePod: network-check-source-6f78d59f99-5jgbv targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-31T03:38:56Z" message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.313249ms message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:41:56Z" - latency: 1.247156ms message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:40:56Z" - latency: 988.496µs message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:39:56Z" - latency: 1.627758ms message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:38:56Z" - latency: 1.537541ms message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:37:56Z" - latency: 1.49778ms message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:36:56Z" - latency: 1.314961ms message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:35:56Z" - latency: 938.155µs message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:34:56Z" - latency: 970.873µs message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:33:56Z" - latency: 1.528256ms message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:32:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T03:31:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-19-to-network-check-target-ip-10-0-134-106 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-19.us-west-2.compute.internal uid: c7ec8608-0ac9-4d0d-80f4-be6b09ac1792 resourceVersion: "102594" uid: 057a4537-6f22-4262-9d0f-797b6555bd23 spec: sourcePod: network-check-source-6f78d59f99-5jgbv targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-31T03:38:56Z" message: 'network-check-target-ip-10-0-134-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.669712ms message: 'network-check-target-ip-10-0-134-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:41:56Z" - latency: 2.668722ms message: 'network-check-target-ip-10-0-134-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:40:56Z" - latency: 2.552642ms message: 'network-check-target-ip-10-0-134-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:39:56Z" - latency: 2.679235ms message: 'network-check-target-ip-10-0-134-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:38:56Z" - latency: 2.421443ms message: 'network-check-target-ip-10-0-134-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:37:56Z" - latency: 2.583081ms message: 'network-check-target-ip-10-0-134-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:36:56Z" - latency: 2.507898ms message: 'network-check-target-ip-10-0-134-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:35:56Z" - latency: 2.418082ms message: 'network-check-target-ip-10-0-134-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:34:56Z" - latency: 2.417788ms message: 'network-check-target-ip-10-0-134-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:33:56Z" - latency: 2.346015ms message: 'network-check-target-ip-10-0-134-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:32:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T03:31:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-19-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-19.us-west-2.compute.internal uid: c7ec8608-0ac9-4d0d-80f4-be6b09ac1792 resourceVersion: "100511" uid: c6750437-9bf5-428d-b003-d6085c3edea4 spec: sourcePod: network-check-source-6f78d59f99-5jgbv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-31T03:37:56Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.002458ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:37:56Z" - latency: 1.741082ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T04:37:56Z" - latency: 1.188271ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:36:56Z" - latency: 1.831396ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T04:36:56Z" - latency: 985.205µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:35:56Z" - latency: 1.936318ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T04:35:56Z" - latency: 858.898µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:34:56Z" - latency: 1.716642ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T04:34:56Z" - latency: 815.36µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:33:56Z" - latency: 1.639649ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T04:33:56Z" kind: List metadata: resourceVersion: ""