apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T07:53:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-164-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-164.ec2.internal uid: ffc84cda-28c8-4e55-b18e-ac0c443f77e3 resourceVersion: "60158" uid: 93628d7c-0863-4b3a-b584-9bf6a192e639 spec: sourcePod: network-check-source-869dcfcdcd-hd9p5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-14T08:00:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.459754ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:35:02Z" - latency: 1.310892ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:34:02Z" - latency: 959.847µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:33:02Z" - latency: 1.162321ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:32:02Z" - latency: 1.69262ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:31:02Z" - latency: 1.276493ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:30:02Z" - latency: 1.034023ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:29:02Z" - latency: 1.246795ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:28:02Z" - latency: 876.315µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:27:02Z" - latency: 1.308152ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:26:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T07:53:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-164-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-164.ec2.internal uid: ffc84cda-28c8-4e55-b18e-ac0c443f77e3 resourceVersion: "60160" uid: b3a75132-58e5-4472-9e83-35fbe517089c spec: sourcePod: network-check-source-869dcfcdcd-hd9p5 targetEndpoint: a3e8e0aa7cc824bdb90d54c58c81bb88-76fff3b052621846.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T07:59:02Z" message: 'load-balancer-api-external: tcp connection to a3e8e0aa7cc824bdb90d54c58c81bb88-76fff3b052621846.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.706329ms message: 'load-balancer-api-external: tcp connection to a3e8e0aa7cc824bdb90d54c58c81bb88-76fff3b052621846.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:35:02Z" - latency: 8.754135ms message: 'load-balancer-api-external: resolved host name a3e8e0aa7cc824bdb90d54c58c81bb88-76fff3b052621846.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T08:35:02Z" - latency: 4.688964ms message: 'load-balancer-api-external: tcp connection to a3e8e0aa7cc824bdb90d54c58c81bb88-76fff3b052621846.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:34:02Z" - latency: 7.516273ms message: 'load-balancer-api-external: resolved host name a3e8e0aa7cc824bdb90d54c58c81bb88-76fff3b052621846.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T08:34:02Z" - latency: 3.378478ms message: 'load-balancer-api-external: tcp connection to a3e8e0aa7cc824bdb90d54c58c81bb88-76fff3b052621846.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:33:02Z" - latency: 7.794703ms message: 'load-balancer-api-external: resolved host name a3e8e0aa7cc824bdb90d54c58c81bb88-76fff3b052621846.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T08:33:02Z" - latency: 3.882629ms message: 'load-balancer-api-external: tcp connection to a3e8e0aa7cc824bdb90d54c58c81bb88-76fff3b052621846.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:32:02Z" - latency: 10.585704ms message: 'load-balancer-api-external: resolved host name a3e8e0aa7cc824bdb90d54c58c81bb88-76fff3b052621846.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T08:32:02Z" - latency: 4.628253ms message: 'load-balancer-api-external: tcp connection to a3e8e0aa7cc824bdb90d54c58c81bb88-76fff3b052621846.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:31:02Z" - latency: 6.600333ms message: 'load-balancer-api-external: resolved host name a3e8e0aa7cc824bdb90d54c58c81bb88-76fff3b052621846.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T08:31:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T07:53:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-164-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-164.ec2.internal uid: ffc84cda-28c8-4e55-b18e-ac0c443f77e3 resourceVersion: "60161" uid: 599741e5-6af7-48d7-8ca0-f83457159c0a spec: sourcePod: network-check-source-869dcfcdcd-hd9p5 targetEndpoint: a3e8e0aa7cc824bdb90d54c58c81bb88-76fff3b052621846.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T07:59:02Z" message: 'load-balancer-api-internal: tcp connection to a3e8e0aa7cc824bdb90d54c58c81bb88-76fff3b052621846.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.700623ms message: 'load-balancer-api-internal: tcp connection to a3e8e0aa7cc824bdb90d54c58c81bb88-76fff3b052621846.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:35:02Z" - latency: 8.806179ms message: 'load-balancer-api-internal: resolved host name a3e8e0aa7cc824bdb90d54c58c81bb88-76fff3b052621846.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T08:35:02Z" - latency: 4.672244ms message: 'load-balancer-api-internal: tcp connection to a3e8e0aa7cc824bdb90d54c58c81bb88-76fff3b052621846.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:34:02Z" - latency: 7.582463ms message: 'load-balancer-api-internal: resolved host name a3e8e0aa7cc824bdb90d54c58c81bb88-76fff3b052621846.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T08:34:02Z" - latency: 5.243455ms message: 'load-balancer-api-internal: tcp connection to a3e8e0aa7cc824bdb90d54c58c81bb88-76fff3b052621846.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:33:02Z" - latency: 7.603659ms message: 'load-balancer-api-internal: resolved host name a3e8e0aa7cc824bdb90d54c58c81bb88-76fff3b052621846.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T08:33:02Z" - latency: 3.77194ms message: 'load-balancer-api-internal: tcp connection to a3e8e0aa7cc824bdb90d54c58c81bb88-76fff3b052621846.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:32:02Z" - latency: 10.565358ms message: 'load-balancer-api-internal: resolved host name a3e8e0aa7cc824bdb90d54c58c81bb88-76fff3b052621846.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T08:32:02Z" - latency: 4.795599ms message: 'load-balancer-api-internal: tcp connection to a3e8e0aa7cc824bdb90d54c58c81bb88-76fff3b052621846.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:31:02Z" - latency: 6.554355ms message: 'load-balancer-api-internal: resolved host name a3e8e0aa7cc824bdb90d54c58c81bb88-76fff3b052621846.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T08:31:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T07:53:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-164-to-network-check-target-ip-10-0-128-86 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-164.ec2.internal uid: ffc84cda-28c8-4e55-b18e-ac0c443f77e3 resourceVersion: "60156" uid: 558148c3-b5e6-4020-b742-9f9f54306739 spec: sourcePod: network-check-source-869dcfcdcd-hd9p5 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-14T08:00:02Z" message: 'network-check-target-ip-10-0-128-86: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.765553ms message: 'network-check-target-ip-10-0-128-86: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:35:02Z" - latency: 2.435329ms message: 'network-check-target-ip-10-0-128-86: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:34:02Z" - latency: 2.323954ms message: 'network-check-target-ip-10-0-128-86: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:33:02Z" - latency: 2.391502ms message: 'network-check-target-ip-10-0-128-86: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:32:02Z" - latency: 2.381832ms message: 'network-check-target-ip-10-0-128-86: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:31:02Z" - latency: 2.707361ms message: 'network-check-target-ip-10-0-128-86: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:30:02Z" - latency: 2.329807ms message: 'network-check-target-ip-10-0-128-86: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:29:02Z" - latency: 2.691699ms message: 'network-check-target-ip-10-0-128-86: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:28:02Z" - latency: 2.317737ms message: 'network-check-target-ip-10-0-128-86: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:27:02Z" - latency: 2.348831ms message: 'network-check-target-ip-10-0-128-86: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:26:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T07:53:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-164-to-network-check-target-ip-10-0-129-164 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-164.ec2.internal uid: ffc84cda-28c8-4e55-b18e-ac0c443f77e3 resourceVersion: "60154" uid: 2bd6d9b9-6ac8-4607-a82b-95c4aeec3125 spec: sourcePod: network-check-source-869dcfcdcd-hd9p5 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-14T08:00:02Z" message: 'network-check-target-ip-10-0-129-164: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.687214ms message: 'network-check-target-ip-10-0-129-164: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:35:02Z" - latency: 1.035499ms message: 'network-check-target-ip-10-0-129-164: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:34:02Z" - latency: 1.027145ms message: 'network-check-target-ip-10-0-129-164: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:33:02Z" - latency: 1.001874ms message: 'network-check-target-ip-10-0-129-164: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:32:02Z" - latency: 1.101535ms message: 'network-check-target-ip-10-0-129-164: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:31:02Z" - latency: 1.503847ms message: 'network-check-target-ip-10-0-129-164: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:30:02Z" - latency: 922.939µs message: 'network-check-target-ip-10-0-129-164: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:29:02Z" - latency: 998.439µs message: 'network-check-target-ip-10-0-129-164: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:28:02Z" - latency: 1.064862ms message: 'network-check-target-ip-10-0-129-164: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:27:02Z" - latency: 1.0785ms message: 'network-check-target-ip-10-0-129-164: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:26:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T07:53:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-164-to-network-check-target-ip-10-0-131-251 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-164.ec2.internal uid: ffc84cda-28c8-4e55-b18e-ac0c443f77e3 resourceVersion: "60155" uid: 78199f1d-33e1-435b-83f5-553871f00c25 spec: sourcePod: network-check-source-869dcfcdcd-hd9p5 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-14T08:00:02Z" message: 'network-check-target-ip-10-0-131-251: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.830139ms message: 'network-check-target-ip-10-0-131-251: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:35:02Z" - latency: 2.305641ms message: 'network-check-target-ip-10-0-131-251: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:34:02Z" - latency: 2.647393ms message: 'network-check-target-ip-10-0-131-251: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:33:02Z" - latency: 2.367647ms message: 'network-check-target-ip-10-0-131-251: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:32:02Z" - latency: 3.073802ms message: 'network-check-target-ip-10-0-131-251: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:31:02Z" - latency: 3.02624ms message: 'network-check-target-ip-10-0-131-251: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:30:02Z" - latency: 2.286668ms message: 'network-check-target-ip-10-0-131-251: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:29:02Z" - latency: 2.386047ms message: 'network-check-target-ip-10-0-131-251: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:28:02Z" - latency: 2.69977ms message: 'network-check-target-ip-10-0-131-251: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:27:02Z" - latency: 2.071315ms message: 'network-check-target-ip-10-0-131-251: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:26:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T07:53:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-164-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-164.ec2.internal uid: ffc84cda-28c8-4e55-b18e-ac0c443f77e3 resourceVersion: "60157" uid: 456558cb-8482-415b-bef7-1b3ad0c07ec3 spec: sourcePod: network-check-source-869dcfcdcd-hd9p5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-14T07:59:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 922.145µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:35:02Z" - latency: 2.724773ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T08:35:02Z" - latency: 1.367859ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:34:02Z" - latency: 1.803951ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T08:34:02Z" - latency: 938.719µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:33:02Z" - latency: 1.808458ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T08:33:02Z" - latency: 982.95µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:32:02Z" - latency: 2.085698ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T08:32:02Z" - latency: 932.786µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T08:31:02Z" - latency: 1.804827ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T08:31:02Z" kind: List metadata: resourceVersion: ""