apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T09:38:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-231-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-231.ec2.internal
      uid: 425d995f-1524-4b10-b0ba-47e5289a4eab
    resourceVersion: "10384"
    uid: 95bfacaa-7817-49be-b488-0c7e13a8b414
  spec:
    sourcePod: network-check-source-56d84b9f44-7zhz6
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T09:38:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-231-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-231.ec2.internal
      uid: 425d995f-1524-4b10-b0ba-47e5289a4eab
    resourceVersion: "13996"
    uid: e8d418a6-0ec9-497f-94bf-c9ca20bb3b7f
  spec:
    sourcePod: network-check-source-56d84b9f44-7zhz6
    targetEndpoint: ac075457efda4446c9b7da8e69727be1-d51e6f006354baab.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T09:44:36Z"
      message: 'load-balancer-api-external: tcp connection to ac075457efda4446c9b7da8e69727be1-d51e6f006354baab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.995952ms
      message: 'load-balancer-api-external: tcp connection to ac075457efda4446c9b7da8e69727be1-d51e6f006354baab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:44:36Z"
    - latency: 9.589566ms
      message: 'load-balancer-api-external: resolved host name ac075457efda4446c9b7da8e69727be1-d51e6f006354baab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:44:36Z"
    - latency: 5.367638ms
      message: 'load-balancer-api-external: tcp connection to ac075457efda4446c9b7da8e69727be1-d51e6f006354baab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:43:36Z"
    - latency: 8.255808ms
      message: 'load-balancer-api-external: resolved host name ac075457efda4446c9b7da8e69727be1-d51e6f006354baab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:43:36Z"
    - latency: 5.373965ms
      message: 'load-balancer-api-external: tcp connection to ac075457efda4446c9b7da8e69727be1-d51e6f006354baab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:42:36Z"
    - latency: 8.288519ms
      message: 'load-balancer-api-external: resolved host name ac075457efda4446c9b7da8e69727be1-d51e6f006354baab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:42:36Z"
    - latency: 5.230099ms
      message: 'load-balancer-api-external: tcp connection to ac075457efda4446c9b7da8e69727be1-d51e6f006354baab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:41:36Z"
    - latency: 8.491259ms
      message: 'load-balancer-api-external: resolved host name ac075457efda4446c9b7da8e69727be1-d51e6f006354baab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:41:36Z"
    - latency: 4.931136ms
      message: 'load-balancer-api-external: tcp connection to ac075457efda4446c9b7da8e69727be1-d51e6f006354baab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:40:36Z"
    - latency: 8.592111ms
      message: 'load-balancer-api-external: resolved host name ac075457efda4446c9b7da8e69727be1-d51e6f006354baab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:40:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T09:38:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-231-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-231.ec2.internal
      uid: 425d995f-1524-4b10-b0ba-47e5289a4eab
    resourceVersion: "13997"
    uid: 8aa3030d-1a2f-403a-8408-82b6b549d26c
  spec:
    sourcePod: network-check-source-56d84b9f44-7zhz6
    targetEndpoint: ac075457efda4446c9b7da8e69727be1-d51e6f006354baab.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T09:44:36Z"
      message: 'load-balancer-api-internal: tcp connection to ac075457efda4446c9b7da8e69727be1-d51e6f006354baab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.987355ms
      message: 'load-balancer-api-internal: tcp connection to ac075457efda4446c9b7da8e69727be1-d51e6f006354baab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:44:36Z"
    - latency: 9.689294ms
      message: 'load-balancer-api-internal: resolved host name ac075457efda4446c9b7da8e69727be1-d51e6f006354baab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:44:36Z"
    - latency: 5.37619ms
      message: 'load-balancer-api-internal: tcp connection to ac075457efda4446c9b7da8e69727be1-d51e6f006354baab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:43:36Z"
    - latency: 8.289477ms
      message: 'load-balancer-api-internal: resolved host name ac075457efda4446c9b7da8e69727be1-d51e6f006354baab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:43:36Z"
    - latency: 5.343855ms
      message: 'load-balancer-api-internal: tcp connection to ac075457efda4446c9b7da8e69727be1-d51e6f006354baab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:42:36Z"
    - latency: 8.385645ms
      message: 'load-balancer-api-internal: resolved host name ac075457efda4446c9b7da8e69727be1-d51e6f006354baab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:42:36Z"
    - latency: 5.198277ms
      message: 'load-balancer-api-internal: tcp connection to ac075457efda4446c9b7da8e69727be1-d51e6f006354baab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:41:36Z"
    - latency: 8.554172ms
      message: 'load-balancer-api-internal: resolved host name ac075457efda4446c9b7da8e69727be1-d51e6f006354baab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:41:36Z"
    - latency: 4.943217ms
      message: 'load-balancer-api-internal: tcp connection to ac075457efda4446c9b7da8e69727be1-d51e6f006354baab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:40:36Z"
    - latency: 8.513318ms
      message: 'load-balancer-api-internal: resolved host name ac075457efda4446c9b7da8e69727be1-d51e6f006354baab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:40:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T09:38:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-231-to-network-check-target-ip-10-0-130-85
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-231.ec2.internal
      uid: 425d995f-1524-4b10-b0ba-47e5289a4eab
    resourceVersion: "10390"
    uid: 581ffc8d-6b1c-4611-97fe-80c6da2780f0
  spec:
    sourcePod: network-check-source-56d84b9f44-7zhz6
    targetEndpoint: 10.133.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T09:38:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-231-to-network-check-target-ip-10-0-138-85
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-231.ec2.internal
      uid: 425d995f-1524-4b10-b0ba-47e5289a4eab
    resourceVersion: "10391"
    uid: 57a43e4d-51c6-4fa3-908b-84435523c40d
  spec:
    sourcePod: network-check-source-56d84b9f44-7zhz6
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T09:38:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-231-to-network-check-target-ip-10-0-141-231
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-231.ec2.internal
      uid: 425d995f-1524-4b10-b0ba-47e5289a4eab
    resourceVersion: "10389"
    uid: 4a640602-d9f0-4bf2-b906-335481fa65aa
  spec:
    sourcePod: network-check-source-56d84b9f44-7zhz6
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T09:38:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-231-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-231.ec2.internal
      uid: 425d995f-1524-4b10-b0ba-47e5289a4eab
    resourceVersion: "13995"
    uid: 17e03723-bdbf-4656-9b17-a13d2e10023a
  spec:
    sourcePod: network-check-source-56d84b9f44-7zhz6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T09:44:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 883.644µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:44:36Z"
    - latency: 2.481221ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:44:36Z"
    - latency: 869.073µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:43:36Z"
    - latency: 1.761365ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:43:36Z"
    - latency: 813.057µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:42:36Z"
    - latency: 1.68783ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:42:36Z"
    - latency: 961.495µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:41:36Z"
    - latency: 1.711875ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:41:36Z"
    - latency: 836.134µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:40:36Z"
    - latency: 1.705902ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:40:36Z"
kind: List
metadata:
  resourceVersion: ""