apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T02:00:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-8-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-8.ec2.internal uid: 28c1c80b-a94a-4127-8041-c2b24cad9b2f resourceVersion: "63393" uid: e6723d88-6f78-4b38-844a-df891270beca spec: sourcePod: network-check-source-7bc5b6bf85-xk5l2 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-18T02:07:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.300292ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:42:22Z" - latency: 1.043828ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:41:22Z" - latency: 1.086335ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:40:22Z" - latency: 1.63297ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:39:22Z" - latency: 1.423939ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:38:22Z" - latency: 1.065275ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:37:22Z" - latency: 1.350767ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:36:22Z" - latency: 1.227011ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:35:22Z" - latency: 1.235659ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:34:22Z" - latency: 1.304451ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:33:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T02:00:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-8-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-8.ec2.internal uid: 28c1c80b-a94a-4127-8041-c2b24cad9b2f resourceVersion: "63396" uid: 8b23316c-1220-4d8b-8f6d-7bece0d7fa2f spec: sourcePod: network-check-source-7bc5b6bf85-xk5l2 targetEndpoint: a440e6b47053b42fe996a99ee17277e6-bf11a160191d7807.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-18T02:06:22Z" message: 'load-balancer-api-external: tcp connection to a440e6b47053b42fe996a99ee17277e6-bf11a160191d7807.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.962173ms message: 'load-balancer-api-external: tcp connection to a440e6b47053b42fe996a99ee17277e6-bf11a160191d7807.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:42:22Z" - latency: 7.919565ms message: 'load-balancer-api-external: resolved host name a440e6b47053b42fe996a99ee17277e6-bf11a160191d7807.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T02:42:22Z" - latency: 3.508799ms message: 'load-balancer-api-external: tcp connection to a440e6b47053b42fe996a99ee17277e6-bf11a160191d7807.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:41:22Z" - latency: 7.381482ms message: 'load-balancer-api-external: resolved host name a440e6b47053b42fe996a99ee17277e6-bf11a160191d7807.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T02:41:22Z" - latency: 4.963134ms message: 'load-balancer-api-external: tcp connection to a440e6b47053b42fe996a99ee17277e6-bf11a160191d7807.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:40:22Z" - latency: 7.582701ms message: 'load-balancer-api-external: resolved host name a440e6b47053b42fe996a99ee17277e6-bf11a160191d7807.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T02:40:22Z" - latency: 3.825001ms message: 'load-balancer-api-external: tcp connection to a440e6b47053b42fe996a99ee17277e6-bf11a160191d7807.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:39:22Z" - latency: 7.389717ms message: 'load-balancer-api-external: resolved host name a440e6b47053b42fe996a99ee17277e6-bf11a160191d7807.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T02:39:22Z" - latency: 4.824015ms message: 'load-balancer-api-external: tcp connection to a440e6b47053b42fe996a99ee17277e6-bf11a160191d7807.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:38:22Z" - latency: 7.87267ms message: 'load-balancer-api-external: resolved host name a440e6b47053b42fe996a99ee17277e6-bf11a160191d7807.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T02:38:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T02:00:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-8-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-8.ec2.internal uid: 28c1c80b-a94a-4127-8041-c2b24cad9b2f resourceVersion: "63395" uid: be5f38f9-a95a-49c0-b601-23e256b6e7d1 spec: sourcePod: network-check-source-7bc5b6bf85-xk5l2 targetEndpoint: a440e6b47053b42fe996a99ee17277e6-bf11a160191d7807.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-18T02:06:22Z" message: 'load-balancer-api-internal: tcp connection to a440e6b47053b42fe996a99ee17277e6-bf11a160191d7807.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.072482ms message: 'load-balancer-api-internal: tcp connection to a440e6b47053b42fe996a99ee17277e6-bf11a160191d7807.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:42:22Z" - latency: 7.840859ms message: 'load-balancer-api-internal: resolved host name a440e6b47053b42fe996a99ee17277e6-bf11a160191d7807.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T02:42:22Z" - latency: 4.123679ms message: 'load-balancer-api-internal: tcp connection to a440e6b47053b42fe996a99ee17277e6-bf11a160191d7807.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:41:22Z" - latency: 7.273363ms message: 'load-balancer-api-internal: resolved host name a440e6b47053b42fe996a99ee17277e6-bf11a160191d7807.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T02:41:22Z" - latency: 4.900423ms message: 'load-balancer-api-internal: tcp connection to a440e6b47053b42fe996a99ee17277e6-bf11a160191d7807.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:40:22Z" - latency: 7.528563ms message: 'load-balancer-api-internal: resolved host name a440e6b47053b42fe996a99ee17277e6-bf11a160191d7807.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T02:40:22Z" - latency: 3.861733ms message: 'load-balancer-api-internal: tcp connection to a440e6b47053b42fe996a99ee17277e6-bf11a160191d7807.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:39:22Z" - latency: 7.259908ms message: 'load-balancer-api-internal: resolved host name a440e6b47053b42fe996a99ee17277e6-bf11a160191d7807.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T02:39:22Z" - latency: 4.482666ms message: 'load-balancer-api-internal: tcp connection to a440e6b47053b42fe996a99ee17277e6-bf11a160191d7807.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:38:22Z" - latency: 7.817285ms message: 'load-balancer-api-internal: resolved host name a440e6b47053b42fe996a99ee17277e6-bf11a160191d7807.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T02:38:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T02:00:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-8-to-network-check-target-ip-10-0-130-187 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-8.ec2.internal uid: 28c1c80b-a94a-4127-8041-c2b24cad9b2f resourceVersion: "63391" uid: cba24856-5838-4368-ac48-0a38128cf6a3 spec: sourcePod: network-check-source-7bc5b6bf85-xk5l2 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-18T02:07:22Z" message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.631528ms message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:42:22Z" - latency: 1.882747ms message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:41:22Z" - latency: 2.27473ms message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:40:22Z" - latency: 2.385001ms message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:39:22Z" - latency: 2.305565ms message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:38:22Z" - latency: 2.234595ms message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:37:22Z" - latency: 2.624272ms message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:36:22Z" - latency: 2.620087ms message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:35:22Z" - latency: 2.170333ms message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:34:22Z" - latency: 2.293808ms message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:33:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T02:00:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-8-to-network-check-target-ip-10-0-133-113 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-8.ec2.internal uid: 28c1c80b-a94a-4127-8041-c2b24cad9b2f resourceVersion: "63390" uid: e768be79-e6a3-4cce-8c99-0976d7bc8a1a spec: sourcePod: network-check-source-7bc5b6bf85-xk5l2 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-18T02:07:22Z" message: 'network-check-target-ip-10-0-133-113: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.268363ms message: 'network-check-target-ip-10-0-133-113: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:42:22Z" - latency: 2.025561ms message: 'network-check-target-ip-10-0-133-113: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:41:22Z" - latency: 2.340721ms message: 'network-check-target-ip-10-0-133-113: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:40:22Z" - latency: 2.506299ms message: 'network-check-target-ip-10-0-133-113: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:39:22Z" - latency: 2.020439ms message: 'network-check-target-ip-10-0-133-113: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:38:22Z" - latency: 2.246551ms message: 'network-check-target-ip-10-0-133-113: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:37:22Z" - latency: 3.199846ms message: 'network-check-target-ip-10-0-133-113: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:36:22Z" - latency: 2.415685ms message: 'network-check-target-ip-10-0-133-113: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:35:22Z" - latency: 2.551845ms message: 'network-check-target-ip-10-0-133-113: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:34:22Z" - latency: 2.222601ms message: 'network-check-target-ip-10-0-133-113: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:33:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T02:00:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-8-to-network-check-target-ip-10-0-143-8 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-8.ec2.internal uid: 28c1c80b-a94a-4127-8041-c2b24cad9b2f resourceVersion: "63389" uid: 99fdcc94-3c14-4eed-be05-35a51d985981 spec: sourcePod: network-check-source-7bc5b6bf85-xk5l2 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-18T02:07:22Z" message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.059596ms message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:42:22Z" - latency: 1.159971ms message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:41:22Z" - latency: 1.234283ms message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:40:22Z" - latency: 1.079792ms message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:39:22Z" - latency: 1.410546ms message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:38:22Z" - latency: 1.037124ms message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:37:22Z" - latency: 1.473022ms message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:36:22Z" - latency: 1.142383ms message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:35:22Z" - latency: 1.018748ms message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:34:22Z" - latency: 1.437337ms message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:33:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T02:00:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-8-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-8.ec2.internal uid: 28c1c80b-a94a-4127-8041-c2b24cad9b2f resourceVersion: "63392" uid: d7118923-535a-4628-bf63-024fddca0fb8 spec: sourcePod: network-check-source-7bc5b6bf85-xk5l2 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-18T02:06:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.072352ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:42:22Z" - latency: 2.326229ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T02:42:22Z" - latency: 1.038121ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:41:22Z" - latency: 1.87198ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T02:41:22Z" - latency: 1.005737ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:40:22Z" - latency: 1.872187ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T02:40:22Z" - latency: 938.836µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:39:22Z" - latency: 1.840401ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T02:39:22Z" - latency: 905.971µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T02:38:22Z" - latency: 2.092912ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T02:38:22Z" kind: List metadata: resourceVersion: ""