apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T08:46:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-123-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-123.ec2.internal
      uid: 5efa1be4-7d54-4b1f-99b9-eeb34eda4d07
    resourceVersion: "14910"
    uid: 1277ba52-844a-4c63-8b2c-8dc10f2d69c7
  spec:
    sourcePod: network-check-source-6f8b768455-mplzt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T08:53:50Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.46769ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:53:50Z"
    - latency: 888.306µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:52:50Z"
    - latency: 971.032µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:51:50Z"
    - latency: 1.46178ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:50:50Z"
    - latency: 1.010284ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:49:50Z"
    - latency: 910.712µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:48:50Z"
    - latency: 1.049551ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:47:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T08:46:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-123-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-123.ec2.internal
      uid: 5efa1be4-7d54-4b1f-99b9-eeb34eda4d07
    resourceVersion: "14438"
    uid: 7262d836-348c-42f8-91a2-64ed2ca7871e
  spec:
    sourcePod: network-check-source-6f8b768455-mplzt
    targetEndpoint: a069be78393ff4af7ae284d0adf5cc25-3517001ec1673a47.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T08:52:50Z"
      message: 'load-balancer-api-external: tcp connection to a069be78393ff4af7ae284d0adf5cc25-3517001ec1673a47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.909289ms
      message: 'load-balancer-api-external: tcp connection to a069be78393ff4af7ae284d0adf5cc25-3517001ec1673a47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:52:50Z"
    - latency: 10.225513ms
      message: 'load-balancer-api-external: resolved host name a069be78393ff4af7ae284d0adf5cc25-3517001ec1673a47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:52:50Z"
    - latency: 4.082369ms
      message: 'load-balancer-api-external: tcp connection to a069be78393ff4af7ae284d0adf5cc25-3517001ec1673a47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:51:50Z"
    - latency: 7.321493ms
      message: 'load-balancer-api-external: resolved host name a069be78393ff4af7ae284d0adf5cc25-3517001ec1673a47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:51:50Z"
    - latency: 4.352326ms
      message: 'load-balancer-api-external: tcp connection to a069be78393ff4af7ae284d0adf5cc25-3517001ec1673a47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:50:50Z"
    - latency: 6.303018ms
      message: 'load-balancer-api-external: resolved host name a069be78393ff4af7ae284d0adf5cc25-3517001ec1673a47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:50:50Z"
    - latency: 4.216094ms
      message: 'load-balancer-api-external: tcp connection to a069be78393ff4af7ae284d0adf5cc25-3517001ec1673a47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:49:50Z"
    - latency: 7.070929ms
      message: 'load-balancer-api-external: resolved host name a069be78393ff4af7ae284d0adf5cc25-3517001ec1673a47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:49:50Z"
    - latency: 4.776884ms
      message: 'load-balancer-api-external: tcp connection to a069be78393ff4af7ae284d0adf5cc25-3517001ec1673a47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:48:50Z"
    - latency: 6.756887ms
      message: 'load-balancer-api-external: resolved host name a069be78393ff4af7ae284d0adf5cc25-3517001ec1673a47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:48:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T08:46:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-123-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-123.ec2.internal
      uid: 5efa1be4-7d54-4b1f-99b9-eeb34eda4d07
    resourceVersion: "14439"
    uid: 3b9a79f3-2ab7-44de-be68-dbbe15374777
  spec:
    sourcePod: network-check-source-6f8b768455-mplzt
    targetEndpoint: a069be78393ff4af7ae284d0adf5cc25-3517001ec1673a47.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T08:52:50Z"
      message: 'load-balancer-api-internal: tcp connection to a069be78393ff4af7ae284d0adf5cc25-3517001ec1673a47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.899237ms
      message: 'load-balancer-api-internal: tcp connection to a069be78393ff4af7ae284d0adf5cc25-3517001ec1673a47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:52:50Z"
    - latency: 10.190006ms
      message: 'load-balancer-api-internal: resolved host name a069be78393ff4af7ae284d0adf5cc25-3517001ec1673a47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:52:50Z"
    - latency: 4.05934ms
      message: 'load-balancer-api-internal: tcp connection to a069be78393ff4af7ae284d0adf5cc25-3517001ec1673a47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:51:50Z"
    - latency: 7.280526ms
      message: 'load-balancer-api-internal: resolved host name a069be78393ff4af7ae284d0adf5cc25-3517001ec1673a47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:51:50Z"
    - latency: 4.387248ms
      message: 'load-balancer-api-internal: tcp connection to a069be78393ff4af7ae284d0adf5cc25-3517001ec1673a47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:50:50Z"
    - latency: 6.270963ms
      message: 'load-balancer-api-internal: resolved host name a069be78393ff4af7ae284d0adf5cc25-3517001ec1673a47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:50:50Z"
    - latency: 4.210776ms
      message: 'load-balancer-api-internal: tcp connection to a069be78393ff4af7ae284d0adf5cc25-3517001ec1673a47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:49:50Z"
    - latency: 7.043939ms
      message: 'load-balancer-api-internal: resolved host name a069be78393ff4af7ae284d0adf5cc25-3517001ec1673a47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:49:50Z"
    - latency: 4.741184ms
      message: 'load-balancer-api-internal: tcp connection to a069be78393ff4af7ae284d0adf5cc25-3517001ec1673a47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:48:50Z"
    - latency: 6.736532ms
      message: 'load-balancer-api-internal: resolved host name a069be78393ff4af7ae284d0adf5cc25-3517001ec1673a47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:48:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T08:46:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-123-to-network-check-target-ip-10-0-130-237
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-123.ec2.internal
      uid: 5efa1be4-7d54-4b1f-99b9-eeb34eda4d07
    resourceVersion: "14908"
    uid: 7e0ac075-114a-4e37-b4c2-e7620223e182
  spec:
    sourcePod: network-check-source-6f8b768455-mplzt
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T08:53:50Z"
      message: 'network-check-target-ip-10-0-130-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.848857ms
      message: 'network-check-target-ip-10-0-130-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:53:50Z"
    - latency: 2.074408ms
      message: 'network-check-target-ip-10-0-130-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:52:50Z"
    - latency: 2.138464ms
      message: 'network-check-target-ip-10-0-130-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:51:50Z"
    - latency: 2.945774ms
      message: 'network-check-target-ip-10-0-130-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:50:50Z"
    - latency: 2.511537ms
      message: 'network-check-target-ip-10-0-130-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:49:50Z"
    - latency: 2.319252ms
      message: 'network-check-target-ip-10-0-130-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:48:50Z"
    - latency: 2.536377ms
      message: 'network-check-target-ip-10-0-130-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:47:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T08:46:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-123-to-network-check-target-ip-10-0-136-123
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-123.ec2.internal
      uid: 5efa1be4-7d54-4b1f-99b9-eeb34eda4d07
    resourceVersion: "14907"
    uid: ac28f93d-99ce-4383-896a-24185e708e53
  spec:
    sourcePod: network-check-source-6f8b768455-mplzt
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T08:53:50Z"
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 910.177µs
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:53:50Z"
    - latency: 699.874µs
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:52:50Z"
    - latency: 942.028µs
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:51:50Z"
    - latency: 892.842µs
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:50:50Z"
    - latency: 1.184769ms
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:49:50Z"
    - latency: 1.105772ms
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:48:50Z"
    - latency: 1.334556ms
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:47:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T08:46:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-123-to-network-check-target-ip-10-0-143-47
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-123.ec2.internal
      uid: 5efa1be4-7d54-4b1f-99b9-eeb34eda4d07
    resourceVersion: "14909"
    uid: df8cdc6d-a647-496d-a0be-a377fad40cad
  spec:
    sourcePod: network-check-source-6f8b768455-mplzt
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T08:53:50Z"
      message: 'network-check-target-ip-10-0-143-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.291227ms
      message: 'network-check-target-ip-10-0-143-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:53:50Z"
    - latency: 2.252006ms
      message: 'network-check-target-ip-10-0-143-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:52:50Z"
    - latency: 1.822675ms
      message: 'network-check-target-ip-10-0-143-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:51:50Z"
    - latency: 2.353828ms
      message: 'network-check-target-ip-10-0-143-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:50:50Z"
    - latency: 2.210769ms
      message: 'network-check-target-ip-10-0-143-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:49:50Z"
    - latency: 2.063875ms
      message: 'network-check-target-ip-10-0-143-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:48:50Z"
    - latency: 2.299638ms
      message: 'network-check-target-ip-10-0-143-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:47:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T08:46:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-123-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-123.ec2.internal
      uid: 5efa1be4-7d54-4b1f-99b9-eeb34eda4d07
    resourceVersion: "14437"
    uid: d69e534a-cc60-46c7-8030-34f6c97707e5
  spec:
    sourcePod: network-check-source-6f8b768455-mplzt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T08:52:50Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 853.977µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:52:50Z"
    - latency: 1.620585ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:52:50Z"
    - latency: 788.991µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:51:50Z"
    - latency: 2.028839ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:51:50Z"
    - latency: 817.69µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:50:50Z"
    - latency: 1.726908ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:50:50Z"
    - latency: 1.031703ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:49:50Z"
    - latency: 1.881738ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:49:50Z"
    - latency: 890.067µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:48:50Z"
    - latency: 2.12943ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:48:50Z"
kind: List
metadata:
  resourceVersion: ""