apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:37:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-10-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-10.ec2.internal uid: 10960fae-7812-4d97-a64a-a5d9b167462e resourceVersion: "21197" uid: e25b4377-224b-4b8b-9f8a-11d54252a106 spec: sourcePod: network-check-source-989f8b8dc-js7f9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-08T16:44:46Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.261367ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:58:46Z" - latency: 981.443µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:57:46Z" - latency: 1.521518ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:56:46Z" - latency: 1.334785ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:55:46Z" - latency: 808.266µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:54:46Z" - latency: 1.039799ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:53:46Z" - latency: 1.201365ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:52:46Z" - latency: 963.375µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:51:46Z" - latency: 974.076µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:50:46Z" - latency: 1.226577ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:49:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:37:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-10-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-10.ec2.internal uid: 10960fae-7812-4d97-a64a-a5d9b167462e resourceVersion: "19857" uid: 9ccddd38-03de-4417-a0b1-7a8233d41816 spec: sourcePod: network-check-source-989f8b8dc-js7f9 targetEndpoint: a4b7eb16ec3d549b1b44a41c6c342587-0c889bc07a408762.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T16:43:46Z" message: 'load-balancer-api-external: tcp connection to a4b7eb16ec3d549b1b44a41c6c342587-0c889bc07a408762.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.17318ms message: 'load-balancer-api-external: tcp connection to a4b7eb16ec3d549b1b44a41c6c342587-0c889bc07a408762.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:55:46Z" - latency: 8.970839ms message: 'load-balancer-api-external: resolved host name a4b7eb16ec3d549b1b44a41c6c342587-0c889bc07a408762.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:55:46Z" - latency: 6.873799ms message: 'load-balancer-api-external: tcp connection to a4b7eb16ec3d549b1b44a41c6c342587-0c889bc07a408762.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:54:46Z" - latency: 6.685089ms message: 'load-balancer-api-external: resolved host name a4b7eb16ec3d549b1b44a41c6c342587-0c889bc07a408762.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:54:46Z" - latency: 5.761339ms message: 'load-balancer-api-external: tcp connection to a4b7eb16ec3d549b1b44a41c6c342587-0c889bc07a408762.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:53:46Z" - latency: 6.928583ms message: 'load-balancer-api-external: resolved host name a4b7eb16ec3d549b1b44a41c6c342587-0c889bc07a408762.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:53:46Z" - latency: 5.027968ms message: 'load-balancer-api-external: tcp connection to a4b7eb16ec3d549b1b44a41c6c342587-0c889bc07a408762.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:52:46Z" - latency: 6.65693ms message: 'load-balancer-api-external: resolved host name a4b7eb16ec3d549b1b44a41c6c342587-0c889bc07a408762.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:52:46Z" - latency: 4.103179ms message: 'load-balancer-api-external: tcp connection to a4b7eb16ec3d549b1b44a41c6c342587-0c889bc07a408762.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:51:46Z" - latency: 7.017927ms message: 'load-balancer-api-external: resolved host name a4b7eb16ec3d549b1b44a41c6c342587-0c889bc07a408762.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:51:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:37:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-10-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-10.ec2.internal uid: 10960fae-7812-4d97-a64a-a5d9b167462e resourceVersion: "19858" uid: e4d0db51-a6be-4d59-b5d5-4473306376bf spec: sourcePod: network-check-source-989f8b8dc-js7f9 targetEndpoint: a4b7eb16ec3d549b1b44a41c6c342587-0c889bc07a408762.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T16:43:46Z" message: 'load-balancer-api-internal: tcp connection to a4b7eb16ec3d549b1b44a41c6c342587-0c889bc07a408762.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.586284ms message: 'load-balancer-api-internal: tcp connection to a4b7eb16ec3d549b1b44a41c6c342587-0c889bc07a408762.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:55:46Z" - latency: 8.93345ms message: 'load-balancer-api-internal: resolved host name a4b7eb16ec3d549b1b44a41c6c342587-0c889bc07a408762.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:55:46Z" - latency: 6.823251ms message: 'load-balancer-api-internal: tcp connection to a4b7eb16ec3d549b1b44a41c6c342587-0c889bc07a408762.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:54:46Z" - latency: 6.811414ms message: 'load-balancer-api-internal: resolved host name a4b7eb16ec3d549b1b44a41c6c342587-0c889bc07a408762.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:54:46Z" - latency: 6.620615ms message: 'load-balancer-api-internal: tcp connection to a4b7eb16ec3d549b1b44a41c6c342587-0c889bc07a408762.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:53:46Z" - latency: 7.012369ms message: 'load-balancer-api-internal: resolved host name a4b7eb16ec3d549b1b44a41c6c342587-0c889bc07a408762.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:53:46Z" - latency: 4.989935ms message: 'load-balancer-api-internal: tcp connection to a4b7eb16ec3d549b1b44a41c6c342587-0c889bc07a408762.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:52:46Z" - latency: 6.7146ms message: 'load-balancer-api-internal: resolved host name a4b7eb16ec3d549b1b44a41c6c342587-0c889bc07a408762.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:52:46Z" - latency: 4.074431ms message: 'load-balancer-api-internal: tcp connection to a4b7eb16ec3d549b1b44a41c6c342587-0c889bc07a408762.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:51:46Z" - latency: 7.08292ms message: 'load-balancer-api-internal: resolved host name a4b7eb16ec3d549b1b44a41c6c342587-0c889bc07a408762.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:51:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:37:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-10-to-network-check-target-ip-10-0-132-10 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-10.ec2.internal uid: 10960fae-7812-4d97-a64a-a5d9b167462e resourceVersion: "21194" uid: 1664e727-44ab-4942-8d9a-8b4543eff479 spec: sourcePod: network-check-source-989f8b8dc-js7f9 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T16:44:46Z" message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 898.35µs message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:58:46Z" - latency: 995.451µs message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:57:46Z" - latency: 895.737µs message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:56:46Z" - latency: 1.541278ms message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:55:46Z" - latency: 956.936µs message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:54:46Z" - latency: 885.232µs message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:53:46Z" - latency: 824.314µs message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:52:46Z" - latency: 808.855µs message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:51:46Z" - latency: 926.434µs message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:50:46Z" - latency: 904.924µs message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:49:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:37:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-10-to-network-check-target-ip-10-0-139-237 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-10.ec2.internal uid: 10960fae-7812-4d97-a64a-a5d9b167462e resourceVersion: "21195" uid: 26a58cd6-f8bf-4f63-bdd1-0625dc93c6bd spec: sourcePod: network-check-source-989f8b8dc-js7f9 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T16:44:46Z" message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.142796ms message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:58:46Z" - latency: 2.097778ms message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:57:46Z" - latency: 2.30198ms message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:56:46Z" - latency: 2.195327ms message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:55:46Z" - latency: 2.161711ms message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:54:46Z" - latency: 2.116869ms message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:53:46Z" - latency: 2.043818ms message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:52:46Z" - latency: 2.371926ms message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:51:46Z" - latency: 2.258277ms message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:50:46Z" - latency: 2.289721ms message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:49:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:37:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-10-to-network-check-target-ip-10-0-141-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-10.ec2.internal uid: 10960fae-7812-4d97-a64a-a5d9b167462e resourceVersion: "21196" uid: 0ab5cd7c-bc9f-441a-8af8-e4e3cc35efb2 spec: sourcePod: network-check-source-989f8b8dc-js7f9 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T16:44:46Z" message: 'network-check-target-ip-10-0-141-103: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.96381ms message: 'network-check-target-ip-10-0-141-103: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:58:46Z" - latency: 2.26654ms message: 'network-check-target-ip-10-0-141-103: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:57:46Z" - latency: 2.230663ms message: 'network-check-target-ip-10-0-141-103: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:56:46Z" - latency: 2.410796ms message: 'network-check-target-ip-10-0-141-103: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:55:46Z" - latency: 2.08827ms message: 'network-check-target-ip-10-0-141-103: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:54:46Z" - latency: 2.411896ms message: 'network-check-target-ip-10-0-141-103: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:53:46Z" - latency: 2.098323ms message: 'network-check-target-ip-10-0-141-103: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:52:46Z" - latency: 2.102997ms message: 'network-check-target-ip-10-0-141-103: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:51:46Z" - latency: 2.188315ms message: 'network-check-target-ip-10-0-141-103: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:50:46Z" - latency: 2.458348ms message: 'network-check-target-ip-10-0-141-103: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:49:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:37:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-10-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-10.ec2.internal uid: 10960fae-7812-4d97-a64a-a5d9b167462e resourceVersion: "19856" uid: 9b639eb7-64ec-4266-9c79-832fb61d0a8f spec: sourcePod: network-check-source-989f8b8dc-js7f9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-08T16:43:46Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.099101ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:55:46Z" - latency: 1.894144ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T16:55:46Z" - latency: 880.727µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:54:46Z" - latency: 1.612873ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T16:54:46Z" - latency: 784.616µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:53:46Z" - latency: 1.76336ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T16:53:46Z" - latency: 869.884µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:52:46Z" - latency: 1.704875ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T16:52:46Z" - latency: 936.299µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:51:46Z" - latency: 1.987034ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T16:51:46Z" kind: List metadata: resourceVersion: ""