apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T19:25:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-249-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-249.ec2.internal uid: 6d7bde22-2812-4245-b7c2-00985baa1e23 resourceVersion: "54416" uid: c4acd2fd-0260-4e89-957b-e060287da144 spec: sourcePod: network-check-source-869dcfcdcd-4v8vd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-12T19:32:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.232262ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T20:00:22Z" - latency: 1.190175ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:59:22Z" - latency: 1.248334ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:58:22Z" - latency: 1.130447ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:57:22Z" - latency: 1.325529ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:56:22Z" - latency: 1.019014ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:55:22Z" - latency: 1.338408ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:54:22Z" - latency: 1.189772ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:53:22Z" - latency: 866.673µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:52:22Z" - latency: 1.108374ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:51:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T19:25:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-249-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-249.ec2.internal uid: 6d7bde22-2812-4245-b7c2-00985baa1e23 resourceVersion: "55476" uid: 456056d0-e7ae-4415-bcab-7eb4472e6c50 spec: sourcePod: network-check-source-869dcfcdcd-4v8vd targetEndpoint: a6be1fc95a3f745119cd290ba6aeb844-0ff466a8267f8eb1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-12T19:31:22Z" message: 'load-balancer-api-external: tcp connection to a6be1fc95a3f745119cd290ba6aeb844-0ff466a8267f8eb1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.269405ms message: 'load-balancer-api-external: tcp connection to a6be1fc95a3f745119cd290ba6aeb844-0ff466a8267f8eb1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T20:01:22Z" - latency: 8.49699ms message: 'load-balancer-api-external: resolved host name a6be1fc95a3f745119cd290ba6aeb844-0ff466a8267f8eb1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T20:01:22Z" - latency: 5.876884ms message: 'load-balancer-api-external: tcp connection to a6be1fc95a3f745119cd290ba6aeb844-0ff466a8267f8eb1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T20:00:22Z" - latency: 8.239303ms message: 'load-balancer-api-external: resolved host name a6be1fc95a3f745119cd290ba6aeb844-0ff466a8267f8eb1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T20:00:22Z" - latency: 4.146095ms message: 'load-balancer-api-external: tcp connection to a6be1fc95a3f745119cd290ba6aeb844-0ff466a8267f8eb1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:59:22Z" - latency: 8.293819ms message: 'load-balancer-api-external: resolved host name a6be1fc95a3f745119cd290ba6aeb844-0ff466a8267f8eb1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T19:59:22Z" - latency: 4.975802ms message: 'load-balancer-api-external: tcp connection to a6be1fc95a3f745119cd290ba6aeb844-0ff466a8267f8eb1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:58:22Z" - latency: 8.852368ms message: 'load-balancer-api-external: resolved host name a6be1fc95a3f745119cd290ba6aeb844-0ff466a8267f8eb1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T19:58:22Z" - latency: 4.067424ms message: 'load-balancer-api-external: tcp connection to a6be1fc95a3f745119cd290ba6aeb844-0ff466a8267f8eb1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:57:22Z" - latency: 8.303779ms message: 'load-balancer-api-external: resolved host name a6be1fc95a3f745119cd290ba6aeb844-0ff466a8267f8eb1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T19:57:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T19:25:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-249-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-249.ec2.internal uid: 6d7bde22-2812-4245-b7c2-00985baa1e23 resourceVersion: "55477" uid: 326caf0f-abad-4813-8f9b-6e68dcf6756b spec: sourcePod: network-check-source-869dcfcdcd-4v8vd targetEndpoint: a6be1fc95a3f745119cd290ba6aeb844-0ff466a8267f8eb1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-12T19:31:22Z" message: 'load-balancer-api-internal: tcp connection to a6be1fc95a3f745119cd290ba6aeb844-0ff466a8267f8eb1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.221524ms message: 'load-balancer-api-internal: tcp connection to a6be1fc95a3f745119cd290ba6aeb844-0ff466a8267f8eb1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T20:01:22Z" - latency: 8.538138ms message: 'load-balancer-api-internal: resolved host name a6be1fc95a3f745119cd290ba6aeb844-0ff466a8267f8eb1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T20:01:22Z" - latency: 3.879043ms message: 'load-balancer-api-internal: tcp connection to a6be1fc95a3f745119cd290ba6aeb844-0ff466a8267f8eb1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T20:00:22Z" - latency: 8.29852ms message: 'load-balancer-api-internal: resolved host name a6be1fc95a3f745119cd290ba6aeb844-0ff466a8267f8eb1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T20:00:22Z" - latency: 4.128032ms message: 'load-balancer-api-internal: tcp connection to a6be1fc95a3f745119cd290ba6aeb844-0ff466a8267f8eb1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:59:22Z" - latency: 8.273171ms message: 'load-balancer-api-internal: resolved host name a6be1fc95a3f745119cd290ba6aeb844-0ff466a8267f8eb1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T19:59:22Z" - latency: 5.440951ms message: 'load-balancer-api-internal: tcp connection to a6be1fc95a3f745119cd290ba6aeb844-0ff466a8267f8eb1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:58:22Z" - latency: 8.77862ms message: 'load-balancer-api-internal: resolved host name a6be1fc95a3f745119cd290ba6aeb844-0ff466a8267f8eb1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T19:58:22Z" - latency: 4.022396ms message: 'load-balancer-api-internal: tcp connection to a6be1fc95a3f745119cd290ba6aeb844-0ff466a8267f8eb1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:57:22Z" - latency: 8.335131ms message: 'load-balancer-api-internal: resolved host name a6be1fc95a3f745119cd290ba6aeb844-0ff466a8267f8eb1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T19:57:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T19:25:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-249-to-network-check-target-ip-10-0-137-63 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-249.ec2.internal uid: 6d7bde22-2812-4245-b7c2-00985baa1e23 resourceVersion: "54414" uid: f2c8522a-8529-4c89-bb13-fa4332e33018 spec: sourcePod: network-check-source-869dcfcdcd-4v8vd targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-12T19:32:22Z" message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.949525ms message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T20:00:22Z" - latency: 1.817288ms message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:59:22Z" - latency: 1.78465ms message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:58:22Z" - latency: 2.337634ms message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:57:22Z" - latency: 1.802202ms message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:56:22Z" - latency: 1.931623ms message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:55:22Z" - latency: 1.717125ms message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:54:22Z" - latency: 1.940624ms message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:53:22Z" - latency: 2.084968ms message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:52:22Z" - latency: 2.768481ms message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:51:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T19:25:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-249-to-network-check-target-ip-10-0-139-170 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-249.ec2.internal uid: 6d7bde22-2812-4245-b7c2-00985baa1e23 resourceVersion: "54415" uid: 14c1c305-568a-4922-be1d-392ad2bbae86 spec: sourcePod: network-check-source-869dcfcdcd-4v8vd targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-12T19:32:22Z" message: 'network-check-target-ip-10-0-139-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.06165ms message: 'network-check-target-ip-10-0-139-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T20:00:22Z" - latency: 1.790499ms message: 'network-check-target-ip-10-0-139-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:59:22Z" - latency: 2.179702ms message: 'network-check-target-ip-10-0-139-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:58:22Z" - latency: 2.073454ms message: 'network-check-target-ip-10-0-139-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:57:22Z" - latency: 2.004392ms message: 'network-check-target-ip-10-0-139-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:56:22Z" - latency: 1.918594ms message: 'network-check-target-ip-10-0-139-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:55:22Z" - latency: 1.851759ms message: 'network-check-target-ip-10-0-139-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:54:22Z" - latency: 2.002734ms message: 'network-check-target-ip-10-0-139-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:53:22Z" - latency: 1.733103ms message: 'network-check-target-ip-10-0-139-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:52:22Z" - latency: 2.705937ms message: 'network-check-target-ip-10-0-139-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:51:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T19:25:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-249-to-network-check-target-ip-10-0-141-249 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-249.ec2.internal uid: 6d7bde22-2812-4245-b7c2-00985baa1e23 resourceVersion: "54413" uid: 6d75c467-3675-48d0-8872-dd5c52bd9bb7 spec: sourcePod: network-check-source-869dcfcdcd-4v8vd targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-12T19:32:22Z" message: 'network-check-target-ip-10-0-141-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 945.424µs message: 'network-check-target-ip-10-0-141-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T20:00:22Z" - latency: 870.041µs message: 'network-check-target-ip-10-0-141-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:59:22Z" - latency: 1.142939ms message: 'network-check-target-ip-10-0-141-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:58:22Z" - latency: 1.664657ms message: 'network-check-target-ip-10-0-141-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:57:22Z" - latency: 954.578µs message: 'network-check-target-ip-10-0-141-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:56:22Z" - latency: 1.575436ms message: 'network-check-target-ip-10-0-141-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:55:22Z" - latency: 1.046599ms message: 'network-check-target-ip-10-0-141-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:54:22Z" - latency: 887.082µs message: 'network-check-target-ip-10-0-141-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:53:22Z" - latency: 967.795µs message: 'network-check-target-ip-10-0-141-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:52:22Z" - latency: 922.298µs message: 'network-check-target-ip-10-0-141-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:51:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T19:25:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-249-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-249.ec2.internal uid: 6d7bde22-2812-4245-b7c2-00985baa1e23 resourceVersion: "55475" uid: 84369663-2c7c-4073-9778-4527387ef6a2 spec: sourcePod: network-check-source-869dcfcdcd-4v8vd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-12T19:31:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.275949ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T20:01:22Z" - latency: 1.883155ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T20:01:22Z" - latency: 749.591µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T20:00:22Z" - latency: 1.967034ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T20:00:22Z" - latency: 848.609µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:59:22Z" - latency: 1.712782ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T19:59:22Z" - latency: 1.095246ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:58:22Z" - latency: 1.803561ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T19:58:22Z" - latency: 859.94µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:57:22Z" - latency: 1.97429ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T19:57:22Z" kind: List metadata: resourceVersion: ""