apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T16:19:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-166-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-166.ec2.internal uid: cfb4290d-e9be-43c8-b2db-ac21c87dd676 resourceVersion: "62649" uid: 712102a9-2bc6-48c2-8744-5a11e71d483e spec: sourcePod: network-check-source-7bc5b6bf85-m8xxx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-23T16:26: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.143569ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T17:01:57Z" - latency: 1.275379ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T17:00:57Z" - latency: 1.173023ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:59:57Z" - latency: 1.19349ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:58:57Z" - latency: 960.914µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:57:57Z" - latency: 1.161749ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:56:57Z" - latency: 1.205439ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:55:57Z" - latency: 1.088188ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:54:57Z" - latency: 1.055887ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:53:57Z" - latency: 1.400594ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:52:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T16:19:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-166-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-166.ec2.internal uid: cfb4290d-e9be-43c8-b2db-ac21c87dd676 resourceVersion: "62650" uid: 901e60ae-ae3a-44d8-ab12-01321bf4a65f spec: sourcePod: network-check-source-7bc5b6bf85-m8xxx targetEndpoint: ad9622138bb9f4e638b292031e82224e-450753a15becb81c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T16:25:57Z" message: 'load-balancer-api-external: tcp connection to ad9622138bb9f4e638b292031e82224e-450753a15becb81c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.369425ms message: 'load-balancer-api-external: tcp connection to ad9622138bb9f4e638b292031e82224e-450753a15becb81c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T17:01:57Z" - latency: 8.730134ms message: 'load-balancer-api-external: resolved host name ad9622138bb9f4e638b292031e82224e-450753a15becb81c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T17:01:57Z" - latency: 5.460585ms message: 'load-balancer-api-external: tcp connection to ad9622138bb9f4e638b292031e82224e-450753a15becb81c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T17:00:57Z" - latency: 7.620719ms message: 'load-balancer-api-external: resolved host name ad9622138bb9f4e638b292031e82224e-450753a15becb81c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T17:00:57Z" - latency: 4.907377ms message: 'load-balancer-api-external: tcp connection to ad9622138bb9f4e638b292031e82224e-450753a15becb81c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:59:57Z" - latency: 5.799086ms message: 'load-balancer-api-external: resolved host name ad9622138bb9f4e638b292031e82224e-450753a15becb81c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T16:59:57Z" - latency: 4.290047ms message: 'load-balancer-api-external: tcp connection to ad9622138bb9f4e638b292031e82224e-450753a15becb81c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:58:57Z" - latency: 6.857967ms message: 'load-balancer-api-external: resolved host name ad9622138bb9f4e638b292031e82224e-450753a15becb81c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T16:58:57Z" - latency: 4.3771ms message: 'load-balancer-api-external: tcp connection to ad9622138bb9f4e638b292031e82224e-450753a15becb81c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:57:57Z" - latency: 7.573284ms message: 'load-balancer-api-external: resolved host name ad9622138bb9f4e638b292031e82224e-450753a15becb81c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T16:57:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T16:19:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-166-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-166.ec2.internal uid: cfb4290d-e9be-43c8-b2db-ac21c87dd676 resourceVersion: "62651" uid: feb57d76-a553-49fc-91a6-ed8cbef2664b spec: sourcePod: network-check-source-7bc5b6bf85-m8xxx targetEndpoint: ad9622138bb9f4e638b292031e82224e-450753a15becb81c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T16:25:57Z" message: 'load-balancer-api-internal: tcp connection to ad9622138bb9f4e638b292031e82224e-450753a15becb81c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.330911ms message: 'load-balancer-api-internal: tcp connection to ad9622138bb9f4e638b292031e82224e-450753a15becb81c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T17:01:57Z" - latency: 8.752206ms message: 'load-balancer-api-internal: resolved host name ad9622138bb9f4e638b292031e82224e-450753a15becb81c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T17:01:57Z" - latency: 4.831174ms message: 'load-balancer-api-internal: tcp connection to ad9622138bb9f4e638b292031e82224e-450753a15becb81c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T17:00:57Z" - latency: 7.67882ms message: 'load-balancer-api-internal: resolved host name ad9622138bb9f4e638b292031e82224e-450753a15becb81c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T17:00:57Z" - latency: 3.923553ms message: 'load-balancer-api-internal: tcp connection to ad9622138bb9f4e638b292031e82224e-450753a15becb81c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:59:57Z" - latency: 5.876164ms message: 'load-balancer-api-internal: resolved host name ad9622138bb9f4e638b292031e82224e-450753a15becb81c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T16:59:57Z" - latency: 4.304042ms message: 'load-balancer-api-internal: tcp connection to ad9622138bb9f4e638b292031e82224e-450753a15becb81c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:58:57Z" - latency: 6.922287ms message: 'load-balancer-api-internal: resolved host name ad9622138bb9f4e638b292031e82224e-450753a15becb81c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T16:58:57Z" - latency: 4.334349ms message: 'load-balancer-api-internal: tcp connection to ad9622138bb9f4e638b292031e82224e-450753a15becb81c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:57:57Z" - latency: 7.554197ms message: 'load-balancer-api-internal: resolved host name ad9622138bb9f4e638b292031e82224e-450753a15becb81c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T16:57:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T16:19:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-166-to-network-check-target-ip-10-0-131-182 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-166.ec2.internal uid: cfb4290d-e9be-43c8-b2db-ac21c87dd676 resourceVersion: "62646" uid: 9d78b5a0-0369-48df-b64c-aa4551195e64 spec: sourcePod: network-check-source-7bc5b6bf85-m8xxx targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-23T16:26:57Z" message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.20782ms message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T17:01:57Z" - latency: 1.999036ms message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T17:00:57Z" - latency: 2.040662ms message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:59:57Z" - latency: 1.962887ms message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:58:57Z" - latency: 1.779796ms message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:57:57Z" - latency: 1.910848ms message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:56:57Z" - latency: 2.023966ms message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:55:57Z" - latency: 2.139622ms message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:54:57Z" - latency: 1.954551ms message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:53:57Z" - latency: 1.958783ms message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:52:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T16:19:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-166-to-network-check-target-ip-10-0-138-199 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-166.ec2.internal uid: cfb4290d-e9be-43c8-b2db-ac21c87dd676 resourceVersion: "62645" uid: 287ea290-8a6f-4ead-bb10-26edaa2f0e53 spec: sourcePod: network-check-source-7bc5b6bf85-m8xxx targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-23T16:26:57Z" message: 'network-check-target-ip-10-0-138-199: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.362076ms message: 'network-check-target-ip-10-0-138-199: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T17:01:57Z" - latency: 2.282042ms message: 'network-check-target-ip-10-0-138-199: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T17:00:57Z" - latency: 2.42416ms message: 'network-check-target-ip-10-0-138-199: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:59:57Z" - latency: 2.551067ms message: 'network-check-target-ip-10-0-138-199: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:58:57Z" - latency: 2.160248ms message: 'network-check-target-ip-10-0-138-199: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:57:57Z" - latency: 2.232631ms message: 'network-check-target-ip-10-0-138-199: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:56:57Z" - latency: 2.085901ms message: 'network-check-target-ip-10-0-138-199: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:55:57Z" - latency: 2.180704ms message: 'network-check-target-ip-10-0-138-199: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:54:57Z" - latency: 2.296485ms message: 'network-check-target-ip-10-0-138-199: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:53:57Z" - latency: 7.072ms message: 'network-check-target-ip-10-0-138-199: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:52:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T16:19:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-166-to-network-check-target-ip-10-0-143-166 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-166.ec2.internal uid: cfb4290d-e9be-43c8-b2db-ac21c87dd676 resourceVersion: "62648" uid: 978da3a0-3146-4c32-95be-2931835653ae spec: sourcePod: network-check-source-7bc5b6bf85-m8xxx targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-23T16:26:57Z" message: 'network-check-target-ip-10-0-143-166: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.426739ms message: 'network-check-target-ip-10-0-143-166: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T17:01:57Z" - latency: 976.91µs message: 'network-check-target-ip-10-0-143-166: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T17:00:57Z" - latency: 920.522µs message: 'network-check-target-ip-10-0-143-166: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:59:57Z" - latency: 934.163µs message: 'network-check-target-ip-10-0-143-166: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:58:57Z" - latency: 977.286µs message: 'network-check-target-ip-10-0-143-166: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:57:57Z" - latency: 2.526317ms message: 'network-check-target-ip-10-0-143-166: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:56:57Z" - latency: 1.369024ms message: 'network-check-target-ip-10-0-143-166: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:55:57Z" - latency: 1.145412ms message: 'network-check-target-ip-10-0-143-166: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:54:57Z" - latency: 953.272µs message: 'network-check-target-ip-10-0-143-166: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:53:57Z" - latency: 1.041415ms message: 'network-check-target-ip-10-0-143-166: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:52:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T16:19:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-166-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-166.ec2.internal uid: cfb4290d-e9be-43c8-b2db-ac21c87dd676 resourceVersion: "62647" uid: e4016f4c-05db-4e6e-aa30-d4798f2db38e spec: sourcePod: network-check-source-7bc5b6bf85-m8xxx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-23T16:25:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.014438ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T17:01:57Z" - latency: 2.287718ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T17:01:57Z" - latency: 864.017µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T17:00:57Z" - latency: 1.671908ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T17:00:57Z" - latency: 784.024µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:59:57Z" - latency: 1.644166ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T16:59:57Z" - latency: 905.035µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:58:57Z" - latency: 1.812871ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T16:58:57Z" - latency: 820.622µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:57:57Z" - latency: 2.393623ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T16:57:57Z" kind: List metadata: resourceVersion: ""