apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T21:11:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-26-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-26.ec2.internal uid: b3ba39c0-39fb-45b9-9806-652f4f4d5b7d resourceVersion: "27558" uid: e18accc6-2d7a-4a47-b0e0-309c4fe0d428 spec: sourcePod: network-check-source-7cbc45fddc-gbl2s targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-18T21:18:06Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 850.77µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:25:06Z" - latency: 812.973µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:24:06Z" - latency: 946.166µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:23:06Z" - latency: 853.702µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:22:06Z" - latency: 972.296µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:21:06Z" - latency: 811.437µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:20:06Z" - latency: 914.453µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:19:06Z" - latency: 984.134µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:18:06Z" - latency: 1.31964ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:17:06Z" - latency: 976.308µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:16:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T21:11:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-26-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-26.ec2.internal uid: b3ba39c0-39fb-45b9-9806-652f4f4d5b7d resourceVersion: "26289" uid: a33fdb9b-2ccb-4b20-8ed3-6e31ebc4dce7 spec: sourcePod: network-check-source-7cbc45fddc-gbl2s targetEndpoint: a38c8e1c0b5474a3c8cd2c37a631ac82-e4ba752a0888d1ac.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-18T21:17:06Z" message: 'load-balancer-api-external: tcp connection to a38c8e1c0b5474a3c8cd2c37a631ac82-e4ba752a0888d1ac.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 9.469295ms message: 'load-balancer-api-external: tcp connection to a38c8e1c0b5474a3c8cd2c37a631ac82-e4ba752a0888d1ac.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:23:06Z" - latency: 7.118526ms message: 'load-balancer-api-external: resolved host name a38c8e1c0b5474a3c8cd2c37a631ac82-e4ba752a0888d1ac.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T21:23:06Z" - latency: 5.592767ms message: 'load-balancer-api-external: tcp connection to a38c8e1c0b5474a3c8cd2c37a631ac82-e4ba752a0888d1ac.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:22:06Z" - latency: 7.482285ms message: 'load-balancer-api-external: resolved host name a38c8e1c0b5474a3c8cd2c37a631ac82-e4ba752a0888d1ac.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T21:22:06Z" - latency: 8.469197ms message: 'load-balancer-api-external: tcp connection to a38c8e1c0b5474a3c8cd2c37a631ac82-e4ba752a0888d1ac.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:21:06Z" - latency: 6.611339ms message: 'load-balancer-api-external: resolved host name a38c8e1c0b5474a3c8cd2c37a631ac82-e4ba752a0888d1ac.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T21:21:06Z" - latency: 4.978604ms message: 'load-balancer-api-external: tcp connection to a38c8e1c0b5474a3c8cd2c37a631ac82-e4ba752a0888d1ac.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:20:06Z" - latency: 9.711812ms message: 'load-balancer-api-external: resolved host name a38c8e1c0b5474a3c8cd2c37a631ac82-e4ba752a0888d1ac.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T21:20:06Z" - latency: 8.055562ms message: 'load-balancer-api-external: tcp connection to a38c8e1c0b5474a3c8cd2c37a631ac82-e4ba752a0888d1ac.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:19:06Z" - latency: 6.249449ms message: 'load-balancer-api-external: resolved host name a38c8e1c0b5474a3c8cd2c37a631ac82-e4ba752a0888d1ac.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T21:19:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T21:11:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-26-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-26.ec2.internal uid: b3ba39c0-39fb-45b9-9806-652f4f4d5b7d resourceVersion: "26288" uid: cc198f9b-858c-4466-ab3f-20037ef15d07 spec: sourcePod: network-check-source-7cbc45fddc-gbl2s targetEndpoint: a38c8e1c0b5474a3c8cd2c37a631ac82-e4ba752a0888d1ac.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-18T21:17:06Z" message: 'load-balancer-api-internal: tcp connection to a38c8e1c0b5474a3c8cd2c37a631ac82-e4ba752a0888d1ac.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 11.793055ms message: 'load-balancer-api-internal: tcp connection to a38c8e1c0b5474a3c8cd2c37a631ac82-e4ba752a0888d1ac.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:23:06Z" - latency: 7.052294ms message: 'load-balancer-api-internal: resolved host name a38c8e1c0b5474a3c8cd2c37a631ac82-e4ba752a0888d1ac.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T21:23:06Z" - latency: 5.615873ms message: 'load-balancer-api-internal: tcp connection to a38c8e1c0b5474a3c8cd2c37a631ac82-e4ba752a0888d1ac.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:22:06Z" - latency: 7.583456ms message: 'load-balancer-api-internal: resolved host name a38c8e1c0b5474a3c8cd2c37a631ac82-e4ba752a0888d1ac.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T21:22:06Z" - latency: 5.325909ms message: 'load-balancer-api-internal: tcp connection to a38c8e1c0b5474a3c8cd2c37a631ac82-e4ba752a0888d1ac.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:21:06Z" - latency: 6.466444ms message: 'load-balancer-api-internal: resolved host name a38c8e1c0b5474a3c8cd2c37a631ac82-e4ba752a0888d1ac.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T21:21:06Z" - latency: 9.014968ms message: 'load-balancer-api-internal: tcp connection to a38c8e1c0b5474a3c8cd2c37a631ac82-e4ba752a0888d1ac.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:20:06Z" - latency: 9.805771ms message: 'load-balancer-api-internal: resolved host name a38c8e1c0b5474a3c8cd2c37a631ac82-e4ba752a0888d1ac.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T21:20:06Z" - latency: 5.707154ms message: 'load-balancer-api-internal: tcp connection to a38c8e1c0b5474a3c8cd2c37a631ac82-e4ba752a0888d1ac.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:19:06Z" - latency: 6.168111ms message: 'load-balancer-api-internal: resolved host name a38c8e1c0b5474a3c8cd2c37a631ac82-e4ba752a0888d1ac.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T21:19:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T21:11:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-26-to-network-check-target-ip-10-0-129-163 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-26.ec2.internal uid: b3ba39c0-39fb-45b9-9806-652f4f4d5b7d resourceVersion: "27556" uid: c8aaf8be-e70b-4ea4-b690-3f9221622a79 spec: sourcePod: network-check-source-7cbc45fddc-gbl2s targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-18T21:18:06Z" message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.547052ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:25:06Z" - latency: 2.176421ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:24:06Z" - latency: 2.07328ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:23:06Z" - latency: 2.696997ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:22:06Z" - latency: 2.132894ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:21:06Z" - latency: 2.344884ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:20:06Z" - latency: 2.173263ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:19:06Z" - latency: 2.358763ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:18:06Z" - latency: 2.415133ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:17:06Z" - latency: 2.326562ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:16:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T21:11:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-26-to-network-check-target-ip-10-0-141-26 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-26.ec2.internal uid: b3ba39c0-39fb-45b9-9806-652f4f4d5b7d resourceVersion: "27555" uid: 30f4c384-76c5-401a-bd90-c5d043611ec1 spec: sourcePod: network-check-source-7cbc45fddc-gbl2s targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-18T21:18:06Z" message: 'network-check-target-ip-10-0-141-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.264312ms message: 'network-check-target-ip-10-0-141-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:25:06Z" - latency: 735.612µs message: 'network-check-target-ip-10-0-141-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:24:06Z" - latency: 989.697µs message: 'network-check-target-ip-10-0-141-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:23:06Z" - latency: 819.395µs message: 'network-check-target-ip-10-0-141-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:22:06Z" - latency: 1.167213ms message: 'network-check-target-ip-10-0-141-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:21:06Z" - latency: 821.314µs message: 'network-check-target-ip-10-0-141-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:20:06Z" - latency: 908.071µs message: 'network-check-target-ip-10-0-141-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:19:06Z" - latency: 1.230715ms message: 'network-check-target-ip-10-0-141-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:18:06Z" - latency: 945.91µs message: 'network-check-target-ip-10-0-141-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:17:06Z" - latency: 1.3208ms message: 'network-check-target-ip-10-0-141-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:16:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T21:11:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-26-to-network-check-target-ip-10-0-142-215 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-26.ec2.internal uid: b3ba39c0-39fb-45b9-9806-652f4f4d5b7d resourceVersion: "27557" uid: 6847d529-cf7a-44aa-947c-bafe856753d5 spec: sourcePod: network-check-source-7cbc45fddc-gbl2s targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-18T21:18:06Z" message: 'network-check-target-ip-10-0-142-215: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.506626ms message: 'network-check-target-ip-10-0-142-215: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:25:06Z" - latency: 2.14849ms message: 'network-check-target-ip-10-0-142-215: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:24:06Z" - latency: 2.676238ms message: 'network-check-target-ip-10-0-142-215: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:23:06Z" - latency: 2.111152ms message: 'network-check-target-ip-10-0-142-215: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:22:06Z" - latency: 2.337528ms message: 'network-check-target-ip-10-0-142-215: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:21:06Z" - latency: 2.403239ms message: 'network-check-target-ip-10-0-142-215: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:20:06Z" - latency: 2.290524ms message: 'network-check-target-ip-10-0-142-215: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:19:06Z" - latency: 2.222583ms message: 'network-check-target-ip-10-0-142-215: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:18:06Z" - latency: 2.708391ms message: 'network-check-target-ip-10-0-142-215: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:17:06Z" - latency: 2.293486ms message: 'network-check-target-ip-10-0-142-215: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:16:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T21:11:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-26-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-26.ec2.internal uid: b3ba39c0-39fb-45b9-9806-652f4f4d5b7d resourceVersion: "26286" uid: 0e1606a1-6b3b-4be7-b5af-53371b689cf3 spec: sourcePod: network-check-source-7cbc45fddc-gbl2s targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-18T21:17:06Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.181108ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:23:06Z" - latency: 1.612483ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T21:23:06Z" - latency: 1.15013ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:22:06Z" - latency: 1.855679ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T21:22:06Z" - latency: 901.266µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:21:06Z" - latency: 1.57041ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T21:21:06Z" - latency: 788.853µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:20:06Z" - latency: 1.729002ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T21:20:06Z" - latency: 778.255µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T21:19:06Z" - latency: 1.620189ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T21:19:06Z" kind: List metadata: resourceVersion: ""