apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T18:06:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-138-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-138.ec2.internal uid: 1014ddbd-ffc2-4648-bc0d-0e9a7c29b538 resourceVersion: "67293" uid: e3e7f53d-646c-42f0-abed-fb2406aecf1c spec: sourcePod: network-check-source-7cbc45fddc-pgpj7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-17T18:13:30Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.141334ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:41:30Z" - latency: 868.025µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:40:30Z" - latency: 908.184µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:39:30Z" - latency: 869.478µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:38:30Z" - latency: 887.053µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:37:30Z" - latency: 1.023418ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:36:30Z" - latency: 997.11µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:35:30Z" - latency: 977.338µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:34:30Z" - latency: 1.00759ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:33:30Z" - latency: 851.588µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:32:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T18:06:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-138-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-138.ec2.internal uid: 1014ddbd-ffc2-4648-bc0d-0e9a7c29b538 resourceVersion: "68143" uid: 4fa30a08-947d-4254-bfbe-edad1bb152f8 spec: sourcePod: network-check-source-7cbc45fddc-pgpj7 targetEndpoint: a3ca4da8cfff241c79609974dbcf0f24-cdf372b3ca39d264.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T18:12:30Z" message: 'load-balancer-api-external: tcp connection to a3ca4da8cfff241c79609974dbcf0f24-cdf372b3ca39d264.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.510748ms message: 'load-balancer-api-external: tcp connection to a3ca4da8cfff241c79609974dbcf0f24-cdf372b3ca39d264.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:42:30Z" - latency: 8.127893ms message: 'load-balancer-api-external: resolved host name a3ca4da8cfff241c79609974dbcf0f24-cdf372b3ca39d264.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:42:30Z" - latency: 4.302614ms message: 'load-balancer-api-external: tcp connection to a3ca4da8cfff241c79609974dbcf0f24-cdf372b3ca39d264.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:41:30Z" - latency: 7.701432ms message: 'load-balancer-api-external: resolved host name a3ca4da8cfff241c79609974dbcf0f24-cdf372b3ca39d264.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:41:30Z" - latency: 5.777435ms message: 'load-balancer-api-external: tcp connection to a3ca4da8cfff241c79609974dbcf0f24-cdf372b3ca39d264.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:40:30Z" - latency: 7.664625ms message: 'load-balancer-api-external: resolved host name a3ca4da8cfff241c79609974dbcf0f24-cdf372b3ca39d264.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:40:30Z" - latency: 4.138248ms message: 'load-balancer-api-external: tcp connection to a3ca4da8cfff241c79609974dbcf0f24-cdf372b3ca39d264.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:39:30Z" - latency: 6.702546ms message: 'load-balancer-api-external: resolved host name a3ca4da8cfff241c79609974dbcf0f24-cdf372b3ca39d264.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:39:30Z" - latency: 4.560929ms message: 'load-balancer-api-external: tcp connection to a3ca4da8cfff241c79609974dbcf0f24-cdf372b3ca39d264.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:38:30Z" - latency: 7.948115ms message: 'load-balancer-api-external: resolved host name a3ca4da8cfff241c79609974dbcf0f24-cdf372b3ca39d264.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:38:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T18:06:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-138-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-138.ec2.internal uid: 1014ddbd-ffc2-4648-bc0d-0e9a7c29b538 resourceVersion: "68144" uid: c49ac0a3-c65d-403f-9028-7317ad0c8956 spec: sourcePod: network-check-source-7cbc45fddc-pgpj7 targetEndpoint: a3ca4da8cfff241c79609974dbcf0f24-cdf372b3ca39d264.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T18:12:30Z" message: 'load-balancer-api-internal: tcp connection to a3ca4da8cfff241c79609974dbcf0f24-cdf372b3ca39d264.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.60894ms message: 'load-balancer-api-internal: tcp connection to a3ca4da8cfff241c79609974dbcf0f24-cdf372b3ca39d264.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:42:30Z" - latency: 8.178247ms message: 'load-balancer-api-internal: resolved host name a3ca4da8cfff241c79609974dbcf0f24-cdf372b3ca39d264.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:42:30Z" - latency: 4.777276ms message: 'load-balancer-api-internal: tcp connection to a3ca4da8cfff241c79609974dbcf0f24-cdf372b3ca39d264.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:41:30Z" - latency: 7.808105ms message: 'load-balancer-api-internal: resolved host name a3ca4da8cfff241c79609974dbcf0f24-cdf372b3ca39d264.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:41:30Z" - latency: 5.816285ms message: 'load-balancer-api-internal: tcp connection to a3ca4da8cfff241c79609974dbcf0f24-cdf372b3ca39d264.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:40:30Z" - latency: 7.629579ms message: 'load-balancer-api-internal: resolved host name a3ca4da8cfff241c79609974dbcf0f24-cdf372b3ca39d264.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:40:30Z" - latency: 4.149823ms message: 'load-balancer-api-internal: tcp connection to a3ca4da8cfff241c79609974dbcf0f24-cdf372b3ca39d264.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:39:30Z" - latency: 6.589119ms message: 'load-balancer-api-internal: resolved host name a3ca4da8cfff241c79609974dbcf0f24-cdf372b3ca39d264.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:39:30Z" - latency: 4.588991ms message: 'load-balancer-api-internal: tcp connection to a3ca4da8cfff241c79609974dbcf0f24-cdf372b3ca39d264.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:38:30Z" - latency: 7.961027ms message: 'load-balancer-api-internal: resolved host name a3ca4da8cfff241c79609974dbcf0f24-cdf372b3ca39d264.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:38:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T18:06:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-138-to-network-check-target-ip-10-0-137-104 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-138.ec2.internal uid: 1014ddbd-ffc2-4648-bc0d-0e9a7c29b538 resourceVersion: "67292" uid: acc99429-0bdd-4531-ab4d-2b0da1c0cf86 spec: sourcePod: network-check-source-7cbc45fddc-pgpj7 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-17T18:13:30Z" message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.919361ms message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:41:30Z" - latency: 2.506091ms message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:40:30Z" - latency: 2.493567ms message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:39:30Z" - latency: 2.361747ms message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:38:30Z" - latency: 2.320112ms message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:37:30Z" - latency: 2.811738ms message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:36:30Z" - latency: 2.385982ms message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:35:30Z" - latency: 2.829664ms message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:34:30Z" - latency: 2.21921ms message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:33:30Z" - latency: 2.214833ms message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:32:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T18:06:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-138-to-network-check-target-ip-10-0-138-138 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-138.ec2.internal uid: 1014ddbd-ffc2-4648-bc0d-0e9a7c29b538 resourceVersion: "67290" uid: c55efbaf-a3c2-42be-8daa-729ea26db618 spec: sourcePod: network-check-source-7cbc45fddc-pgpj7 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-17T18:13:30Z" message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.469388ms message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:41:30Z" - latency: 904.898µs message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:40:30Z" - latency: 1.096686ms message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:39:30Z" - latency: 938.522µs message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:38:30Z" - latency: 1.406343ms message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:37:30Z" - latency: 1.641805ms message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:36:30Z" - latency: 783.319µs message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:35:30Z" - latency: 1.189838ms message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:34:30Z" - latency: 1.892776ms message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:33:30Z" - latency: 1.478112ms message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:32:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T18:06:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-138-to-network-check-target-ip-10-0-142-105 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-138.ec2.internal uid: 1014ddbd-ffc2-4648-bc0d-0e9a7c29b538 resourceVersion: "67291" uid: f322abeb-3c0a-455b-bdaa-8c32d415ebe4 spec: sourcePod: network-check-source-7cbc45fddc-pgpj7 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-17T18:13:30Z" message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.483889ms message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:41:30Z" - latency: 2.437753ms message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:40:30Z" - latency: 2.246069ms message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:39:30Z" - latency: 2.346311ms message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:38:30Z" - latency: 2.108519ms message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:37:30Z" - latency: 2.622462ms message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:36:30Z" - latency: 2.36588ms message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:35:30Z" - latency: 2.299426ms message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:34:30Z" - latency: 2.095264ms message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:33:30Z" - latency: 2.238786ms message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:32:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T18:06:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-138-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-138.ec2.internal uid: 1014ddbd-ffc2-4648-bc0d-0e9a7c29b538 resourceVersion: "68142" uid: 0490c8bc-4dfc-436d-9ef3-4f2358a443e1 spec: sourcePod: network-check-source-7cbc45fddc-pgpj7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-17T18:12:30Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.108721ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:42:30Z" - latency: 2.311504ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T18:42:30Z" - latency: 1.188971ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:41:30Z" - latency: 2.557026ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T18:41:30Z" - latency: 828.159µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:40:30Z" - latency: 1.645364ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T18:40:30Z" - latency: 1.068218ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:39:30Z" - latency: 1.905682ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T18:39:30Z" - latency: 851.336µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:38:30Z" - latency: 1.725431ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T18:38:30Z" kind: List metadata: resourceVersion: ""