apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T22:23:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-148-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-148.us-east-2.compute.internal uid: 71ac56ab-11d7-43e5-860f-14527106bdf5 resourceVersion: "122351" uid: 63b98030-3160-404c-9c2e-6f912fddfc12 spec: sourcePod: network-check-source-6f78d59f99-4gg4t targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-01T22:30:42Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.009834ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:12:42Z" - latency: 1.25652ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:11:42Z" - latency: 4.231183ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:10:42Z" - latency: 1.039672ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:09:42Z" - latency: 1.384437ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:08:42Z" - latency: 1.500575ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:07:42Z" - latency: 1.085014ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:06:42Z" - latency: 1.003415ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:05:42Z" - latency: 1.20726ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:04:42Z" - latency: 1.253985ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:03:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T22:23:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-148-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-148.us-east-2.compute.internal uid: 71ac56ab-11d7-43e5-860f-14527106bdf5 resourceVersion: "121810" uid: 3a02bf1e-18b9-4e55-89f7-8decbdf3f39e spec: sourcePod: network-check-source-6f78d59f99-4gg4t targetEndpoint: a077b489d192b45a5b23110ceb1ff204-b74fce3ba89a9b64.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-01T22:29:42Z" message: 'load-balancer-api-external: tcp connection to a077b489d192b45a5b23110ceb1ff204-b74fce3ba89a9b64.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.564626ms message: 'load-balancer-api-external: tcp connection to a077b489d192b45a5b23110ceb1ff204-b74fce3ba89a9b64.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:11:42Z" - latency: 7.048115ms message: 'load-balancer-api-external: resolved host name a077b489d192b45a5b23110ceb1ff204-b74fce3ba89a9b64.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T23:11:42Z" - latency: 5.92664ms message: 'load-balancer-api-external: tcp connection to a077b489d192b45a5b23110ceb1ff204-b74fce3ba89a9b64.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:10:42Z" - latency: 48.199544ms message: 'load-balancer-api-external: resolved host name a077b489d192b45a5b23110ceb1ff204-b74fce3ba89a9b64.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T23:10:42Z" - latency: 7.304584ms message: 'load-balancer-api-external: tcp connection to a077b489d192b45a5b23110ceb1ff204-b74fce3ba89a9b64.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:09:42Z" - latency: 9.675754ms message: 'load-balancer-api-external: resolved host name a077b489d192b45a5b23110ceb1ff204-b74fce3ba89a9b64.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T23:09:42Z" - latency: 6.005702ms message: 'load-balancer-api-external: tcp connection to a077b489d192b45a5b23110ceb1ff204-b74fce3ba89a9b64.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:08:42Z" - latency: 7.728595ms message: 'load-balancer-api-external: resolved host name a077b489d192b45a5b23110ceb1ff204-b74fce3ba89a9b64.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T23:08:42Z" - latency: 5.84373ms message: 'load-balancer-api-external: tcp connection to a077b489d192b45a5b23110ceb1ff204-b74fce3ba89a9b64.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:07:42Z" - latency: 6.996811ms message: 'load-balancer-api-external: resolved host name a077b489d192b45a5b23110ceb1ff204-b74fce3ba89a9b64.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T23:07:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T22:23:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-148-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-148.us-east-2.compute.internal uid: 71ac56ab-11d7-43e5-860f-14527106bdf5 resourceVersion: "121809" uid: 46c19d9d-7c34-4c39-8cdb-d3ce6c5d4748 spec: sourcePod: network-check-source-6f78d59f99-4gg4t targetEndpoint: a077b489d192b45a5b23110ceb1ff204-b74fce3ba89a9b64.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-01T22:29:42Z" message: 'load-balancer-api-internal: tcp connection to a077b489d192b45a5b23110ceb1ff204-b74fce3ba89a9b64.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.592374ms message: 'load-balancer-api-internal: tcp connection to a077b489d192b45a5b23110ceb1ff204-b74fce3ba89a9b64.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:11:42Z" - latency: 6.993248ms message: 'load-balancer-api-internal: resolved host name a077b489d192b45a5b23110ceb1ff204-b74fce3ba89a9b64.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T23:11:42Z" - latency: 7.45366ms message: 'load-balancer-api-internal: tcp connection to a077b489d192b45a5b23110ceb1ff204-b74fce3ba89a9b64.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:10:42Z" - latency: 47.275116ms message: 'load-balancer-api-internal: resolved host name a077b489d192b45a5b23110ceb1ff204-b74fce3ba89a9b64.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T23:10:42Z" - latency: 7.362278ms message: 'load-balancer-api-internal: tcp connection to a077b489d192b45a5b23110ceb1ff204-b74fce3ba89a9b64.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:09:42Z" - latency: 9.697248ms message: 'load-balancer-api-internal: resolved host name a077b489d192b45a5b23110ceb1ff204-b74fce3ba89a9b64.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T23:09:42Z" - latency: 5.318864ms message: 'load-balancer-api-internal: tcp connection to a077b489d192b45a5b23110ceb1ff204-b74fce3ba89a9b64.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:08:42Z" - latency: 7.672415ms message: 'load-balancer-api-internal: resolved host name a077b489d192b45a5b23110ceb1ff204-b74fce3ba89a9b64.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T23:08:42Z" - latency: 4.691766ms message: 'load-balancer-api-internal: tcp connection to a077b489d192b45a5b23110ceb1ff204-b74fce3ba89a9b64.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:07:42Z" - latency: 6.908581ms message: 'load-balancer-api-internal: resolved host name a077b489d192b45a5b23110ceb1ff204-b74fce3ba89a9b64.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T23:07:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T22:23:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-148-to-network-check-target-ip-10-0-128-55 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-148.us-east-2.compute.internal uid: 71ac56ab-11d7-43e5-860f-14527106bdf5 resourceVersion: "122378" uid: 86ece0bd-0b97-48c8-ae19-57f276a6660d spec: sourcePod: network-check-source-6f78d59f99-4gg4t targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-01T22:30:45Z" message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.046378ms message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:12:45Z" - latency: 1.126385ms message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:11:45Z" - latency: 1.141721ms message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:10:45Z" - latency: 1.804518ms message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:09:45Z" - latency: 1.411093ms message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:08:45Z" - latency: 2.279043ms message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:07:45Z" - latency: 2.262888ms message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:06:45Z" - latency: 1.005507ms message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:05:45Z" - latency: 5.135241ms message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:04:45Z" - latency: 2.252481ms message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:03:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T22:23:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-148-to-network-check-target-ip-10-0-134-88 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-148.us-east-2.compute.internal uid: 71ac56ab-11d7-43e5-860f-14527106bdf5 resourceVersion: "122426" uid: 9dcec04d-8d2e-45f7-8911-e171baff991f spec: sourcePod: network-check-source-6f78d59f99-4gg4t targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-01T22:30:50Z" message: 'network-check-target-ip-10-0-134-88: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.708863ms message: 'network-check-target-ip-10-0-134-88: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:12:50Z" - latency: 2.3183ms message: 'network-check-target-ip-10-0-134-88: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:11:50Z" - latency: 2.686826ms message: 'network-check-target-ip-10-0-134-88: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:10:50Z" - latency: 2.502636ms message: 'network-check-target-ip-10-0-134-88: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:09:50Z" - latency: 2.470479ms message: 'network-check-target-ip-10-0-134-88: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:08:50Z" - latency: 1.003416ms message: 'network-check-target-ip-10-0-134-88: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:07:50Z" - latency: 13.513718ms message: 'network-check-target-ip-10-0-134-88: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:06:50Z" - latency: 2.594662ms message: 'network-check-target-ip-10-0-134-88: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:05:50Z" - latency: 2.697139ms message: 'network-check-target-ip-10-0-134-88: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:04:50Z" - latency: 2.538813ms message: 'network-check-target-ip-10-0-134-88: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:03:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T22:23:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-148-to-network-check-target-ip-10-0-141-148 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-148.us-east-2.compute.internal uid: 71ac56ab-11d7-43e5-860f-14527106bdf5 resourceVersion: "122350" uid: b7f59cb5-2d26-4278-85ed-224c625f0c05 spec: sourcePod: network-check-source-6f78d59f99-4gg4t targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-01T22:30:42Z" message: 'network-check-target-ip-10-0-141-148: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.394345ms message: 'network-check-target-ip-10-0-141-148: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:12:42Z" - latency: 1.75588ms message: 'network-check-target-ip-10-0-141-148: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:11:42Z" - latency: 4.754534ms message: 'network-check-target-ip-10-0-141-148: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:10:42Z" - latency: 1.690763ms message: 'network-check-target-ip-10-0-141-148: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:09:42Z" - latency: 1.980187ms message: 'network-check-target-ip-10-0-141-148: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:08:42Z" - latency: 1.863668ms message: 'network-check-target-ip-10-0-141-148: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:07:42Z" - latency: 1.508083ms message: 'network-check-target-ip-10-0-141-148: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:06:42Z" - latency: 1.3278ms message: 'network-check-target-ip-10-0-141-148: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:05:42Z" - latency: 1.579449ms message: 'network-check-target-ip-10-0-141-148: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:04:42Z" - latency: 1.070274ms message: 'network-check-target-ip-10-0-141-148: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:03:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T22:23:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-148-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-148.us-east-2.compute.internal uid: 71ac56ab-11d7-43e5-860f-14527106bdf5 resourceVersion: "121808" uid: 1501070d-5cb3-4709-bb8b-5873036dc53f spec: sourcePod: network-check-source-6f78d59f99-4gg4t targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-01T22:29:42Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.161133ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:11:42Z" - latency: 1.845588ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T23:11:42Z" - latency: 8.136844ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:10:42Z" - latency: 19.032486ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T23:10:42Z" - latency: 881.007µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:09:42Z" - latency: 1.855774ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T23:09:42Z" - latency: 1.926627ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:08:42Z" - latency: 2.205482ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T23:08:42Z" - latency: 2.422779ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T23:07:42Z" - latency: 1.997991ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T23:07:42Z" kind: List metadata: resourceVersion: ""