apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:10:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-248-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-248.ec2.internal
      uid: 1f76bf73-6c16-439e-9399-80b6338b1dc1
    resourceVersion: "10769"
    uid: e3d57331-35c8-467f-a870-db0c96e04a91
  spec:
    sourcePod: network-check-source-989f8b8dc-6gn26
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:10:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-248-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-248.ec2.internal
      uid: 1f76bf73-6c16-439e-9399-80b6338b1dc1
    resourceVersion: "14292"
    uid: c2592979-9e6e-43ae-a98f-d2c2114cf077
  spec:
    sourcePod: network-check-source-989f8b8dc-6gn26
    targetEndpoint: ae8637b1c471b4adaab6ad20b961ac49-5c6956c415e41770.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:16:21Z"
      message: 'load-balancer-api-external: tcp connection to ae8637b1c471b4adaab6ad20b961ac49-5c6956c415e41770.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.758706ms
      message: 'load-balancer-api-external: tcp connection to ae8637b1c471b4adaab6ad20b961ac49-5c6956c415e41770.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:16:21Z"
    - latency: 7.042758ms
      message: 'load-balancer-api-external: resolved host name ae8637b1c471b4adaab6ad20b961ac49-5c6956c415e41770.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:16:21Z"
    - latency: 5.722773ms
      message: 'load-balancer-api-external: tcp connection to ae8637b1c471b4adaab6ad20b961ac49-5c6956c415e41770.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:15:21Z"
    - latency: 6.724963ms
      message: 'load-balancer-api-external: resolved host name ae8637b1c471b4adaab6ad20b961ac49-5c6956c415e41770.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:15:21Z"
    - latency: 3.718813ms
      message: 'load-balancer-api-external: tcp connection to ae8637b1c471b4adaab6ad20b961ac49-5c6956c415e41770.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:14:21Z"
    - latency: 6.451647ms
      message: 'load-balancer-api-external: resolved host name ae8637b1c471b4adaab6ad20b961ac49-5c6956c415e41770.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:14:21Z"
    - latency: 6.472461ms
      message: 'load-balancer-api-external: tcp connection to ae8637b1c471b4adaab6ad20b961ac49-5c6956c415e41770.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:13:21Z"
    - latency: 6.672617ms
      message: 'load-balancer-api-external: resolved host name ae8637b1c471b4adaab6ad20b961ac49-5c6956c415e41770.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:13:21Z"
    - latency: 5.272204ms
      message: 'load-balancer-api-external: tcp connection to ae8637b1c471b4adaab6ad20b961ac49-5c6956c415e41770.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:12:21Z"
    - latency: 6.301327ms
      message: 'load-balancer-api-external: resolved host name ae8637b1c471b4adaab6ad20b961ac49-5c6956c415e41770.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:12:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:10:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-248-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-248.ec2.internal
      uid: 1f76bf73-6c16-439e-9399-80b6338b1dc1
    resourceVersion: "14293"
    uid: 015466fc-44dd-401f-8247-a2a359f2ee33
  spec:
    sourcePod: network-check-source-989f8b8dc-6gn26
    targetEndpoint: ae8637b1c471b4adaab6ad20b961ac49-5c6956c415e41770.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:16:21Z"
      message: 'load-balancer-api-internal: tcp connection to ae8637b1c471b4adaab6ad20b961ac49-5c6956c415e41770.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.80712ms
      message: 'load-balancer-api-internal: tcp connection to ae8637b1c471b4adaab6ad20b961ac49-5c6956c415e41770.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:16:21Z"
    - latency: 6.981775ms
      message: 'load-balancer-api-internal: resolved host name ae8637b1c471b4adaab6ad20b961ac49-5c6956c415e41770.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:16:21Z"
    - latency: 5.715064ms
      message: 'load-balancer-api-internal: tcp connection to ae8637b1c471b4adaab6ad20b961ac49-5c6956c415e41770.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:15:21Z"
    - latency: 6.647982ms
      message: 'load-balancer-api-internal: resolved host name ae8637b1c471b4adaab6ad20b961ac49-5c6956c415e41770.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:15:21Z"
    - latency: 4.77359ms
      message: 'load-balancer-api-internal: tcp connection to ae8637b1c471b4adaab6ad20b961ac49-5c6956c415e41770.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:14:21Z"
    - latency: 6.407098ms
      message: 'load-balancer-api-internal: resolved host name ae8637b1c471b4adaab6ad20b961ac49-5c6956c415e41770.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:14:21Z"
    - latency: 6.435557ms
      message: 'load-balancer-api-internal: tcp connection to ae8637b1c471b4adaab6ad20b961ac49-5c6956c415e41770.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:13:21Z"
    - latency: 6.74654ms
      message: 'load-balancer-api-internal: resolved host name ae8637b1c471b4adaab6ad20b961ac49-5c6956c415e41770.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:13:21Z"
    - latency: 5.835451ms
      message: 'load-balancer-api-internal: tcp connection to ae8637b1c471b4adaab6ad20b961ac49-5c6956c415e41770.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:12:21Z"
    - latency: 6.220479ms
      message: 'load-balancer-api-internal: resolved host name ae8637b1c471b4adaab6ad20b961ac49-5c6956c415e41770.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:12:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:10:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-248-to-network-check-target-ip-10-0-131-229
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-248.ec2.internal
      uid: 1f76bf73-6c16-439e-9399-80b6338b1dc1
    resourceVersion: "10768"
    uid: f94d3d6b-570f-42b3-86e7-137f43d12dea
  spec:
    sourcePod: network-check-source-989f8b8dc-6gn26
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:10:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-248-to-network-check-target-ip-10-0-133-206
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-248.ec2.internal
      uid: 1f76bf73-6c16-439e-9399-80b6338b1dc1
    resourceVersion: "10765"
    uid: 720a06dc-c3b5-4dfc-b542-fbd3483260be
  spec:
    sourcePod: network-check-source-989f8b8dc-6gn26
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:10:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-248-to-network-check-target-ip-10-0-137-248
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-248.ec2.internal
      uid: 1f76bf73-6c16-439e-9399-80b6338b1dc1
    resourceVersion: "10766"
    uid: e7d532f5-9229-4045-91b6-9d4e7e8d1522
  spec:
    sourcePod: network-check-source-989f8b8dc-6gn26
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:10:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-248-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-248.ec2.internal
      uid: 1f76bf73-6c16-439e-9399-80b6338b1dc1
    resourceVersion: "14291"
    uid: 94830e15-4c1c-4365-a8b0-d05489345e1d
  spec:
    sourcePod: network-check-source-989f8b8dc-6gn26
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:16:21Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 748.773µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:16:21Z"
    - latency: 2.010882ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:16:21Z"
    - latency: 925.479µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:15:21Z"
    - latency: 1.711671ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:15:21Z"
    - latency: 932.184µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:14:21Z"
    - latency: 1.833248ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:14:21Z"
    - latency: 848.306µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:13:21Z"
    - latency: 1.637343ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:13:21Z"
    - latency: 1.070133ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:12:21Z"
    - latency: 1.78351ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:12:21Z"
kind: List
metadata:
  resourceVersion: ""