apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:13:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-65-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-65.ec2.internal
      uid: ec776f51-6358-4aae-b108-bf6902f1d004
    resourceVersion: "14356"
    uid: 4f5bfd4c-46fe-4265-be1f-bb4d03332d5a
  spec:
    sourcePod: network-check-source-869dcfcdcd-2xjb6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:20:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.102555ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:20:04Z"
    - latency: 1.059749ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:19:04Z"
    - latency: 1.078303ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:18:04Z"
    - latency: 1.202954ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:17:04Z"
    - latency: 978.085µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:16:04Z"
    - latency: 992.604µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:15:04Z"
    - latency: 1.047369ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:14:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:13:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-65-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-65.ec2.internal
      uid: ec776f51-6358-4aae-b108-bf6902f1d004
    resourceVersion: "14026"
    uid: 98c85837-b959-4c91-bba9-ac5f1318cb57
  spec:
    sourcePod: network-check-source-869dcfcdcd-2xjb6
    targetEndpoint: a093b5de068f44a72a8d5c8a209e870e-4f06a8fcb5d06d68.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:19:04Z"
      message: 'load-balancer-api-external: tcp connection to a093b5de068f44a72a8d5c8a209e870e-4f06a8fcb5d06d68.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.673466ms
      message: 'load-balancer-api-external: tcp connection to a093b5de068f44a72a8d5c8a209e870e-4f06a8fcb5d06d68.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:19:04Z"
    - latency: 7.843576ms
      message: 'load-balancer-api-external: resolved host name a093b5de068f44a72a8d5c8a209e870e-4f06a8fcb5d06d68.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:19:04Z"
    - latency: 4.365839ms
      message: 'load-balancer-api-external: tcp connection to a093b5de068f44a72a8d5c8a209e870e-4f06a8fcb5d06d68.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:18:04Z"
    - latency: 8.582211ms
      message: 'load-balancer-api-external: resolved host name a093b5de068f44a72a8d5c8a209e870e-4f06a8fcb5d06d68.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:18:04Z"
    - latency: 5.646747ms
      message: 'load-balancer-api-external: tcp connection to a093b5de068f44a72a8d5c8a209e870e-4f06a8fcb5d06d68.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:17:04Z"
    - latency: 8.490499ms
      message: 'load-balancer-api-external: resolved host name a093b5de068f44a72a8d5c8a209e870e-4f06a8fcb5d06d68.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:17:04Z"
    - latency: 4.878401ms
      message: 'load-balancer-api-external: tcp connection to a093b5de068f44a72a8d5c8a209e870e-4f06a8fcb5d06d68.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:16:04Z"
    - latency: 8.541269ms
      message: 'load-balancer-api-external: resolved host name a093b5de068f44a72a8d5c8a209e870e-4f06a8fcb5d06d68.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:16:04Z"
    - latency: 4.850539ms
      message: 'load-balancer-api-external: tcp connection to a093b5de068f44a72a8d5c8a209e870e-4f06a8fcb5d06d68.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:15:04Z"
    - latency: 11.829079ms
      message: 'load-balancer-api-external: resolved host name a093b5de068f44a72a8d5c8a209e870e-4f06a8fcb5d06d68.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:15:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:13:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-65-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-65.ec2.internal
      uid: ec776f51-6358-4aae-b108-bf6902f1d004
    resourceVersion: "14025"
    uid: 0e386310-c4fb-4cd4-8b70-e15c2fe03200
  spec:
    sourcePod: network-check-source-869dcfcdcd-2xjb6
    targetEndpoint: a093b5de068f44a72a8d5c8a209e870e-4f06a8fcb5d06d68.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:19:04Z"
      message: 'load-balancer-api-internal: tcp connection to a093b5de068f44a72a8d5c8a209e870e-4f06a8fcb5d06d68.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.294729ms
      message: 'load-balancer-api-internal: tcp connection to a093b5de068f44a72a8d5c8a209e870e-4f06a8fcb5d06d68.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:19:04Z"
    - latency: 7.816901ms
      message: 'load-balancer-api-internal: resolved host name a093b5de068f44a72a8d5c8a209e870e-4f06a8fcb5d06d68.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:19:04Z"
    - latency: 4.340081ms
      message: 'load-balancer-api-internal: tcp connection to a093b5de068f44a72a8d5c8a209e870e-4f06a8fcb5d06d68.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:18:04Z"
    - latency: 8.482527ms
      message: 'load-balancer-api-internal: resolved host name a093b5de068f44a72a8d5c8a209e870e-4f06a8fcb5d06d68.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:18:04Z"
    - latency: 4.521962ms
      message: 'load-balancer-api-internal: tcp connection to a093b5de068f44a72a8d5c8a209e870e-4f06a8fcb5d06d68.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:17:04Z"
    - latency: 8.620335ms
      message: 'load-balancer-api-internal: resolved host name a093b5de068f44a72a8d5c8a209e870e-4f06a8fcb5d06d68.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:17:04Z"
    - latency: 5.0268ms
      message: 'load-balancer-api-internal: tcp connection to a093b5de068f44a72a8d5c8a209e870e-4f06a8fcb5d06d68.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:16:04Z"
    - latency: 8.485779ms
      message: 'load-balancer-api-internal: resolved host name a093b5de068f44a72a8d5c8a209e870e-4f06a8fcb5d06d68.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:16:04Z"
    - latency: 4.176053ms
      message: 'load-balancer-api-internal: tcp connection to a093b5de068f44a72a8d5c8a209e870e-4f06a8fcb5d06d68.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:15:04Z"
    - latency: 11.73999ms
      message: 'load-balancer-api-internal: resolved host name a093b5de068f44a72a8d5c8a209e870e-4f06a8fcb5d06d68.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:15:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:13:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-65-to-network-check-target-ip-10-0-128-12
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-65.ec2.internal
      uid: ec776f51-6358-4aae-b108-bf6902f1d004
    resourceVersion: "14354"
    uid: efc1b15f-e7e4-4e96-9580-db53e1d559c0
  spec:
    sourcePod: network-check-source-869dcfcdcd-2xjb6
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:20:04Z"
      message: 'network-check-target-ip-10-0-128-12: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.298173ms
      message: 'network-check-target-ip-10-0-128-12: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:20:04Z"
    - latency: 2.421467ms
      message: 'network-check-target-ip-10-0-128-12: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:19:04Z"
    - latency: 2.240373ms
      message: 'network-check-target-ip-10-0-128-12: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:18:04Z"
    - latency: 1.951431ms
      message: 'network-check-target-ip-10-0-128-12: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:17:04Z"
    - latency: 2.109063ms
      message: 'network-check-target-ip-10-0-128-12: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:16:04Z"
    - latency: 2.865188ms
      message: 'network-check-target-ip-10-0-128-12: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:15:04Z"
    - latency: 2.467183ms
      message: 'network-check-target-ip-10-0-128-12: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:14:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:13:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-65-to-network-check-target-ip-10-0-133-40
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-65.ec2.internal
      uid: ec776f51-6358-4aae-b108-bf6902f1d004
    resourceVersion: "14355"
    uid: 854fa473-f9c0-4b6e-afe5-2309b8d98626
  spec:
    sourcePod: network-check-source-869dcfcdcd-2xjb6
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:20:04Z"
      message: 'network-check-target-ip-10-0-133-40: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.065248ms
      message: 'network-check-target-ip-10-0-133-40: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:20:04Z"
    - latency: 2.458256ms
      message: 'network-check-target-ip-10-0-133-40: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:19:04Z"
    - latency: 2.31368ms
      message: 'network-check-target-ip-10-0-133-40: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:18:04Z"
    - latency: 2.204647ms
      message: 'network-check-target-ip-10-0-133-40: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:17:04Z"
    - latency: 2.109073ms
      message: 'network-check-target-ip-10-0-133-40: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:16:04Z"
    - latency: 2.918458ms
      message: 'network-check-target-ip-10-0-133-40: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:15:04Z"
    - latency: 2.796269ms
      message: 'network-check-target-ip-10-0-133-40: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:14:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:13:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-65-to-network-check-target-ip-10-0-138-65
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-65.ec2.internal
      uid: ec776f51-6358-4aae-b108-bf6902f1d004
    resourceVersion: "14353"
    uid: 7b4a2b87-de65-4181-bda2-1b70d8c78912
  spec:
    sourcePod: network-check-source-869dcfcdcd-2xjb6
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:20:04Z"
      message: 'network-check-target-ip-10-0-138-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 951.484µs
      message: 'network-check-target-ip-10-0-138-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:20:04Z"
    - latency: 1.025092ms
      message: 'network-check-target-ip-10-0-138-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:19:04Z"
    - latency: 854.945µs
      message: 'network-check-target-ip-10-0-138-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:18:04Z"
    - latency: 930.958µs
      message: 'network-check-target-ip-10-0-138-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:17:04Z"
    - latency: 826.71µs
      message: 'network-check-target-ip-10-0-138-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:16:04Z"
    - latency: 929.385µs
      message: 'network-check-target-ip-10-0-138-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:15:04Z"
    - latency: 1.315211ms
      message: 'network-check-target-ip-10-0-138-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:14:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:13:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-65-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-65.ec2.internal
      uid: ec776f51-6358-4aae-b108-bf6902f1d004
    resourceVersion: "14024"
    uid: d32df774-225c-477c-b4d5-f91cfe3adabe
  spec:
    sourcePod: network-check-source-869dcfcdcd-2xjb6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:19:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 798.938µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:19:04Z"
    - latency: 1.791435ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:19:04Z"
    - latency: 1.219068ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:18:04Z"
    - latency: 1.756877ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:18:04Z"
    - latency: 935.028µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:17:04Z"
    - latency: 2.013518ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:17:04Z"
    - latency: 932.367µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:16:04Z"
    - latency: 1.763358ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:16:04Z"
    - latency: 1.079523ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:15:04Z"
    - latency: 2.734557ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:15:04Z"
kind: List
metadata:
  resourceVersion: ""