apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T12:15:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-94-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-94.ec2.internal uid: acdf22d4-8952-4c7f-8656-33d4ad5f6d02 resourceVersion: "48610" uid: 1f6a39c2-cc43-4ec3-b949-2c6795510100 spec: sourcePod: network-check-source-989f8b8dc-zjkp8 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T12:22:37Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.248194ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:43:37Z" - latency: 1.346756ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:42:37Z" - latency: 1.102805ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:41:37Z" - latency: 1.101541ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:40:37Z" - latency: 1.098441ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:39:37Z" - latency: 773.775µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:38:37Z" - latency: 1.010142ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:37:37Z" - latency: 1.016301ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:36:37Z" - latency: 1.157679ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:35:37Z" - latency: 1.029192ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:34:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T12:15:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-94-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-94.ec2.internal uid: acdf22d4-8952-4c7f-8656-33d4ad5f6d02 resourceVersion: "50700" uid: 773c5f45-4a19-4839-b65c-f92a36ebc418 spec: sourcePod: network-check-source-989f8b8dc-zjkp8 targetEndpoint: a6211ff51d4da4be0a5cf1269172442e-df8ba01423ace0c5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T12:21:37Z" message: 'load-balancer-api-external: tcp connection to a6211ff51d4da4be0a5cf1269172442e-df8ba01423ace0c5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.969338ms message: 'load-balancer-api-external: tcp connection to a6211ff51d4da4be0a5cf1269172442e-df8ba01423ace0c5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:45:37Z" - latency: 6.893703ms message: 'load-balancer-api-external: resolved host name a6211ff51d4da4be0a5cf1269172442e-df8ba01423ace0c5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T12:45:37Z" - latency: 6.427008ms message: 'load-balancer-api-external: tcp connection to a6211ff51d4da4be0a5cf1269172442e-df8ba01423ace0c5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:44:37Z" - latency: 6.699953ms message: 'load-balancer-api-external: resolved host name a6211ff51d4da4be0a5cf1269172442e-df8ba01423ace0c5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T12:44:37Z" - latency: 5.492376ms message: 'load-balancer-api-external: tcp connection to a6211ff51d4da4be0a5cf1269172442e-df8ba01423ace0c5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:43:37Z" - latency: 6.215349ms message: 'load-balancer-api-external: resolved host name a6211ff51d4da4be0a5cf1269172442e-df8ba01423ace0c5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T12:43:37Z" - latency: 5.187036ms message: 'load-balancer-api-external: tcp connection to a6211ff51d4da4be0a5cf1269172442e-df8ba01423ace0c5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:42:37Z" - latency: 14.255746ms message: 'load-balancer-api-external: resolved host name a6211ff51d4da4be0a5cf1269172442e-df8ba01423ace0c5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T12:42:37Z" - latency: 5.938528ms message: 'load-balancer-api-external: tcp connection to a6211ff51d4da4be0a5cf1269172442e-df8ba01423ace0c5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:41:37Z" - latency: 6.817696ms message: 'load-balancer-api-external: resolved host name a6211ff51d4da4be0a5cf1269172442e-df8ba01423ace0c5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T12:41:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T12:15:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-94-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-94.ec2.internal uid: acdf22d4-8952-4c7f-8656-33d4ad5f6d02 resourceVersion: "50699" uid: 989310f1-ef9f-423f-a61e-be302053c843 spec: sourcePod: network-check-source-989f8b8dc-zjkp8 targetEndpoint: a6211ff51d4da4be0a5cf1269172442e-df8ba01423ace0c5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T12:21:37Z" message: 'load-balancer-api-internal: tcp connection to a6211ff51d4da4be0a5cf1269172442e-df8ba01423ace0c5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.955892ms message: 'load-balancer-api-internal: tcp connection to a6211ff51d4da4be0a5cf1269172442e-df8ba01423ace0c5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:45:37Z" - latency: 6.828624ms message: 'load-balancer-api-internal: resolved host name a6211ff51d4da4be0a5cf1269172442e-df8ba01423ace0c5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T12:45:37Z" - latency: 4.943328ms message: 'load-balancer-api-internal: tcp connection to a6211ff51d4da4be0a5cf1269172442e-df8ba01423ace0c5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:44:37Z" - latency: 6.792276ms message: 'load-balancer-api-internal: resolved host name a6211ff51d4da4be0a5cf1269172442e-df8ba01423ace0c5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T12:44:37Z" - latency: 5.448848ms message: 'load-balancer-api-internal: tcp connection to a6211ff51d4da4be0a5cf1269172442e-df8ba01423ace0c5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:43:37Z" - latency: 6.174713ms message: 'load-balancer-api-internal: resolved host name a6211ff51d4da4be0a5cf1269172442e-df8ba01423ace0c5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T12:43:37Z" - latency: 5.166264ms message: 'load-balancer-api-internal: tcp connection to a6211ff51d4da4be0a5cf1269172442e-df8ba01423ace0c5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:42:37Z" - latency: 14.329679ms message: 'load-balancer-api-internal: resolved host name a6211ff51d4da4be0a5cf1269172442e-df8ba01423ace0c5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T12:42:37Z" - latency: 5.947043ms message: 'load-balancer-api-internal: tcp connection to a6211ff51d4da4be0a5cf1269172442e-df8ba01423ace0c5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:41:37Z" - latency: 6.894118ms message: 'load-balancer-api-internal: resolved host name a6211ff51d4da4be0a5cf1269172442e-df8ba01423ace0c5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T12:41:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T12:15:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-94-to-network-check-target-ip-10-0-128-128 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-94.ec2.internal uid: acdf22d4-8952-4c7f-8656-33d4ad5f6d02 resourceVersion: "48608" uid: 6646cf93-9815-4862-8753-35a496b418d9 spec: sourcePod: network-check-source-989f8b8dc-zjkp8 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T12:22:37Z" message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.035854ms message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:43:37Z" - latency: 2.057724ms message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:42:37Z" - latency: 1.983816ms message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:41:37Z" - latency: 2.12609ms message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:40:37Z" - latency: 1.951948ms message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:39:37Z" - latency: 2.034263ms message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:38:37Z" - latency: 1.964674ms message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:37:37Z" - latency: 2.028336ms message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:36:37Z" - latency: 2.129542ms message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:35:37Z" - latency: 1.883083ms message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:34:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T12:15:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-94-to-network-check-target-ip-10-0-133-7 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-94.ec2.internal uid: acdf22d4-8952-4c7f-8656-33d4ad5f6d02 resourceVersion: "48609" uid: af4ed55c-c2a8-49af-8d57-da877bf179cd spec: sourcePod: network-check-source-989f8b8dc-zjkp8 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T12:22:37Z" message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.50812ms message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:43:37Z" - latency: 2.470975ms message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:42:37Z" - latency: 2.139037ms message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:41:37Z" - latency: 2.724632ms message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:40:37Z" - latency: 2.2759ms message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:39:37Z" - latency: 2.276267ms message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:38:37Z" - latency: 2.280544ms message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:37:37Z" - latency: 2.409259ms message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:36:37Z" - latency: 2.275212ms message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:35:37Z" - latency: 2.025325ms message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:34:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T12:15:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-94-to-network-check-target-ip-10-0-141-94 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-94.ec2.internal uid: acdf22d4-8952-4c7f-8656-33d4ad5f6d02 resourceVersion: "48607" uid: d514cacb-eaee-4b07-87ba-87b184f1e746 spec: sourcePod: network-check-source-989f8b8dc-zjkp8 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T12:22:37Z" message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 834.453µs message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:43:37Z" - latency: 1.097537ms message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:42:37Z" - latency: 854.056µs message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:41:37Z" - latency: 932.486µs message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:40:37Z" - latency: 1.017607ms message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:39:37Z" - latency: 1.210051ms message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:38:37Z" - latency: 1.014906ms message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:37:37Z" - latency: 1.248732ms message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:36:37Z" - latency: 774.72µs message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:35:37Z" - latency: 920.093µs message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:34:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T12:15:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-94-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-94.ec2.internal uid: acdf22d4-8952-4c7f-8656-33d4ad5f6d02 resourceVersion: "50698" uid: 95e4be99-9177-490e-9e1e-5eb1a37d2491 spec: sourcePod: network-check-source-989f8b8dc-zjkp8 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T12:21:37Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.002713ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:45:37Z" - latency: 1.876958ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T12:45:37Z" - latency: 983.124µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:44:37Z" - latency: 1.837834ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T12:44:37Z" - latency: 874.055µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:43:37Z" - latency: 1.758445ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T12:43:37Z" - latency: 833.379µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:42:37Z" - latency: 1.886354ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T12:42:37Z" - latency: 1.112238ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T12:41:37Z" - latency: 1.926424ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T12:41:37Z" kind: List metadata: resourceVersion: ""