apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T07:37:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-107-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-107.ec2.internal
      uid: 80fa3871-ecd8-4b98-baeb-2249b2ad3ccf
    resourceVersion: "14701"
    uid: 25afb0e5-3d8f-49f9-969e-b07db0ad3d2f
  spec:
    sourcePod: network-check-source-65bdbbff45-9rr9p
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T07:44:19Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 884.985µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:44:19Z"
    - latency: 947.711µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:43:19Z"
    - latency: 1.035653ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:42:19Z"
    - latency: 1.389353ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:41:19Z"
    - latency: 1.15153ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:40:19Z"
    - latency: 1.073458ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:39:19Z"
    - latency: 1.081054ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:38:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T07:37:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-107-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-107.ec2.internal
      uid: 80fa3871-ecd8-4b98-baeb-2249b2ad3ccf
    resourceVersion: "14356"
    uid: 014dad1b-d410-47aa-be88-abf4e14cc17f
  spec:
    sourcePod: network-check-source-65bdbbff45-9rr9p
    targetEndpoint: a466eeae8894d40cb93d0d25adb8d543-60c497526557cb5e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T07:43:19Z"
      message: 'load-balancer-api-external: tcp connection to a466eeae8894d40cb93d0d25adb8d543-60c497526557cb5e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.683135ms
      message: 'load-balancer-api-external: tcp connection to a466eeae8894d40cb93d0d25adb8d543-60c497526557cb5e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:43:19Z"
    - latency: 9.239721ms
      message: 'load-balancer-api-external: resolved host name a466eeae8894d40cb93d0d25adb8d543-60c497526557cb5e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T07:43:19Z"
    - latency: 6.236869ms
      message: 'load-balancer-api-external: tcp connection to a466eeae8894d40cb93d0d25adb8d543-60c497526557cb5e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:42:19Z"
    - latency: 7.919335ms
      message: 'load-balancer-api-external: resolved host name a466eeae8894d40cb93d0d25adb8d543-60c497526557cb5e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T07:42:19Z"
    - latency: 4.955785ms
      message: 'load-balancer-api-external: tcp connection to a466eeae8894d40cb93d0d25adb8d543-60c497526557cb5e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:41:19Z"
    - latency: 8.91597ms
      message: 'load-balancer-api-external: resolved host name a466eeae8894d40cb93d0d25adb8d543-60c497526557cb5e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T07:41:19Z"
    - latency: 4.639473ms
      message: 'load-balancer-api-external: tcp connection to a466eeae8894d40cb93d0d25adb8d543-60c497526557cb5e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:40:19Z"
    - latency: 8.561731ms
      message: 'load-balancer-api-external: resolved host name a466eeae8894d40cb93d0d25adb8d543-60c497526557cb5e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T07:40:19Z"
    - latency: 3.948679ms
      message: 'load-balancer-api-external: tcp connection to a466eeae8894d40cb93d0d25adb8d543-60c497526557cb5e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:39:19Z"
    - latency: 7.671183ms
      message: 'load-balancer-api-external: resolved host name a466eeae8894d40cb93d0d25adb8d543-60c497526557cb5e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T07:39:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T07:37:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-107-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-107.ec2.internal
      uid: 80fa3871-ecd8-4b98-baeb-2249b2ad3ccf
    resourceVersion: "14357"
    uid: 278522d9-0bf5-496a-a77b-35a3b1ec4dec
  spec:
    sourcePod: network-check-source-65bdbbff45-9rr9p
    targetEndpoint: a466eeae8894d40cb93d0d25adb8d543-60c497526557cb5e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T07:43:19Z"
      message: 'load-balancer-api-internal: tcp connection to a466eeae8894d40cb93d0d25adb8d543-60c497526557cb5e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 8.435434ms
      message: 'load-balancer-api-internal: tcp connection to a466eeae8894d40cb93d0d25adb8d543-60c497526557cb5e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:43:19Z"
    - latency: 9.179343ms
      message: 'load-balancer-api-internal: resolved host name a466eeae8894d40cb93d0d25adb8d543-60c497526557cb5e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T07:43:19Z"
    - latency: 6.194816ms
      message: 'load-balancer-api-internal: tcp connection to a466eeae8894d40cb93d0d25adb8d543-60c497526557cb5e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:42:19Z"
    - latency: 8.04126ms
      message: 'load-balancer-api-internal: resolved host name a466eeae8894d40cb93d0d25adb8d543-60c497526557cb5e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T07:42:19Z"
    - latency: 4.971101ms
      message: 'load-balancer-api-internal: tcp connection to a466eeae8894d40cb93d0d25adb8d543-60c497526557cb5e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:41:19Z"
    - latency: 9.035438ms
      message: 'load-balancer-api-internal: resolved host name a466eeae8894d40cb93d0d25adb8d543-60c497526557cb5e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T07:41:19Z"
    - latency: 5.020538ms
      message: 'load-balancer-api-internal: tcp connection to a466eeae8894d40cb93d0d25adb8d543-60c497526557cb5e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:40:19Z"
    - latency: 8.686913ms
      message: 'load-balancer-api-internal: resolved host name a466eeae8894d40cb93d0d25adb8d543-60c497526557cb5e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T07:40:19Z"
    - latency: 3.42627ms
      message: 'load-balancer-api-internal: tcp connection to a466eeae8894d40cb93d0d25adb8d543-60c497526557cb5e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:39:19Z"
    - latency: 7.766166ms
      message: 'load-balancer-api-internal: resolved host name a466eeae8894d40cb93d0d25adb8d543-60c497526557cb5e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T07:39:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T07:37:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-107-to-network-check-target-ip-10-0-130-107
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-107.ec2.internal
      uid: 80fa3871-ecd8-4b98-baeb-2249b2ad3ccf
    resourceVersion: "14700"
    uid: dc0de134-512e-4746-ada8-e86ce8c03304
  spec:
    sourcePod: network-check-source-65bdbbff45-9rr9p
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T07:44:19Z"
      message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.072629ms
      message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:44:19Z"
    - latency: 879.233µs
      message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:43:19Z"
    - latency: 878.435µs
      message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:42:19Z"
    - latency: 1.084039ms
      message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:41:19Z"
    - latency: 825.46µs
      message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:40:19Z"
    - latency: 890.112µs
      message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:39:19Z"
    - latency: 1.337367ms
      message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:38:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T07:37:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-107-to-network-check-target-ip-10-0-133-235
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-107.ec2.internal
      uid: 80fa3871-ecd8-4b98-baeb-2249b2ad3ccf
    resourceVersion: "14699"
    uid: 47fae03b-ec95-47a1-ac23-9107361406cc
  spec:
    sourcePod: network-check-source-65bdbbff45-9rr9p
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T07:44:19Z"
      message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.054895ms
      message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:44:19Z"
    - latency: 2.3764ms
      message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:43:19Z"
    - latency: 2.358796ms
      message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:42:19Z"
    - latency: 2.262203ms
      message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:41:19Z"
    - latency: 2.217684ms
      message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:40:19Z"
    - latency: 2.113553ms
      message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:39:19Z"
    - latency: 2.216953ms
      message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:38:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T07:37:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-107-to-network-check-target-ip-10-0-134-23
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-107.ec2.internal
      uid: 80fa3871-ecd8-4b98-baeb-2249b2ad3ccf
    resourceVersion: "14698"
    uid: 266d5762-7d28-4954-a6d3-62485a22c25f
  spec:
    sourcePod: network-check-source-65bdbbff45-9rr9p
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T07:44:19Z"
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.819684ms
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:44:19Z"
    - latency: 1.864674ms
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:43:19Z"
    - latency: 1.889389ms
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:42:19Z"
    - latency: 2.0608ms
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:41:19Z"
    - latency: 1.850815ms
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:40:19Z"
    - latency: 1.808996ms
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:39:19Z"
    - latency: 2.041865ms
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:38:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T07:37:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-107-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-107.ec2.internal
      uid: 80fa3871-ecd8-4b98-baeb-2249b2ad3ccf
    resourceVersion: "14355"
    uid: a27e0e40-0967-4c5b-9e0f-80c7e5fabc1e
  spec:
    sourcePod: network-check-source-65bdbbff45-9rr9p
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T07:43:19Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 816.618µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:43:19Z"
    - latency: 1.653285ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T07:43:19Z"
    - latency: 935.057µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:42:19Z"
    - latency: 1.745746ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T07:42:19Z"
    - latency: 1.054237ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:41:19Z"
    - latency: 1.84842ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T07:41:19Z"
    - latency: 754.52µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:40:19Z"
    - latency: 2.066276ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T07:40:19Z"
    - latency: 1.107577ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T07:39:19Z"
    - latency: 1.850906ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T07:39:19Z"
kind: List
metadata:
  resourceVersion: ""