apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T15:21:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-29-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-29.ec2.internal
      uid: d7bb0ed8-2461-47a0-947b-b511af4751a9
    resourceVersion: "23763"
    uid: 4fdbdb9f-33db-42f5-8e12-6e3c7a9a84a2
  spec:
    sourcePod: network-check-source-8894fc9bd-k9sfm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T15:28:21Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.207762ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:28:21Z"
    - latency: 789.331µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:27:21Z"
    - latency: 1.328551ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:26:21Z"
    - latency: 803.792µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:25:21Z"
    - latency: 1.503076ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:24:21Z"
    - latency: 910.411µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:23:21Z"
    - latency: 1.000358ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:22:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T15:21:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-29-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-29.ec2.internal
      uid: d7bb0ed8-2461-47a0-947b-b511af4751a9
    resourceVersion: "22665"
    uid: 1ada1429-2d98-453e-911f-de93f2dc2654
  spec:
    sourcePod: network-check-source-8894fc9bd-k9sfm
    targetEndpoint: a3134101187f14dc49f81b52f5a9eced-3497dbefbb02cf16.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T15:27:21Z"
      message: 'load-balancer-api-external: tcp connection to a3134101187f14dc49f81b52f5a9eced-3497dbefbb02cf16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.829656ms
      message: 'load-balancer-api-external: tcp connection to a3134101187f14dc49f81b52f5a9eced-3497dbefbb02cf16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:27:21Z"
    - latency: 6.468773ms
      message: 'load-balancer-api-external: resolved host name a3134101187f14dc49f81b52f5a9eced-3497dbefbb02cf16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T15:27:21Z"
    - latency: 3.882767ms
      message: 'load-balancer-api-external: tcp connection to a3134101187f14dc49f81b52f5a9eced-3497dbefbb02cf16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:26:21Z"
    - latency: 6.175589ms
      message: 'load-balancer-api-external: resolved host name a3134101187f14dc49f81b52f5a9eced-3497dbefbb02cf16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T15:26:21Z"
    - latency: 4.282258ms
      message: 'load-balancer-api-external: tcp connection to a3134101187f14dc49f81b52f5a9eced-3497dbefbb02cf16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:25:21Z"
    - latency: 6.097539ms
      message: 'load-balancer-api-external: resolved host name a3134101187f14dc49f81b52f5a9eced-3497dbefbb02cf16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T15:25:21Z"
    - latency: 4.986711ms
      message: 'load-balancer-api-external: tcp connection to a3134101187f14dc49f81b52f5a9eced-3497dbefbb02cf16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:24:21Z"
    - latency: 7.084894ms
      message: 'load-balancer-api-external: resolved host name a3134101187f14dc49f81b52f5a9eced-3497dbefbb02cf16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T15:24:21Z"
    - latency: 5.220589ms
      message: 'load-balancer-api-external: tcp connection to a3134101187f14dc49f81b52f5a9eced-3497dbefbb02cf16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:23:21Z"
    - latency: 6.737803ms
      message: 'load-balancer-api-external: resolved host name a3134101187f14dc49f81b52f5a9eced-3497dbefbb02cf16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T15:23:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T15:21:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-29-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-29.ec2.internal
      uid: d7bb0ed8-2461-47a0-947b-b511af4751a9
    resourceVersion: "22666"
    uid: db7ad87a-1d78-4829-9e38-5d5988cd514f
  spec:
    sourcePod: network-check-source-8894fc9bd-k9sfm
    targetEndpoint: a3134101187f14dc49f81b52f5a9eced-3497dbefbb02cf16.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T15:27:21Z"
      message: 'load-balancer-api-internal: tcp connection to a3134101187f14dc49f81b52f5a9eced-3497dbefbb02cf16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.582519ms
      message: 'load-balancer-api-internal: tcp connection to a3134101187f14dc49f81b52f5a9eced-3497dbefbb02cf16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:27:21Z"
    - latency: 6.603078ms
      message: 'load-balancer-api-internal: resolved host name a3134101187f14dc49f81b52f5a9eced-3497dbefbb02cf16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T15:27:21Z"
    - latency: 5.156288ms
      message: 'load-balancer-api-internal: tcp connection to a3134101187f14dc49f81b52f5a9eced-3497dbefbb02cf16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:26:21Z"
    - latency: 6.922187ms
      message: 'load-balancer-api-internal: resolved host name a3134101187f14dc49f81b52f5a9eced-3497dbefbb02cf16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T15:26:21Z"
    - latency: 4.292304ms
      message: 'load-balancer-api-internal: tcp connection to a3134101187f14dc49f81b52f5a9eced-3497dbefbb02cf16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:25:21Z"
    - latency: 6.294069ms
      message: 'load-balancer-api-internal: resolved host name a3134101187f14dc49f81b52f5a9eced-3497dbefbb02cf16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T15:25:21Z"
    - latency: 5.205344ms
      message: 'load-balancer-api-internal: tcp connection to a3134101187f14dc49f81b52f5a9eced-3497dbefbb02cf16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:24:21Z"
    - latency: 7.157091ms
      message: 'load-balancer-api-internal: resolved host name a3134101187f14dc49f81b52f5a9eced-3497dbefbb02cf16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T15:24:21Z"
    - latency: 5.217732ms
      message: 'load-balancer-api-internal: tcp connection to a3134101187f14dc49f81b52f5a9eced-3497dbefbb02cf16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:23:21Z"
    - latency: 6.859428ms
      message: 'load-balancer-api-internal: resolved host name a3134101187f14dc49f81b52f5a9eced-3497dbefbb02cf16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T15:23:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T15:21:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-29-to-network-check-target-ip-10-0-130-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-29.ec2.internal
      uid: d7bb0ed8-2461-47a0-947b-b511af4751a9
    resourceVersion: "23761"
    uid: 8efbfed2-02f4-4a1d-ab51-57589d9e20be
  spec:
    sourcePod: network-check-source-8894fc9bd-k9sfm
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T15:28:21Z"
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.996851ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:28:21Z"
    - latency: 2.427402ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:27:21Z"
    - latency: 1.926261ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:26:21Z"
    - latency: 2.197412ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:25:21Z"
    - latency: 2.163066ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:24:21Z"
    - latency: 2.64614ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:23:21Z"
    - latency: 2.530809ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:22:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T15:21:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-29-to-network-check-target-ip-10-0-131-29
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-29.ec2.internal
      uid: d7bb0ed8-2461-47a0-947b-b511af4751a9
    resourceVersion: "23760"
    uid: 4abd462d-eb2c-4a61-819e-8408dc98b0df
  spec:
    sourcePod: network-check-source-8894fc9bd-k9sfm
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T15:28:21Z"
      message: 'network-check-target-ip-10-0-131-29: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 945.75µs
      message: 'network-check-target-ip-10-0-131-29: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:28:21Z"
    - latency: 837.374µs
      message: 'network-check-target-ip-10-0-131-29: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:27:21Z"
    - latency: 1.332294ms
      message: 'network-check-target-ip-10-0-131-29: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:26:21Z"
    - latency: 1.329942ms
      message: 'network-check-target-ip-10-0-131-29: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:25:21Z"
    - latency: 850.504µs
      message: 'network-check-target-ip-10-0-131-29: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:24:21Z"
    - latency: 926.629µs
      message: 'network-check-target-ip-10-0-131-29: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:23:21Z"
    - latency: 1.386852ms
      message: 'network-check-target-ip-10-0-131-29: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:22:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T15:21:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-29-to-network-check-target-ip-10-0-133-75
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-29.ec2.internal
      uid: d7bb0ed8-2461-47a0-947b-b511af4751a9
    resourceVersion: "23762"
    uid: b0d851c5-1671-466c-a6f8-b3390662e285
  spec:
    sourcePod: network-check-source-8894fc9bd-k9sfm
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T15:28:21Z"
      message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.246832ms
      message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:28:21Z"
    - latency: 2.045451ms
      message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:27:21Z"
    - latency: 2.099096ms
      message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:26:21Z"
    - latency: 2.248512ms
      message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:25:21Z"
    - latency: 2.562647ms
      message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:24:21Z"
    - latency: 2.489812ms
      message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:23:21Z"
    - latency: 2.436445ms
      message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:22:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T15:21:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-29-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-29.ec2.internal
      uid: d7bb0ed8-2461-47a0-947b-b511af4751a9
    resourceVersion: "22664"
    uid: a45813b2-43a4-4b3f-9056-a7b8336bd383
  spec:
    sourcePod: network-check-source-8894fc9bd-k9sfm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T15:27:21Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 953.902µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:27:21Z"
    - latency: 2.305993ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T15:27:21Z"
    - latency: 947.906µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:26:21Z"
    - latency: 1.863697ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T15:26:21Z"
    - latency: 921.03µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:25:21Z"
    - latency: 1.763198ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T15:25:21Z"
    - latency: 1.225472ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:24:21Z"
    - latency: 2.075128ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T15:24:21Z"
    - latency: 920.274µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T15:23:21Z"
    - latency: 1.993429ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T15:23:21Z"
kind: List
metadata:
  resourceVersion: ""