apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T14:39:56Z"
    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: 55f09199-52b5-4567-9ef2-fa969f940e8a
    resourceVersion: "14458"
    uid: 5d7f4c70-0fbd-4590-a8bb-e4f9eec6d108
  spec:
    sourcePod: network-check-source-56d84b9f44-79l9w
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T14:46:57Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 844.583µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:46:57Z"
    - latency: 871.097µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:45:57Z"
    - latency: 1.020385ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:44:57Z"
    - latency: 1.215774ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:43:57Z"
    - latency: 819.544µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:42:57Z"
    - latency: 858.82µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:41:57Z"
    - latency: 1.097361ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:40:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T14:39:56Z"
    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: 55f09199-52b5-4567-9ef2-fa969f940e8a
    resourceVersion: "16205"
    uid: ab23e905-f6c8-40c8-a08f-bf86c364988e
  spec:
    sourcePod: network-check-source-56d84b9f44-79l9w
    targetEndpoint: ab4c493f1462c4d4ab384549034b71a1-8af2405c0314cb54.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T14:45:57Z"
      message: 'load-balancer-api-external: tcp connection to ab4c493f1462c4d4ab384549034b71a1-8af2405c0314cb54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.852296ms
      message: 'load-balancer-api-external: tcp connection to ab4c493f1462c4d4ab384549034b71a1-8af2405c0314cb54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:51:57Z"
    - latency: 8.059587ms
      message: 'load-balancer-api-external: resolved host name ab4c493f1462c4d4ab384549034b71a1-8af2405c0314cb54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:51:57Z"
    - latency: 3.893907ms
      message: 'load-balancer-api-external: tcp connection to ab4c493f1462c4d4ab384549034b71a1-8af2405c0314cb54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:50:57Z"
    - latency: 6.138279ms
      message: 'load-balancer-api-external: resolved host name ab4c493f1462c4d4ab384549034b71a1-8af2405c0314cb54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:50:57Z"
    - latency: 4.2122ms
      message: 'load-balancer-api-external: tcp connection to ab4c493f1462c4d4ab384549034b71a1-8af2405c0314cb54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:49:57Z"
    - latency: 10.940773ms
      message: 'load-balancer-api-external: resolved host name ab4c493f1462c4d4ab384549034b71a1-8af2405c0314cb54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:49:57Z"
    - latency: 4.448681ms
      message: 'load-balancer-api-external: tcp connection to ab4c493f1462c4d4ab384549034b71a1-8af2405c0314cb54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:48:57Z"
    - latency: 7.361058ms
      message: 'load-balancer-api-external: resolved host name ab4c493f1462c4d4ab384549034b71a1-8af2405c0314cb54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:48:57Z"
    - latency: 4.356314ms
      message: 'load-balancer-api-external: tcp connection to ab4c493f1462c4d4ab384549034b71a1-8af2405c0314cb54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:47:57Z"
    - latency: 6.380137ms
      message: 'load-balancer-api-external: resolved host name ab4c493f1462c4d4ab384549034b71a1-8af2405c0314cb54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:47:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T14:39:56Z"
    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: 55f09199-52b5-4567-9ef2-fa969f940e8a
    resourceVersion: "16206"
    uid: 573aa50e-69ab-4a46-be22-ecc338ca458a
  spec:
    sourcePod: network-check-source-56d84b9f44-79l9w
    targetEndpoint: ab4c493f1462c4d4ab384549034b71a1-8af2405c0314cb54.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T14:45:57Z"
      message: 'load-balancer-api-internal: tcp connection to ab4c493f1462c4d4ab384549034b71a1-8af2405c0314cb54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.393626ms
      message: 'load-balancer-api-internal: tcp connection to ab4c493f1462c4d4ab384549034b71a1-8af2405c0314cb54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:51:57Z"
    - latency: 8.000723ms
      message: 'load-balancer-api-internal: resolved host name ab4c493f1462c4d4ab384549034b71a1-8af2405c0314cb54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:51:57Z"
    - latency: 3.855013ms
      message: 'load-balancer-api-internal: tcp connection to ab4c493f1462c4d4ab384549034b71a1-8af2405c0314cb54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:50:57Z"
    - latency: 6.124071ms
      message: 'load-balancer-api-internal: resolved host name ab4c493f1462c4d4ab384549034b71a1-8af2405c0314cb54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:50:57Z"
    - latency: 4.218285ms
      message: 'load-balancer-api-internal: tcp connection to ab4c493f1462c4d4ab384549034b71a1-8af2405c0314cb54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:49:57Z"
    - latency: 10.883308ms
      message: 'load-balancer-api-internal: resolved host name ab4c493f1462c4d4ab384549034b71a1-8af2405c0314cb54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:49:57Z"
    - latency: 3.558424ms
      message: 'load-balancer-api-internal: tcp connection to ab4c493f1462c4d4ab384549034b71a1-8af2405c0314cb54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:48:57Z"
    - latency: 7.300191ms
      message: 'load-balancer-api-internal: resolved host name ab4c493f1462c4d4ab384549034b71a1-8af2405c0314cb54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:48:57Z"
    - latency: 4.365123ms
      message: 'load-balancer-api-internal: tcp connection to ab4c493f1462c4d4ab384549034b71a1-8af2405c0314cb54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:47:57Z"
    - latency: 6.347163ms
      message: 'load-balancer-api-internal: resolved host name ab4c493f1462c4d4ab384549034b71a1-8af2405c0314cb54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:47:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T14:39:56Z"
    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-128-220
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-60.ec2.internal
      uid: 55f09199-52b5-4567-9ef2-fa969f940e8a
    resourceVersion: "14456"
    uid: c738962b-3b10-4661-9618-50d6075d595a
  spec:
    sourcePod: network-check-source-56d84b9f44-79l9w
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T14:46:57Z"
      message: 'network-check-target-ip-10-0-128-220: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.275427ms
      message: 'network-check-target-ip-10-0-128-220: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:46:57Z"
    - latency: 1.893556ms
      message: 'network-check-target-ip-10-0-128-220: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:45:57Z"
    - latency: 2.372372ms
      message: 'network-check-target-ip-10-0-128-220: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:44:57Z"
    - latency: 2.044928ms
      message: 'network-check-target-ip-10-0-128-220: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:43:57Z"
    - latency: 2.059121ms
      message: 'network-check-target-ip-10-0-128-220: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:42:57Z"
    - latency: 2.190157ms
      message: 'network-check-target-ip-10-0-128-220: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:41:57Z"
    - latency: 2.431852ms
      message: 'network-check-target-ip-10-0-128-220: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:40:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T14:39:56Z"
    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: 55f09199-52b5-4567-9ef2-fa969f940e8a
    resourceVersion: "14455"
    uid: 0a6f869a-8b18-4708-b99e-a1386dc5c060
  spec:
    sourcePod: network-check-source-56d84b9f44-79l9w
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T14:46:57Z"
      message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 867.922µs
      message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:46:57Z"
    - latency: 869.334µs
      message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:45:57Z"
    - latency: 943.476µs
      message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:44:57Z"
    - latency: 1.349623ms
      message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:43:57Z"
    - latency: 1.056415ms
      message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:42:57Z"
    - latency: 1.473919ms
      message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:41:57Z"
    - latency: 1.33377ms
      message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:40:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T14:39:56Z"
    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-141-41
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-60.ec2.internal
      uid: 55f09199-52b5-4567-9ef2-fa969f940e8a
    resourceVersion: "14457"
    uid: e2758b09-90c9-43f7-bcdb-28db2ad50133
  spec:
    sourcePod: network-check-source-56d84b9f44-79l9w
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T14:46:57Z"
      message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.040401ms
      message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:46:57Z"
    - latency: 1.805832ms
      message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:45:57Z"
    - latency: 1.778138ms
      message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:44:57Z"
    - latency: 1.730662ms
      message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:43:57Z"
    - latency: 1.977656ms
      message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:42:57Z"
    - latency: 1.976835ms
      message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:41:57Z"
    - latency: 2.389924ms
      message: 'network-check-target-ip-10-0-141-41: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:40:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T14:39:56Z"
    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: 55f09199-52b5-4567-9ef2-fa969f940e8a
    resourceVersion: "16204"
    uid: b3dc87b2-2934-4f5a-8484-81b659e55b22
  spec:
    sourcePod: network-check-source-56d84b9f44-79l9w
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T14:45:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 814.045µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:51:57Z"
    - latency: 1.966694ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:51:57Z"
    - latency: 848.612µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:50:57Z"
    - latency: 1.717514ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:50:57Z"
    - latency: 1.049261ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:49:57Z"
    - latency: 1.739556ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:49:57Z"
    - latency: 863.256µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:48:57Z"
    - latency: 2.412605ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:48:57Z"
    - latency: 1.084891ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:47:57Z"
    - latency: 1.733363ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:47:57Z"
kind: List
metadata:
  resourceVersion: ""