apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T14:12:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-171-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-171.ec2.internal uid: 9bdf0ef5-24db-4dae-94d5-bed0fb69ff91 resourceVersion: "118846" uid: 673b1e46-a6f3-48bc-a526-15896bded76d spec: sourcePod: network-check-source-6f78d59f99-rjz49 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T14:19:43Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 977.984µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:22:43Z" - latency: 952.014µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:21:43Z" - latency: 1.080152ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:20:43Z" - latency: 1.103531ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:19:43Z" - latency: 1.204855ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:18:43Z" - latency: 1.479006ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:17:43Z" - latency: 1.19555ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:16:43Z" - latency: 1.615136ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:15:43Z" - latency: 1.019597ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:14:43Z" - latency: 1.051222ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:13:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T14:12:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-171-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-171.ec2.internal uid: 9bdf0ef5-24db-4dae-94d5-bed0fb69ff91 resourceVersion: "120487" uid: 56559ff9-2d94-4ba4-8cc7-09a3771b1cf8 spec: sourcePod: network-check-source-6f78d59f99-rjz49 targetEndpoint: ae06cdc7fee814954b7c01d5dbbab6d2-1ff7affd91d7e310.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T14:18:43Z" message: 'load-balancer-api-external: tcp connection to ae06cdc7fee814954b7c01d5dbbab6d2-1ff7affd91d7e310.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 24.006913ms message: 'load-balancer-api-external: tcp connection to ae06cdc7fee814954b7c01d5dbbab6d2-1ff7affd91d7e310.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:24:43Z" - latency: 6.710848ms message: 'load-balancer-api-external: resolved host name ae06cdc7fee814954b7c01d5dbbab6d2-1ff7affd91d7e310.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T15:24:43Z" - latency: 17.94864ms message: 'load-balancer-api-external: tcp connection to ae06cdc7fee814954b7c01d5dbbab6d2-1ff7affd91d7e310.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:23:43Z" - latency: 7.093767ms message: 'load-balancer-api-external: resolved host name ae06cdc7fee814954b7c01d5dbbab6d2-1ff7affd91d7e310.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T15:23:43Z" - latency: 16.560996ms message: 'load-balancer-api-external: tcp connection to ae06cdc7fee814954b7c01d5dbbab6d2-1ff7affd91d7e310.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:22:43Z" - latency: 6.121993ms message: 'load-balancer-api-external: resolved host name ae06cdc7fee814954b7c01d5dbbab6d2-1ff7affd91d7e310.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T15:22:43Z" - latency: 25.868157ms message: 'load-balancer-api-external: tcp connection to ae06cdc7fee814954b7c01d5dbbab6d2-1ff7affd91d7e310.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:21:43Z" - latency: 7.148048ms message: 'load-balancer-api-external: resolved host name ae06cdc7fee814954b7c01d5dbbab6d2-1ff7affd91d7e310.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T15:21:43Z" - latency: 17.7013ms message: 'load-balancer-api-external: tcp connection to ae06cdc7fee814954b7c01d5dbbab6d2-1ff7affd91d7e310.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:20:43Z" - latency: 6.605567ms message: 'load-balancer-api-external: resolved host name ae06cdc7fee814954b7c01d5dbbab6d2-1ff7affd91d7e310.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T15:20:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T14:12:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-171-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-171.ec2.internal uid: 9bdf0ef5-24db-4dae-94d5-bed0fb69ff91 resourceVersion: "120486" uid: 26d07a63-dd02-459d-9009-d94af7859b6a spec: sourcePod: network-check-source-6f78d59f99-rjz49 targetEndpoint: ae06cdc7fee814954b7c01d5dbbab6d2-1ff7affd91d7e310.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T14:18:43Z" message: 'load-balancer-api-internal: tcp connection to ae06cdc7fee814954b7c01d5dbbab6d2-1ff7affd91d7e310.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.066947ms message: 'load-balancer-api-internal: tcp connection to ae06cdc7fee814954b7c01d5dbbab6d2-1ff7affd91d7e310.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:24:43Z" - latency: 6.595073ms message: 'load-balancer-api-internal: resolved host name ae06cdc7fee814954b7c01d5dbbab6d2-1ff7affd91d7e310.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T15:24:43Z" - latency: 18.874091ms message: 'load-balancer-api-internal: tcp connection to ae06cdc7fee814954b7c01d5dbbab6d2-1ff7affd91d7e310.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:23:43Z" - latency: 7.203083ms message: 'load-balancer-api-internal: resolved host name ae06cdc7fee814954b7c01d5dbbab6d2-1ff7affd91d7e310.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T15:23:43Z" - latency: 20.070496ms message: 'load-balancer-api-internal: tcp connection to ae06cdc7fee814954b7c01d5dbbab6d2-1ff7affd91d7e310.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:22:43Z" - latency: 6.157457ms message: 'load-balancer-api-internal: resolved host name ae06cdc7fee814954b7c01d5dbbab6d2-1ff7affd91d7e310.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T15:22:43Z" - latency: 25.852058ms message: 'load-balancer-api-internal: tcp connection to ae06cdc7fee814954b7c01d5dbbab6d2-1ff7affd91d7e310.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:21:43Z" - latency: 7.200896ms message: 'load-balancer-api-internal: resolved host name ae06cdc7fee814954b7c01d5dbbab6d2-1ff7affd91d7e310.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T15:21:43Z" - latency: 17.697704ms message: 'load-balancer-api-internal: tcp connection to ae06cdc7fee814954b7c01d5dbbab6d2-1ff7affd91d7e310.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:20:43Z" - latency: 6.515074ms message: 'load-balancer-api-internal: resolved host name ae06cdc7fee814954b7c01d5dbbab6d2-1ff7affd91d7e310.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T15:20:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T14:12:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-171-to-network-check-target-ip-10-0-128-190 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-171.ec2.internal uid: 9bdf0ef5-24db-4dae-94d5-bed0fb69ff91 resourceVersion: "118843" uid: 896dc2ab-619f-4078-b2de-a18d46975766 spec: sourcePod: network-check-source-6f78d59f99-rjz49 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T14:19:43Z" message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.409044ms message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:22:43Z" - latency: 2.352639ms message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:21:43Z" - latency: 2.109574ms message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:20:43Z" - latency: 2.525128ms message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:19:43Z" - latency: 2.916743ms message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:18:43Z" - latency: 2.607593ms message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:17:43Z" - latency: 2.362018ms message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:16:43Z" - latency: 2.474122ms message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:15:43Z" - latency: 1.858992ms message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:14:43Z" - latency: 2.07648ms message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:13:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T14:12:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-171-to-network-check-target-ip-10-0-130-191 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-171.ec2.internal uid: 9bdf0ef5-24db-4dae-94d5-bed0fb69ff91 resourceVersion: "118845" uid: c6c6371b-12c3-4ca1-9aea-1f265308fdbf spec: sourcePod: network-check-source-6f78d59f99-rjz49 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T14:19:43Z" message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.763526ms message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:22:43Z" - latency: 2.509014ms message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:21:43Z" - latency: 2.682852ms message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:20:43Z" - latency: 2.676357ms message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:19:43Z" - latency: 2.894874ms message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:18:43Z" - latency: 2.67066ms message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:17:43Z" - latency: 2.198725ms message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:16:43Z" - latency: 2.443342ms message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:15:43Z" - latency: 1.983964ms message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:14:43Z" - latency: 2.32734ms message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:13:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T14:12:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-171-to-network-check-target-ip-10-0-143-171 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-171.ec2.internal uid: 9bdf0ef5-24db-4dae-94d5-bed0fb69ff91 resourceVersion: "118844" uid: 660699f9-ae29-42bb-82c0-6a490e68193b spec: sourcePod: network-check-source-6f78d59f99-rjz49 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T14:19:43Z" message: 'network-check-target-ip-10-0-143-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.6051ms message: 'network-check-target-ip-10-0-143-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:22:43Z" - latency: 914.385µs message: 'network-check-target-ip-10-0-143-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:21:43Z" - latency: 1.419655ms message: 'network-check-target-ip-10-0-143-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:20:43Z" - latency: 852.352µs message: 'network-check-target-ip-10-0-143-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:19:43Z" - latency: 831.462µs message: 'network-check-target-ip-10-0-143-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:18:43Z" - latency: 1.086307ms message: 'network-check-target-ip-10-0-143-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:17:43Z" - latency: 938.951µs message: 'network-check-target-ip-10-0-143-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:16:43Z" - latency: 828.936µs message: 'network-check-target-ip-10-0-143-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:15:43Z" - latency: 1.079495ms message: 'network-check-target-ip-10-0-143-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:14:43Z" - latency: 994.369µs message: 'network-check-target-ip-10-0-143-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:13:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T14:12:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-171-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-171.ec2.internal uid: 9bdf0ef5-24db-4dae-94d5-bed0fb69ff91 resourceVersion: "120484" uid: 9bc4676d-082c-4658-86b0-a4c490942248 spec: sourcePod: network-check-source-6f78d59f99-rjz49 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T14:18:43Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.037033ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:24:43Z" - latency: 1.708139ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T15:24:43Z" - latency: 1.111496ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:23:43Z" - latency: 1.940485ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T15:23:43Z" - latency: 1.233515ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:22:43Z" - latency: 1.726693ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T15:22:43Z" - latency: 899.646µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:21:43Z" - latency: 2.149526ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T15:21:43Z" - latency: 946.623µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:20:43Z" - latency: 2.016591ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T15:20:43Z" kind: List metadata: resourceVersion: ""