apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:21:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-230-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-230.ec2.internal
      uid: c301c462-6062-422e-9641-5d22f1eb6d45
    resourceVersion: "11261"
    uid: 343c1258-cfd1-4eac-990d-87ea0d3fb400
  spec:
    sourcePod: network-check-source-685456655f-5f72x
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:21:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-230-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-230.ec2.internal
      uid: c301c462-6062-422e-9641-5d22f1eb6d45
    resourceVersion: "14677"
    uid: b8d8a76e-140c-48ec-9d5e-cbafceca5dcf
  spec:
    sourcePod: network-check-source-685456655f-5f72x
    targetEndpoint: a9e36ae6834014d67af2a4a5a812de9a-465e4825d2ecf29a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:27:34Z"
      message: 'load-balancer-api-external: tcp connection to a9e36ae6834014d67af2a4a5a812de9a-465e4825d2ecf29a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.193992ms
      message: 'load-balancer-api-external: tcp connection to a9e36ae6834014d67af2a4a5a812de9a-465e4825d2ecf29a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:27:34Z"
    - latency: 6.430311ms
      message: 'load-balancer-api-external: resolved host name a9e36ae6834014d67af2a4a5a812de9a-465e4825d2ecf29a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:27:34Z"
    - latency: 6.061695ms
      message: 'load-balancer-api-external: tcp connection to a9e36ae6834014d67af2a4a5a812de9a-465e4825d2ecf29a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:26:34Z"
    - latency: 6.978414ms
      message: 'load-balancer-api-external: resolved host name a9e36ae6834014d67af2a4a5a812de9a-465e4825d2ecf29a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:26:34Z"
    - latency: 6.190806ms
      message: 'load-balancer-api-external: tcp connection to a9e36ae6834014d67af2a4a5a812de9a-465e4825d2ecf29a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:34Z"
    - latency: 6.9237ms
      message: 'load-balancer-api-external: resolved host name a9e36ae6834014d67af2a4a5a812de9a-465e4825d2ecf29a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:25:34Z"
    - latency: 4.239848ms
      message: 'load-balancer-api-external: tcp connection to a9e36ae6834014d67af2a4a5a812de9a-465e4825d2ecf29a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:24:34Z"
    - latency: 6.882123ms
      message: 'load-balancer-api-external: resolved host name a9e36ae6834014d67af2a4a5a812de9a-465e4825d2ecf29a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:24:34Z"
    - latency: 5.41665ms
      message: 'load-balancer-api-external: tcp connection to a9e36ae6834014d67af2a4a5a812de9a-465e4825d2ecf29a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:23:34Z"
    - latency: 10.230924ms
      message: 'load-balancer-api-external: resolved host name a9e36ae6834014d67af2a4a5a812de9a-465e4825d2ecf29a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:23:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:21:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-230-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-230.ec2.internal
      uid: c301c462-6062-422e-9641-5d22f1eb6d45
    resourceVersion: "14678"
    uid: 65f9f961-b33d-4d78-a7c4-3ae5bd18614a
  spec:
    sourcePod: network-check-source-685456655f-5f72x
    targetEndpoint: a9e36ae6834014d67af2a4a5a812de9a-465e4825d2ecf29a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:27:34Z"
      message: 'load-balancer-api-internal: tcp connection to a9e36ae6834014d67af2a4a5a812de9a-465e4825d2ecf29a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.970259ms
      message: 'load-balancer-api-internal: tcp connection to a9e36ae6834014d67af2a4a5a812de9a-465e4825d2ecf29a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:27:34Z"
    - latency: 6.519901ms
      message: 'load-balancer-api-internal: resolved host name a9e36ae6834014d67af2a4a5a812de9a-465e4825d2ecf29a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:27:34Z"
    - latency: 6.0609ms
      message: 'load-balancer-api-internal: tcp connection to a9e36ae6834014d67af2a4a5a812de9a-465e4825d2ecf29a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:26:34Z"
    - latency: 7.089035ms
      message: 'load-balancer-api-internal: resolved host name a9e36ae6834014d67af2a4a5a812de9a-465e4825d2ecf29a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:26:34Z"
    - latency: 3.726222ms
      message: 'load-balancer-api-internal: tcp connection to a9e36ae6834014d67af2a4a5a812de9a-465e4825d2ecf29a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:34Z"
    - latency: 7.020484ms
      message: 'load-balancer-api-internal: resolved host name a9e36ae6834014d67af2a4a5a812de9a-465e4825d2ecf29a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:25:34Z"
    - latency: 4.19302ms
      message: 'load-balancer-api-internal: tcp connection to a9e36ae6834014d67af2a4a5a812de9a-465e4825d2ecf29a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:24:34Z"
    - latency: 6.93695ms
      message: 'load-balancer-api-internal: resolved host name a9e36ae6834014d67af2a4a5a812de9a-465e4825d2ecf29a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:24:34Z"
    - latency: 5.172519ms
      message: 'load-balancer-api-internal: tcp connection to a9e36ae6834014d67af2a4a5a812de9a-465e4825d2ecf29a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:23:34Z"
    - latency: 10.217681ms
      message: 'load-balancer-api-internal: resolved host name a9e36ae6834014d67af2a4a5a812de9a-465e4825d2ecf29a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:23:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:21:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-230-to-network-check-target-ip-10-0-130-230
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-230.ec2.internal
      uid: c301c462-6062-422e-9641-5d22f1eb6d45
    resourceVersion: "11268"
    uid: 8293a1c9-9abd-49c1-a63e-078d2e9ae391
  spec:
    sourcePod: network-check-source-685456655f-5f72x
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:21:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-230-to-network-check-target-ip-10-0-135-235
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-230.ec2.internal
      uid: c301c462-6062-422e-9641-5d22f1eb6d45
    resourceVersion: "11260"
    uid: 6e3b5a9e-0561-452f-98d0-c1dcda4acc3b
  spec:
    sourcePod: network-check-source-685456655f-5f72x
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:21:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-230-to-network-check-target-ip-10-0-141-166
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-230.ec2.internal
      uid: c301c462-6062-422e-9641-5d22f1eb6d45
    resourceVersion: "11267"
    uid: b2539a5f-0038-4868-8439-987cf871b095
  spec:
    sourcePod: network-check-source-685456655f-5f72x
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:21:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-230-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-230.ec2.internal
      uid: c301c462-6062-422e-9641-5d22f1eb6d45
    resourceVersion: "14676"
    uid: 8834b213-3347-46fa-ab2a-c03852b3d908
  spec:
    sourcePod: network-check-source-685456655f-5f72x
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:27:34Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 967.021µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:27:34Z"
    - latency: 1.668203ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:27:34Z"
    - latency: 850.038µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:26:34Z"
    - latency: 1.819114ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:26:34Z"
    - latency: 1.049099ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:34Z"
    - latency: 1.891264ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:25:34Z"
    - latency: 927.979µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:24:34Z"
    - latency: 1.74398ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:24:34Z"
    - latency: 940.837µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:23:34Z"
    - latency: 2.070627ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:23:34Z"
kind: List
metadata:
  resourceVersion: ""