apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T22:47:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-65-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-65.ec2.internal
      uid: d81ca099-20be-449a-b67a-67f82ef58f75
    resourceVersion: "23654"
    uid: d17532c6-6308-429a-98a2-10e939dc86a6
  spec:
    sourcePod: network-check-source-dbd9cf844-s9fxz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T22:54:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.064319ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:54:52Z"
    - latency: 10.395191ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:53:52Z"
    - latency: 1.139323ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:52:52Z"
    - latency: 1.348279ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:51:52Z"
    - latency: 1.013134ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:50:52Z"
    - latency: 1.087862ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:49:52Z"
    - latency: 1.160838ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:48:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T22:47:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-65-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-65.ec2.internal
      uid: d81ca099-20be-449a-b67a-67f82ef58f75
    resourceVersion: "22572"
    uid: b5beecdf-5252-40ca-80c7-b1f1dd5b41b7
  spec:
    sourcePod: network-check-source-dbd9cf844-s9fxz
    targetEndpoint: a8e69c57780ee447a8db53c4617b91bf-59063dbf9ec991a1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T22:53:52Z"
      message: 'load-balancer-api-external: tcp connection to a8e69c57780ee447a8db53c4617b91bf-59063dbf9ec991a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.863808ms
      message: 'load-balancer-api-external: tcp connection to a8e69c57780ee447a8db53c4617b91bf-59063dbf9ec991a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:53:52Z"
    - latency: 31.719688ms
      message: 'load-balancer-api-external: resolved host name a8e69c57780ee447a8db53c4617b91bf-59063dbf9ec991a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:53:52Z"
    - latency: 4.971902ms
      message: 'load-balancer-api-external: tcp connection to a8e69c57780ee447a8db53c4617b91bf-59063dbf9ec991a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:52:52Z"
    - latency: 7.865443ms
      message: 'load-balancer-api-external: resolved host name a8e69c57780ee447a8db53c4617b91bf-59063dbf9ec991a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:52:52Z"
    - latency: 5.345977ms
      message: 'load-balancer-api-external: tcp connection to a8e69c57780ee447a8db53c4617b91bf-59063dbf9ec991a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:51:52Z"
    - latency: 6.862565ms
      message: 'load-balancer-api-external: resolved host name a8e69c57780ee447a8db53c4617b91bf-59063dbf9ec991a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:51:52Z"
    - latency: 4.493796ms
      message: 'load-balancer-api-external: tcp connection to a8e69c57780ee447a8db53c4617b91bf-59063dbf9ec991a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:50:52Z"
    - latency: 6.382667ms
      message: 'load-balancer-api-external: resolved host name a8e69c57780ee447a8db53c4617b91bf-59063dbf9ec991a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:50:52Z"
    - latency: 4.99329ms
      message: 'load-balancer-api-external: tcp connection to a8e69c57780ee447a8db53c4617b91bf-59063dbf9ec991a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:49:52Z"
    - latency: 7.214793ms
      message: 'load-balancer-api-external: resolved host name a8e69c57780ee447a8db53c4617b91bf-59063dbf9ec991a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:49:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T22:47:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-65-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-65.ec2.internal
      uid: d81ca099-20be-449a-b67a-67f82ef58f75
    resourceVersion: "22571"
    uid: 4b1228cf-009c-4d6a-8763-0fcc9d003024
  spec:
    sourcePod: network-check-source-dbd9cf844-s9fxz
    targetEndpoint: a8e69c57780ee447a8db53c4617b91bf-59063dbf9ec991a1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T22:53:52Z"
      message: 'load-balancer-api-internal: tcp connection to a8e69c57780ee447a8db53c4617b91bf-59063dbf9ec991a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.85409ms
      message: 'load-balancer-api-internal: tcp connection to a8e69c57780ee447a8db53c4617b91bf-59063dbf9ec991a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:53:52Z"
    - latency: 25.832593ms
      message: 'load-balancer-api-internal: resolved host name a8e69c57780ee447a8db53c4617b91bf-59063dbf9ec991a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:53:52Z"
    - latency: 4.98564ms
      message: 'load-balancer-api-internal: tcp connection to a8e69c57780ee447a8db53c4617b91bf-59063dbf9ec991a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:52:52Z"
    - latency: 7.912933ms
      message: 'load-balancer-api-internal: resolved host name a8e69c57780ee447a8db53c4617b91bf-59063dbf9ec991a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:52:52Z"
    - latency: 5.047497ms
      message: 'load-balancer-api-internal: tcp connection to a8e69c57780ee447a8db53c4617b91bf-59063dbf9ec991a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:51:52Z"
    - latency: 6.818055ms
      message: 'load-balancer-api-internal: resolved host name a8e69c57780ee447a8db53c4617b91bf-59063dbf9ec991a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:51:52Z"
    - latency: 3.219555ms
      message: 'load-balancer-api-internal: tcp connection to a8e69c57780ee447a8db53c4617b91bf-59063dbf9ec991a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:50:52Z"
    - latency: 6.407894ms
      message: 'load-balancer-api-internal: resolved host name a8e69c57780ee447a8db53c4617b91bf-59063dbf9ec991a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:50:52Z"
    - latency: 5.334148ms
      message: 'load-balancer-api-internal: tcp connection to a8e69c57780ee447a8db53c4617b91bf-59063dbf9ec991a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:49:52Z"
    - latency: 7.342726ms
      message: 'load-balancer-api-internal: resolved host name a8e69c57780ee447a8db53c4617b91bf-59063dbf9ec991a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:49:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T22:47:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-65-to-network-check-target-ip-10-0-130-215
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-65.ec2.internal
      uid: d81ca099-20be-449a-b67a-67f82ef58f75
    resourceVersion: "23653"
    uid: 88cfea68-e1ad-4459-8b7b-88fcef829b9a
  spec:
    sourcePod: network-check-source-dbd9cf844-s9fxz
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T22:54:52Z"
      message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.252887ms
      message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:54:52Z"
    - latency: 3.682119ms
      message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:53:52Z"
    - latency: 2.289463ms
      message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:52:52Z"
    - latency: 2.073706ms
      message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:51:52Z"
    - latency: 2.369126ms
      message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:50:52Z"
    - latency: 2.332631ms
      message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:49:52Z"
    - latency: 1.737799ms
      message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:48:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T22:47:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-65-to-network-check-target-ip-10-0-132-244
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-65.ec2.internal
      uid: d81ca099-20be-449a-b67a-67f82ef58f75
    resourceVersion: "23652"
    uid: 612f3f7d-e99a-4c38-817c-5597d57d8a88
  spec:
    sourcePod: network-check-source-dbd9cf844-s9fxz
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T22:54:52Z"
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.758867ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:54:52Z"
    - latency: 3.358981ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:53:52Z"
    - latency: 2.214422ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:52:52Z"
    - latency: 2.33407ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:51:52Z"
    - latency: 2.295232ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:50:52Z"
    - latency: 2.366367ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:49:52Z"
    - latency: 2.453758ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:48:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T22:47:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-65-to-network-check-target-ip-10-0-137-65
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-65.ec2.internal
      uid: d81ca099-20be-449a-b67a-67f82ef58f75
    resourceVersion: "23651"
    uid: ef4d4785-92c3-41ff-acef-af9fd31d2f36
  spec:
    sourcePod: network-check-source-dbd9cf844-s9fxz
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T22:54:52Z"
      message: 'network-check-target-ip-10-0-137-65: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 805.993µs
      message: 'network-check-target-ip-10-0-137-65: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:54:52Z"
    - latency: 1.561697ms
      message: 'network-check-target-ip-10-0-137-65: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:53:52Z"
    - latency: 998.362µs
      message: 'network-check-target-ip-10-0-137-65: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:52:52Z"
    - latency: 967.423µs
      message: 'network-check-target-ip-10-0-137-65: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:51:52Z"
    - latency: 949.299µs
      message: 'network-check-target-ip-10-0-137-65: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:50:52Z"
    - latency: 1.202254ms
      message: 'network-check-target-ip-10-0-137-65: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:49:52Z"
    - latency: 1.558786ms
      message: 'network-check-target-ip-10-0-137-65: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:48:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T22:47:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-65-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-65.ec2.internal
      uid: d81ca099-20be-449a-b67a-67f82ef58f75
    resourceVersion: "22570"
    uid: 83ce6cb9-74ce-4740-a908-ebdd4f4c021f
  spec:
    sourcePod: network-check-source-dbd9cf844-s9fxz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T22:53:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.871568ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:53:52Z"
    - latency: 4.645186ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:53:52Z"
    - latency: 730.817µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:52:52Z"
    - latency: 2.026481ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:52:52Z"
    - latency: 1.02729ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:51:52Z"
    - latency: 1.805964ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:51:52Z"
    - latency: 805.867µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:50:52Z"
    - latency: 1.738301ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:50:52Z"
    - latency: 1.074078ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:49:52Z"
    - latency: 1.679847ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:49:52Z"
kind: List
metadata:
  resourceVersion: ""