apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T16:12:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-70-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-70.ec2.internal
      uid: 1754c6f3-1668-4583-bb6b-a1eb95051612
    resourceVersion: "10981"
    uid: 66c98801-1831-4ae4-b7d0-39c3c3e2ad5a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4zzhc
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T16:12:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-70-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-70.ec2.internal
      uid: 1754c6f3-1668-4583-bb6b-a1eb95051612
    resourceVersion: "14550"
    uid: 0aa9d4e8-1f0a-477d-9f81-1ccfc239c31c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4zzhc
    targetEndpoint: aac6e140f802e41a295eab44d8a6ff71-03cef5c1607cd1e5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T16:18:28Z"
      message: 'load-balancer-api-external: tcp connection to aac6e140f802e41a295eab44d8a6ff71-03cef5c1607cd1e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.638014ms
      message: 'load-balancer-api-external: tcp connection to aac6e140f802e41a295eab44d8a6ff71-03cef5c1607cd1e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:18:28Z"
    - latency: 6.658443ms
      message: 'load-balancer-api-external: resolved host name aac6e140f802e41a295eab44d8a6ff71-03cef5c1607cd1e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:18:28Z"
    - latency: 6.632683ms
      message: 'load-balancer-api-external: tcp connection to aac6e140f802e41a295eab44d8a6ff71-03cef5c1607cd1e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:17:28Z"
    - latency: 6.709119ms
      message: 'load-balancer-api-external: resolved host name aac6e140f802e41a295eab44d8a6ff71-03cef5c1607cd1e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:17:28Z"
    - latency: 5.532944ms
      message: 'load-balancer-api-external: tcp connection to aac6e140f802e41a295eab44d8a6ff71-03cef5c1607cd1e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:16:28Z"
    - latency: 6.611602ms
      message: 'load-balancer-api-external: resolved host name aac6e140f802e41a295eab44d8a6ff71-03cef5c1607cd1e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:16:28Z"
    - latency: 5.232696ms
      message: 'load-balancer-api-external: tcp connection to aac6e140f802e41a295eab44d8a6ff71-03cef5c1607cd1e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:15:28Z"
    - latency: 6.990732ms
      message: 'load-balancer-api-external: resolved host name aac6e140f802e41a295eab44d8a6ff71-03cef5c1607cd1e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:15:28Z"
    - latency: 4.991711ms
      message: 'load-balancer-api-external: tcp connection to aac6e140f802e41a295eab44d8a6ff71-03cef5c1607cd1e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:14:28Z"
    - latency: 6.224621ms
      message: 'load-balancer-api-external: resolved host name aac6e140f802e41a295eab44d8a6ff71-03cef5c1607cd1e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:14:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T16:12:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-70-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-70.ec2.internal
      uid: 1754c6f3-1668-4583-bb6b-a1eb95051612
    resourceVersion: "14549"
    uid: 3c913fc6-0fd4-4c4b-b8a1-cb0b19c8648c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4zzhc
    targetEndpoint: aac6e140f802e41a295eab44d8a6ff71-03cef5c1607cd1e5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T16:18:28Z"
      message: 'load-balancer-api-internal: tcp connection to aac6e140f802e41a295eab44d8a6ff71-03cef5c1607cd1e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.624424ms
      message: 'load-balancer-api-internal: tcp connection to aac6e140f802e41a295eab44d8a6ff71-03cef5c1607cd1e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:18:28Z"
    - latency: 6.591493ms
      message: 'load-balancer-api-internal: resolved host name aac6e140f802e41a295eab44d8a6ff71-03cef5c1607cd1e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:18:28Z"
    - latency: 6.413647ms
      message: 'load-balancer-api-internal: tcp connection to aac6e140f802e41a295eab44d8a6ff71-03cef5c1607cd1e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:17:28Z"
    - latency: 6.73044ms
      message: 'load-balancer-api-internal: resolved host name aac6e140f802e41a295eab44d8a6ff71-03cef5c1607cd1e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:17:28Z"
    - latency: 5.551368ms
      message: 'load-balancer-api-internal: tcp connection to aac6e140f802e41a295eab44d8a6ff71-03cef5c1607cd1e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:16:28Z"
    - latency: 6.628419ms
      message: 'load-balancer-api-internal: resolved host name aac6e140f802e41a295eab44d8a6ff71-03cef5c1607cd1e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:16:28Z"
    - latency: 4.928195ms
      message: 'load-balancer-api-internal: tcp connection to aac6e140f802e41a295eab44d8a6ff71-03cef5c1607cd1e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:15:28Z"
    - latency: 7.029254ms
      message: 'load-balancer-api-internal: resolved host name aac6e140f802e41a295eab44d8a6ff71-03cef5c1607cd1e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:15:28Z"
    - latency: 4.198408ms
      message: 'load-balancer-api-internal: tcp connection to aac6e140f802e41a295eab44d8a6ff71-03cef5c1607cd1e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:14:28Z"
    - latency: 6.128151ms
      message: 'load-balancer-api-internal: resolved host name aac6e140f802e41a295eab44d8a6ff71-03cef5c1607cd1e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:14:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T16:12:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-70-to-network-check-target-ip-10-0-133-31
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-70.ec2.internal
      uid: 1754c6f3-1668-4583-bb6b-a1eb95051612
    resourceVersion: "10977"
    uid: cb5cbe3c-ea3c-4b69-ad37-3eb7e008c44d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4zzhc
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T16:12:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-70-to-network-check-target-ip-10-0-138-156
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-70.ec2.internal
      uid: 1754c6f3-1668-4583-bb6b-a1eb95051612
    resourceVersion: "10979"
    uid: 7720abf5-71dd-460a-b201-47ff8d578eee
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4zzhc
    targetEndpoint: 10.134.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T16:12:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-70-to-network-check-target-ip-10-0-140-70
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-70.ec2.internal
      uid: 1754c6f3-1668-4583-bb6b-a1eb95051612
    resourceVersion: "10978"
    uid: bb8bac66-46ac-4ceb-adaa-7b3ee2446d54
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4zzhc
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T16:12:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-70-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-70.ec2.internal
      uid: 1754c6f3-1668-4583-bb6b-a1eb95051612
    resourceVersion: "14547"
    uid: 3dfe1569-f431-429b-848f-86cf8fa6d164
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4zzhc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T16:18:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 899.661µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:18:28Z"
    - latency: 1.929968ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:18:28Z"
    - latency: 798.662µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:17:28Z"
    - latency: 1.661322ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:17:28Z"
    - latency: 839.169µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:16:28Z"
    - latency: 2.199495ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:16:28Z"
    - latency: 786.082µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:15:28Z"
    - latency: 1.891106ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:15:28Z"
    - latency: 1.126233ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:14:28Z"
    - latency: 1.517573ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:14:28Z"
kind: List
metadata:
  resourceVersion: ""