apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T08:06:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-60-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-60.ec2.internal
      uid: ac0be1f2-c169-49e1-b236-cb405a206b2f
    resourceVersion: "11243"
    uid: 357a0d08-9e97-477d-b403-375db6c27b1b
  spec:
    sourcePod: network-check-source-7d88cb55d8-np45r
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T08:06:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-60-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-60.ec2.internal
      uid: ac0be1f2-c169-49e1-b236-cb405a206b2f
    resourceVersion: "22234"
    uid: d71e85bb-fe1b-4a42-ae24-fe14df6124ed
  spec:
    sourcePod: network-check-source-7d88cb55d8-np45r
    targetEndpoint: a951d1b710c124aff8425e03ae6cda87-5ce2cf440c45a85d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T08:12:08Z"
      message: 'load-balancer-api-external: tcp connection to a951d1b710c124aff8425e03ae6cda87-5ce2cf440c45a85d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.410209ms
      message: 'load-balancer-api-external: tcp connection to a951d1b710c124aff8425e03ae6cda87-5ce2cf440c45a85d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:12:08Z"
    - latency: 9.267128ms
      message: 'load-balancer-api-external: resolved host name a951d1b710c124aff8425e03ae6cda87-5ce2cf440c45a85d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:12:08Z"
    - latency: 4.802896ms
      message: 'load-balancer-api-external: tcp connection to a951d1b710c124aff8425e03ae6cda87-5ce2cf440c45a85d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:11:08Z"
    - latency: 9.561044ms
      message: 'load-balancer-api-external: resolved host name a951d1b710c124aff8425e03ae6cda87-5ce2cf440c45a85d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:11:08Z"
    - latency: 5.713388ms
      message: 'load-balancer-api-external: tcp connection to a951d1b710c124aff8425e03ae6cda87-5ce2cf440c45a85d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:10:08Z"
    - latency: 9.422055ms
      message: 'load-balancer-api-external: resolved host name a951d1b710c124aff8425e03ae6cda87-5ce2cf440c45a85d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:10:08Z"
    - latency: 4.800181ms
      message: 'load-balancer-api-external: tcp connection to a951d1b710c124aff8425e03ae6cda87-5ce2cf440c45a85d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:09:08Z"
    - latency: 8.497822ms
      message: 'load-balancer-api-external: resolved host name a951d1b710c124aff8425e03ae6cda87-5ce2cf440c45a85d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:09:08Z"
    - latency: 3.737871ms
      message: 'load-balancer-api-external: tcp connection to a951d1b710c124aff8425e03ae6cda87-5ce2cf440c45a85d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:08:08Z"
    - latency: 15.863829ms
      message: 'load-balancer-api-external: resolved host name a951d1b710c124aff8425e03ae6cda87-5ce2cf440c45a85d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:08:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T08:06:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-60-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-60.ec2.internal
      uid: ac0be1f2-c169-49e1-b236-cb405a206b2f
    resourceVersion: "22233"
    uid: 9d89c4b8-5b4b-4486-8170-a3aa1301230b
  spec:
    sourcePod: network-check-source-7d88cb55d8-np45r
    targetEndpoint: a951d1b710c124aff8425e03ae6cda87-5ce2cf440c45a85d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T08:12:08Z"
      message: 'load-balancer-api-internal: tcp connection to a951d1b710c124aff8425e03ae6cda87-5ce2cf440c45a85d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.189756ms
      message: 'load-balancer-api-internal: tcp connection to a951d1b710c124aff8425e03ae6cda87-5ce2cf440c45a85d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:12:08Z"
    - latency: 9.365936ms
      message: 'load-balancer-api-internal: resolved host name a951d1b710c124aff8425e03ae6cda87-5ce2cf440c45a85d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:12:08Z"
    - latency: 4.38242ms
      message: 'load-balancer-api-internal: tcp connection to a951d1b710c124aff8425e03ae6cda87-5ce2cf440c45a85d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:11:08Z"
    - latency: 9.651377ms
      message: 'load-balancer-api-internal: resolved host name a951d1b710c124aff8425e03ae6cda87-5ce2cf440c45a85d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:11:08Z"
    - latency: 5.589953ms
      message: 'load-balancer-api-internal: tcp connection to a951d1b710c124aff8425e03ae6cda87-5ce2cf440c45a85d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:10:08Z"
    - latency: 9.516192ms
      message: 'load-balancer-api-internal: resolved host name a951d1b710c124aff8425e03ae6cda87-5ce2cf440c45a85d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:10:08Z"
    - latency: 5.106075ms
      message: 'load-balancer-api-internal: tcp connection to a951d1b710c124aff8425e03ae6cda87-5ce2cf440c45a85d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:09:08Z"
    - latency: 8.709721ms
      message: 'load-balancer-api-internal: resolved host name a951d1b710c124aff8425e03ae6cda87-5ce2cf440c45a85d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:09:08Z"
    - latency: 3.747393ms
      message: 'load-balancer-api-internal: tcp connection to a951d1b710c124aff8425e03ae6cda87-5ce2cf440c45a85d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:08:08Z"
    - latency: 16.580965ms
      message: 'load-balancer-api-internal: resolved host name a951d1b710c124aff8425e03ae6cda87-5ce2cf440c45a85d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:08:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T08:06:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-60-to-network-check-target-ip-10-0-130-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-60.ec2.internal
      uid: ac0be1f2-c169-49e1-b236-cb405a206b2f
    resourceVersion: "11242"
    uid: 0df061b7-d43d-4d6d-967a-97d407ae21af
  spec:
    sourcePod: network-check-source-7d88cb55d8-np45r
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T08:06:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-60-to-network-check-target-ip-10-0-134-85
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-60.ec2.internal
      uid: ac0be1f2-c169-49e1-b236-cb405a206b2f
    resourceVersion: "11239"
    uid: 0f697cf6-4fe9-47a4-978b-421a7fbfbdda
  spec:
    sourcePod: network-check-source-7d88cb55d8-np45r
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T08:06:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-60-to-network-check-target-ip-10-0-139-60
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-60.ec2.internal
      uid: ac0be1f2-c169-49e1-b236-cb405a206b2f
    resourceVersion: "11247"
    uid: 41c385ed-49e3-4385-b6d5-912e7fe203fc
  spec:
    sourcePod: network-check-source-7d88cb55d8-np45r
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T08:06:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-60-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-60.ec2.internal
      uid: ac0be1f2-c169-49e1-b236-cb405a206b2f
    resourceVersion: "22232"
    uid: 2ddbe028-0f5f-40a2-aa83-ad84b41ea2a8
  spec:
    sourcePod: network-check-source-7d88cb55d8-np45r
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T08:12:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.215357ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:12:08Z"
    - latency: 2.01805ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:12:08Z"
    - latency: 1.08579ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:11:08Z"
    - latency: 1.627524ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:11:08Z"
    - latency: 869.526µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:10:08Z"
    - latency: 2.22622ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:10:08Z"
    - latency: 1.004057ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:09:08Z"
    - latency: 2.226367ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:09:08Z"
    - latency: 1.211783ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:08:08Z"
    - latency: 1.605824ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:08:08Z"
kind: List
metadata:
  resourceVersion: ""