apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:42:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-118-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-118.ec2.internal uid: af268491-8b54-4afb-b6d5-34b3e7ded7f7 resourceVersion: "72011" uid: 0d9c0b99-655e-437b-9541-5344ba8a95e9 spec: sourcePod: network-check-source-869dcfcdcd-kns7z targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T17:49: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.337418ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:38:37Z" - latency: 1.532381ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:37:37Z" - latency: 1.639243ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:36:37Z" - latency: 1.373614ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:35:37Z" - latency: 1.220977ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:34:37Z" - latency: 1.051143ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:33:37Z" - latency: 1.846893ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:32:37Z" - latency: 1.295769ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:31:37Z" - latency: 1.420434ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:30:37Z" - latency: 1.339321ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:29:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:42:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-118-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-118.ec2.internal uid: af268491-8b54-4afb-b6d5-34b3e7ded7f7 resourceVersion: "69328" uid: 475b04cf-b4c2-4770-95b9-a67721754d6b spec: sourcePod: network-check-source-869dcfcdcd-kns7z targetEndpoint: a06caf0690c83408e8e1ab76b1cacb04-6bd3147b9bc78608.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T17:48:37Z" message: 'load-balancer-api-external: tcp connection to a06caf0690c83408e8e1ab76b1cacb04-6bd3147b9bc78608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.981399ms message: 'load-balancer-api-external: tcp connection to a06caf0690c83408e8e1ab76b1cacb04-6bd3147b9bc78608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:36:37Z" - latency: 12.416819ms message: 'load-balancer-api-external: resolved host name a06caf0690c83408e8e1ab76b1cacb04-6bd3147b9bc78608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:36:37Z" - latency: 4.999966ms message: 'load-balancer-api-external: tcp connection to a06caf0690c83408e8e1ab76b1cacb04-6bd3147b9bc78608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:35:37Z" - latency: 12.846692ms message: 'load-balancer-api-external: resolved host name a06caf0690c83408e8e1ab76b1cacb04-6bd3147b9bc78608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:35:37Z" - latency: 4.110603ms message: 'load-balancer-api-external: tcp connection to a06caf0690c83408e8e1ab76b1cacb04-6bd3147b9bc78608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:34:37Z" - latency: 13.4796ms message: 'load-balancer-api-external: resolved host name a06caf0690c83408e8e1ab76b1cacb04-6bd3147b9bc78608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:34:37Z" - latency: 4.490906ms message: 'load-balancer-api-external: tcp connection to a06caf0690c83408e8e1ab76b1cacb04-6bd3147b9bc78608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:33:37Z" - latency: 12.182115ms message: 'load-balancer-api-external: resolved host name a06caf0690c83408e8e1ab76b1cacb04-6bd3147b9bc78608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:33:37Z" - latency: 4.885402ms message: 'load-balancer-api-external: tcp connection to a06caf0690c83408e8e1ab76b1cacb04-6bd3147b9bc78608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:32:37Z" - latency: 17.197902ms message: 'load-balancer-api-external: resolved host name a06caf0690c83408e8e1ab76b1cacb04-6bd3147b9bc78608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:32:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:42:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-118-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-118.ec2.internal uid: af268491-8b54-4afb-b6d5-34b3e7ded7f7 resourceVersion: "69329" uid: fcda60de-0852-451f-9198-367833efcdb4 spec: sourcePod: network-check-source-869dcfcdcd-kns7z targetEndpoint: a06caf0690c83408e8e1ab76b1cacb04-6bd3147b9bc78608.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T17:48:37Z" message: 'load-balancer-api-internal: tcp connection to a06caf0690c83408e8e1ab76b1cacb04-6bd3147b9bc78608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.372545ms message: 'load-balancer-api-internal: tcp connection to a06caf0690c83408e8e1ab76b1cacb04-6bd3147b9bc78608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:36:37Z" - latency: 12.523835ms message: 'load-balancer-api-internal: resolved host name a06caf0690c83408e8e1ab76b1cacb04-6bd3147b9bc78608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:36:37Z" - latency: 5.011644ms message: 'load-balancer-api-internal: tcp connection to a06caf0690c83408e8e1ab76b1cacb04-6bd3147b9bc78608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:35:37Z" - latency: 12.758683ms message: 'load-balancer-api-internal: resolved host name a06caf0690c83408e8e1ab76b1cacb04-6bd3147b9bc78608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:35:37Z" - latency: 4.043612ms message: 'load-balancer-api-internal: tcp connection to a06caf0690c83408e8e1ab76b1cacb04-6bd3147b9bc78608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:34:37Z" - latency: 13.553008ms message: 'load-balancer-api-internal: resolved host name a06caf0690c83408e8e1ab76b1cacb04-6bd3147b9bc78608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:34:37Z" - latency: 4.49526ms message: 'load-balancer-api-internal: tcp connection to a06caf0690c83408e8e1ab76b1cacb04-6bd3147b9bc78608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:33:37Z" - latency: 12.210959ms message: 'load-balancer-api-internal: resolved host name a06caf0690c83408e8e1ab76b1cacb04-6bd3147b9bc78608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:33:37Z" - latency: 5.165846ms message: 'load-balancer-api-internal: tcp connection to a06caf0690c83408e8e1ab76b1cacb04-6bd3147b9bc78608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:32:37Z" - latency: 17.214335ms message: 'load-balancer-api-internal: resolved host name a06caf0690c83408e8e1ab76b1cacb04-6bd3147b9bc78608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:32:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:42:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-118-to-network-check-target-ip-10-0-132-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-118.ec2.internal uid: af268491-8b54-4afb-b6d5-34b3e7ded7f7 resourceVersion: "72008" uid: 105616a2-756e-42d7-a6a6-7322ebfcc7a9 spec: sourcePod: network-check-source-869dcfcdcd-kns7z targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T17:49:37Z" message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.308898ms message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:38:37Z" - latency: 2.281546ms message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:37:37Z" - latency: 3.062619ms message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:36:37Z" - latency: 2.12314ms message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:35:37Z" - latency: 2.501474ms message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:34:37Z" - latency: 2.208187ms message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:33:37Z" - latency: 2.518957ms message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:32:37Z" - latency: 2.508396ms message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:31:37Z" - latency: 2.832677ms message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:30:37Z" - latency: 2.378507ms message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:29:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:42:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-118-to-network-check-target-ip-10-0-141-118 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-118.ec2.internal uid: af268491-8b54-4afb-b6d5-34b3e7ded7f7 resourceVersion: "72007" uid: 21eb8210-2959-4c95-af26-1ce772115131 spec: sourcePod: network-check-source-869dcfcdcd-kns7z targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T17:49:37Z" message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.175321ms message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:38:37Z" - latency: 1.079256ms message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:37:37Z" - latency: 1.740557ms message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:36:37Z" - latency: 1.015838ms message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:35:37Z" - latency: 2.608878ms message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:34:37Z" - latency: 860.574µs message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:33:37Z" - latency: 1.524337ms message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:32:37Z" - latency: 1.964905ms message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:31:37Z" - latency: 1.03649ms message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:30:37Z" - latency: 968.837µs message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:29:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:42:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-118-to-network-check-target-ip-10-0-141-44 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-118.ec2.internal uid: af268491-8b54-4afb-b6d5-34b3e7ded7f7 resourceVersion: "72009" uid: a6004660-f233-4bb5-8817-d26dcae728c3 spec: sourcePod: network-check-source-869dcfcdcd-kns7z targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T17:49:37Z" message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.233511ms message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:38:37Z" - latency: 2.052501ms message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:37:37Z" - latency: 2.440413ms message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:36:37Z" - latency: 2.415022ms message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:35:37Z" - latency: 2.208283ms message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:34:37Z" - latency: 2.610991ms message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:33:37Z" - latency: 2.2303ms message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:32:37Z" - latency: 2.311395ms message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:31:37Z" - latency: 1.967521ms message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:30:37Z" - latency: 2.381524ms message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:29:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:42:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-118-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-118.ec2.internal uid: af268491-8b54-4afb-b6d5-34b3e7ded7f7 resourceVersion: "69326" uid: 57830749-e569-467a-9a09-f27a27a9037f spec: sourcePod: network-check-source-869dcfcdcd-kns7z targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T17:48:37Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 937.509µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:36:37Z" - latency: 2.44225ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:36:37Z" - latency: 1.219823ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:35:37Z" - latency: 2.443628ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:35:37Z" - latency: 1.23337ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:34:37Z" - latency: 2.636456ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:34:37Z" - latency: 1.194267ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:33:37Z" - latency: 2.45597ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:33:37Z" - latency: 912.66µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:32:37Z" - latency: 2.048124ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:32:37Z" kind: List metadata: resourceVersion: ""