apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T09:33:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-161-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-161.ec2.internal uid: 1111c84c-dae0-480e-8cdd-06a5342b4e6f resourceVersion: "19302" uid: f009dec5-4a7c-4254-80c2-f4d0457dcfb2 spec: sourcePod: network-check-source-6f8b768455-cgr5c targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-17T09:40:12Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 902.217µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:54:12Z" - latency: 1.023209ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:53:12Z" - latency: 920.261µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:52:12Z" - latency: 1.037514ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:51:12Z" - latency: 908.049µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:50:12Z" - latency: 1.099263ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:49:12Z" - latency: 966.882µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:48:12Z" - latency: 965.822µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:47:12Z" - latency: 1.204728ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:46:12Z" - latency: 945.527µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:45:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T09:33:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-161-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-161.ec2.internal uid: 1111c84c-dae0-480e-8cdd-06a5342b4e6f resourceVersion: "20531" uid: fd9e349b-a9f3-4f14-8058-6a029c4a71ac spec: sourcePod: network-check-source-6f8b768455-cgr5c targetEndpoint: a7606115f6f0e40cd9cdcd5c3c4172c2-e42f7ec56787f705.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T09:39:12Z" message: 'load-balancer-api-external: tcp connection to a7606115f6f0e40cd9cdcd5c3c4172c2-e42f7ec56787f705.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.615877ms message: 'load-balancer-api-external: tcp connection to a7606115f6f0e40cd9cdcd5c3c4172c2-e42f7ec56787f705.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:57:12Z" - latency: 8.967373ms message: 'load-balancer-api-external: resolved host name a7606115f6f0e40cd9cdcd5c3c4172c2-e42f7ec56787f705.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T09:57:12Z" - latency: 3.947047ms message: 'load-balancer-api-external: tcp connection to a7606115f6f0e40cd9cdcd5c3c4172c2-e42f7ec56787f705.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:56:12Z" - latency: 8.275024ms message: 'load-balancer-api-external: resolved host name a7606115f6f0e40cd9cdcd5c3c4172c2-e42f7ec56787f705.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T09:56:12Z" - latency: 3.547084ms message: 'load-balancer-api-external: tcp connection to a7606115f6f0e40cd9cdcd5c3c4172c2-e42f7ec56787f705.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:55:12Z" - latency: 7.825306ms message: 'load-balancer-api-external: resolved host name a7606115f6f0e40cd9cdcd5c3c4172c2-e42f7ec56787f705.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T09:55:12Z" - latency: 6.406022ms message: 'load-balancer-api-external: tcp connection to a7606115f6f0e40cd9cdcd5c3c4172c2-e42f7ec56787f705.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:54:12Z" - latency: 8.878964ms message: 'load-balancer-api-external: resolved host name a7606115f6f0e40cd9cdcd5c3c4172c2-e42f7ec56787f705.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T09:54:12Z" - latency: 5.697838ms message: 'load-balancer-api-external: tcp connection to a7606115f6f0e40cd9cdcd5c3c4172c2-e42f7ec56787f705.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:53:12Z" - latency: 8.476885ms message: 'load-balancer-api-external: resolved host name a7606115f6f0e40cd9cdcd5c3c4172c2-e42f7ec56787f705.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T09:53:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T09:33:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-161-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-161.ec2.internal uid: 1111c84c-dae0-480e-8cdd-06a5342b4e6f resourceVersion: "20530" uid: 5ebc918b-9509-4f38-8de3-a6a6f1aefd48 spec: sourcePod: network-check-source-6f8b768455-cgr5c targetEndpoint: a7606115f6f0e40cd9cdcd5c3c4172c2-e42f7ec56787f705.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T09:39:12Z" message: 'load-balancer-api-internal: tcp connection to a7606115f6f0e40cd9cdcd5c3c4172c2-e42f7ec56787f705.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.620478ms message: 'load-balancer-api-internal: tcp connection to a7606115f6f0e40cd9cdcd5c3c4172c2-e42f7ec56787f705.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:57:12Z" - latency: 9.006557ms message: 'load-balancer-api-internal: resolved host name a7606115f6f0e40cd9cdcd5c3c4172c2-e42f7ec56787f705.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T09:57:12Z" - latency: 3.231834ms message: 'load-balancer-api-internal: tcp connection to a7606115f6f0e40cd9cdcd5c3c4172c2-e42f7ec56787f705.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:56:12Z" - latency: 8.364032ms message: 'load-balancer-api-internal: resolved host name a7606115f6f0e40cd9cdcd5c3c4172c2-e42f7ec56787f705.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T09:56:12Z" - latency: 3.552706ms message: 'load-balancer-api-internal: tcp connection to a7606115f6f0e40cd9cdcd5c3c4172c2-e42f7ec56787f705.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:55:12Z" - latency: 7.79077ms message: 'load-balancer-api-internal: resolved host name a7606115f6f0e40cd9cdcd5c3c4172c2-e42f7ec56787f705.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T09:55:12Z" - latency: 6.447569ms message: 'load-balancer-api-internal: tcp connection to a7606115f6f0e40cd9cdcd5c3c4172c2-e42f7ec56787f705.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:54:12Z" - latency: 8.816996ms message: 'load-balancer-api-internal: resolved host name a7606115f6f0e40cd9cdcd5c3c4172c2-e42f7ec56787f705.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T09:54:12Z" - latency: 5.058192ms message: 'load-balancer-api-internal: tcp connection to a7606115f6f0e40cd9cdcd5c3c4172c2-e42f7ec56787f705.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:53:12Z" - latency: 8.372142ms message: 'load-balancer-api-internal: resolved host name a7606115f6f0e40cd9cdcd5c3c4172c2-e42f7ec56787f705.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T09:53:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T09:33:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-161-to-network-check-target-ip-10-0-135-161 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-161.ec2.internal uid: 1111c84c-dae0-480e-8cdd-06a5342b4e6f resourceVersion: "19300" uid: f5ac648c-9f00-4b18-b694-597a88beda2f spec: sourcePod: network-check-source-6f8b768455-cgr5c targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-17T09:40:12Z" message: 'network-check-target-ip-10-0-135-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.002542ms message: 'network-check-target-ip-10-0-135-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:54:12Z" - latency: 1.519728ms message: 'network-check-target-ip-10-0-135-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:53:12Z" - latency: 1.564163ms message: 'network-check-target-ip-10-0-135-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:52:12Z" - latency: 1.319211ms message: 'network-check-target-ip-10-0-135-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:51:12Z" - latency: 1.948294ms message: 'network-check-target-ip-10-0-135-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:50:12Z" - latency: 1.476168ms message: 'network-check-target-ip-10-0-135-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:49:12Z" - latency: 1.031844ms message: 'network-check-target-ip-10-0-135-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:48:12Z" - latency: 1.182254ms message: 'network-check-target-ip-10-0-135-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:47:12Z" - latency: 1.27315ms message: 'network-check-target-ip-10-0-135-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:46:12Z" - latency: 1.56065ms message: 'network-check-target-ip-10-0-135-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:45:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T09:33:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-161-to-network-check-target-ip-10-0-137-238 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-161.ec2.internal uid: 1111c84c-dae0-480e-8cdd-06a5342b4e6f resourceVersion: "19301" uid: eef6c5f7-48ff-4d2e-8663-6507ce0f886e spec: sourcePod: network-check-source-6f8b768455-cgr5c targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-17T09:40:12Z" message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.238213ms message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:54:12Z" - latency: 2.304068ms message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:53:12Z" - latency: 2.170955ms message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:52:12Z" - latency: 1.802893ms message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:51:12Z" - latency: 2.573659ms message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:50:12Z" - latency: 2.225086ms message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:49:12Z" - latency: 2.030894ms message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:48:12Z" - latency: 2.693483ms message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:47:12Z" - latency: 2.160539ms message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:46:12Z" - latency: 2.451264ms message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:45:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T09:33:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-161-to-network-check-target-ip-10-0-138-7 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-161.ec2.internal uid: 1111c84c-dae0-480e-8cdd-06a5342b4e6f resourceVersion: "19303" uid: 282db59c-12cd-42fa-93f5-0a4faa0568b4 spec: sourcePod: network-check-source-6f8b768455-cgr5c targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-17T09:40:12Z" message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.483954ms message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:54:12Z" - latency: 2.889381ms message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:53:12Z" - latency: 2.587918ms message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:52:12Z" - latency: 2.288994ms message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:51:12Z" - latency: 2.432888ms message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:50:12Z" - latency: 2.157431ms message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:49:12Z" - latency: 2.097636ms message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:48:12Z" - latency: 2.436435ms message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:47:12Z" - latency: 2.330902ms message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:46:12Z" - latency: 2.259248ms message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:45:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T09:33:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-161-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-161.ec2.internal uid: 1111c84c-dae0-480e-8cdd-06a5342b4e6f resourceVersion: "20529" uid: 70cd557b-7ce0-409a-bbb7-65d116422bfa spec: sourcePod: network-check-source-6f8b768455-cgr5c targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-17T09:39:12Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.521286ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:57:12Z" - latency: 1.881845ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T09:57:12Z" - latency: 977.713µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:56:12Z" - latency: 1.892646ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T09:56:12Z" - latency: 783.824µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:55:12Z" - latency: 2.007045ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T09:55:12Z" - latency: 1.309827ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:54:12Z" - latency: 1.824051ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T09:54:12Z" - latency: 1.06882ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T09:53:12Z" - latency: 1.830338ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T09:53:12Z" kind: List metadata: resourceVersion: ""