apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T17:59:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-113-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-113.ec2.internal uid: 3434b1fc-ce0d-4dd3-b580-f02d54ad05a4 resourceVersion: "32129" uid: 831a1bda-d7ef-4772-830a-d587fdbf23c2 spec: sourcePod: network-check-source-7cbc45fddc-6bppp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-17T18:06:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.285931ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:41:57Z" - latency: 1.157249ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:40:57Z" - latency: 1.593462ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:39:57Z" - latency: 1.048938ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:38:57Z" - latency: 838.919µ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:57Z" - latency: 1.840654ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:36:57Z" - latency: 1.211257ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:35:57Z" - latency: 1.071112ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:34:57Z" - latency: 1.262873ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:33:57Z" - latency: 1.358544ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:32:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T17:59:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-113-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-113.ec2.internal uid: 3434b1fc-ce0d-4dd3-b580-f02d54ad05a4 resourceVersion: "32130" uid: 40b024ba-146d-4f07-9e2c-eec415b15e88 spec: sourcePod: network-check-source-7cbc45fddc-6bppp targetEndpoint: a338b3205f22c47af8a435a9c9770373-468d666c2389c575.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T18:05:57Z" message: 'load-balancer-api-external: tcp connection to a338b3205f22c47af8a435a9c9770373-468d666c2389c575.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.027664ms message: 'load-balancer-api-external: tcp connection to a338b3205f22c47af8a435a9c9770373-468d666c2389c575.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:41:57Z" - latency: 8.032846ms message: 'load-balancer-api-external: resolved host name a338b3205f22c47af8a435a9c9770373-468d666c2389c575.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:41:57Z" - latency: 5.758547ms message: 'load-balancer-api-external: tcp connection to a338b3205f22c47af8a435a9c9770373-468d666c2389c575.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:40:57Z" - latency: 8.214395ms message: 'load-balancer-api-external: resolved host name a338b3205f22c47af8a435a9c9770373-468d666c2389c575.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:40:57Z" - latency: 4.818292ms message: 'load-balancer-api-external: tcp connection to a338b3205f22c47af8a435a9c9770373-468d666c2389c575.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:39:57Z" - latency: 7.015196ms message: 'load-balancer-api-external: resolved host name a338b3205f22c47af8a435a9c9770373-468d666c2389c575.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:39:57Z" - latency: 4.837388ms message: 'load-balancer-api-external: tcp connection to a338b3205f22c47af8a435a9c9770373-468d666c2389c575.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:38:57Z" - latency: 7.909626ms message: 'load-balancer-api-external: resolved host name a338b3205f22c47af8a435a9c9770373-468d666c2389c575.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:38:57Z" - latency: 5.132465ms message: 'load-balancer-api-external: tcp connection to a338b3205f22c47af8a435a9c9770373-468d666c2389c575.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:37:57Z" - latency: 7.077957ms message: 'load-balancer-api-external: resolved host name a338b3205f22c47af8a435a9c9770373-468d666c2389c575.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:37:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T17:59:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-113-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-113.ec2.internal uid: 3434b1fc-ce0d-4dd3-b580-f02d54ad05a4 resourceVersion: "32131" uid: 62918771-38bc-423f-b908-93f0d2e25869 spec: sourcePod: network-check-source-7cbc45fddc-6bppp targetEndpoint: a338b3205f22c47af8a435a9c9770373-468d666c2389c575.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T18:05:57Z" message: 'load-balancer-api-internal: tcp connection to a338b3205f22c47af8a435a9c9770373-468d666c2389c575.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.044006ms message: 'load-balancer-api-internal: tcp connection to a338b3205f22c47af8a435a9c9770373-468d666c2389c575.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:41:57Z" - latency: 8.096198ms message: 'load-balancer-api-internal: resolved host name a338b3205f22c47af8a435a9c9770373-468d666c2389c575.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:41:57Z" - latency: 5.753518ms message: 'load-balancer-api-internal: tcp connection to a338b3205f22c47af8a435a9c9770373-468d666c2389c575.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:40:57Z" - latency: 8.368382ms message: 'load-balancer-api-internal: resolved host name a338b3205f22c47af8a435a9c9770373-468d666c2389c575.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:40:57Z" - latency: 4.839499ms message: 'load-balancer-api-internal: tcp connection to a338b3205f22c47af8a435a9c9770373-468d666c2389c575.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:39:57Z" - latency: 7.126866ms message: 'load-balancer-api-internal: resolved host name a338b3205f22c47af8a435a9c9770373-468d666c2389c575.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:39:57Z" - latency: 4.853796ms message: 'load-balancer-api-internal: tcp connection to a338b3205f22c47af8a435a9c9770373-468d666c2389c575.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:38:57Z" - latency: 7.972808ms message: 'load-balancer-api-internal: resolved host name a338b3205f22c47af8a435a9c9770373-468d666c2389c575.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:38:57Z" - latency: 5.102453ms message: 'load-balancer-api-internal: tcp connection to a338b3205f22c47af8a435a9c9770373-468d666c2389c575.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:37:57Z" - latency: 7.149137ms message: 'load-balancer-api-internal: resolved host name a338b3205f22c47af8a435a9c9770373-468d666c2389c575.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T18:37:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T17:59:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-113-to-network-check-target-ip-10-0-133-113 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-113.ec2.internal uid: 3434b1fc-ce0d-4dd3-b580-f02d54ad05a4 resourceVersion: "32125" uid: fe2b86ae-95af-40bc-bd78-95f7fb928865 spec: sourcePod: network-check-source-7cbc45fddc-6bppp targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-17T18:06:57Z" message: 'network-check-target-ip-10-0-133-113: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.65708ms message: 'network-check-target-ip-10-0-133-113: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:41:57Z" - latency: 1.677397ms message: 'network-check-target-ip-10-0-133-113: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:40:57Z" - latency: 1.687537ms message: 'network-check-target-ip-10-0-133-113: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:39:57Z" - latency: 1.00841ms message: 'network-check-target-ip-10-0-133-113: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:38:57Z" - latency: 1.668763ms message: 'network-check-target-ip-10-0-133-113: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:37:57Z" - latency: 998.604µs message: 'network-check-target-ip-10-0-133-113: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:36:57Z" - latency: 885.841µs message: 'network-check-target-ip-10-0-133-113: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:35:57Z" - latency: 1.188504ms message: 'network-check-target-ip-10-0-133-113: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:34:57Z" - latency: 1.002417ms message: 'network-check-target-ip-10-0-133-113: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:33:57Z" - latency: 1.094692ms message: 'network-check-target-ip-10-0-133-113: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:32:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T17:59:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-113-to-network-check-target-ip-10-0-135-193 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-113.ec2.internal uid: 3434b1fc-ce0d-4dd3-b580-f02d54ad05a4 resourceVersion: "32127" uid: df9164de-39c8-4f54-a049-3062eef41384 spec: sourcePod: network-check-source-7cbc45fddc-6bppp targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-17T18:06:57Z" message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.52505ms message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:41:57Z" - latency: 2.371227ms message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:40:57Z" - latency: 2.648346ms message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:39:57Z" - latency: 2.346171ms message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:38:57Z" - latency: 2.379773ms message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:37:57Z" - latency: 2.167811ms message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:36:57Z" - latency: 2.521641ms message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:35:57Z" - latency: 2.238305ms message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:34:57Z" - latency: 2.142239ms message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:33:57Z" - latency: 2.31929ms message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:32:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T17:59:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-113-to-network-check-target-ip-10-0-135-240 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-113.ec2.internal uid: 3434b1fc-ce0d-4dd3-b580-f02d54ad05a4 resourceVersion: "32126" uid: f70a0c69-f662-42a0-908c-36140f6d5f49 spec: sourcePod: network-check-source-7cbc45fddc-6bppp targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-17T18:06:57Z" message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.630036ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:41:57Z" - latency: 2.385627ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:40:57Z" - latency: 2.224454ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:39:57Z" - latency: 2.24819ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:38:57Z" - latency: 2.336639ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:37:57Z" - latency: 2.441789ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:36:57Z" - latency: 2.460631ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:35:57Z" - latency: 2.256641ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:34:57Z" - latency: 2.179639ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:33:57Z" - latency: 2.567874ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:32:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T17:59:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-113-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-113.ec2.internal uid: 3434b1fc-ce0d-4dd3-b580-f02d54ad05a4 resourceVersion: "32128" uid: fc4809a7-a4da-43ef-b76a-b9987b580dfa spec: sourcePod: network-check-source-7cbc45fddc-6bppp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-17T18:05:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.409474ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:41:57Z" - latency: 2.191171ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T18:41:57Z" - latency: 1.239058ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:40:57Z" - latency: 2.302744ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T18:40:57Z" - latency: 1.226927ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:39:57Z" - latency: 1.920179ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T18:39:57Z" - latency: 1.35192ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:38:57Z" - latency: 2.42528ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T18:38:57Z" - latency: 1.058592ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T18:37:57Z" - latency: 1.838127ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T18:37:57Z" kind: List metadata: resourceVersion: ""