apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T17:28:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-56-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-56.ec2.internal
      uid: 4b7f058a-b8fa-4524-9c2a-323559f950bb
    resourceVersion: "12395"
    uid: 5ce932f9-94c2-42eb-9aae-ec5f383528e5
  spec:
    sourcePod: network-check-source-dbd9cf844-vxt5g
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T17:28:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-56-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-56.ec2.internal
      uid: 4b7f058a-b8fa-4524-9c2a-323559f950bb
    resourceVersion: "14008"
    uid: 3f89d1cb-796f-45ba-bef7-06bcacbee3af
  spec:
    sourcePod: network-check-source-dbd9cf844-vxt5g
    targetEndpoint: aa50f1043216944b980ae0cca8d6495a-52d24c534d2d3655.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T17:34:48Z"
      message: 'load-balancer-api-external: tcp connection to aa50f1043216944b980ae0cca8d6495a-52d24c534d2d3655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.660653ms
      message: 'load-balancer-api-external: tcp connection to aa50f1043216944b980ae0cca8d6495a-52d24c534d2d3655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:34:48Z"
    - latency: 7.437319ms
      message: 'load-balancer-api-external: resolved host name aa50f1043216944b980ae0cca8d6495a-52d24c534d2d3655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:34:48Z"
    - latency: 4.047845ms
      message: 'load-balancer-api-external: tcp connection to aa50f1043216944b980ae0cca8d6495a-52d24c534d2d3655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:33:48Z"
    - latency: 8.875107ms
      message: 'load-balancer-api-external: resolved host name aa50f1043216944b980ae0cca8d6495a-52d24c534d2d3655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:33:48Z"
    - latency: 5.337294ms
      message: 'load-balancer-api-external: tcp connection to aa50f1043216944b980ae0cca8d6495a-52d24c534d2d3655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:32:48Z"
    - latency: 8.787344ms
      message: 'load-balancer-api-external: resolved host name aa50f1043216944b980ae0cca8d6495a-52d24c534d2d3655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:32:48Z"
    - latency: 5.058411ms
      message: 'load-balancer-api-external: tcp connection to aa50f1043216944b980ae0cca8d6495a-52d24c534d2d3655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:31:48Z"
    - latency: 9.149326ms
      message: 'load-balancer-api-external: resolved host name aa50f1043216944b980ae0cca8d6495a-52d24c534d2d3655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:31:48Z"
    - latency: 3.90044ms
      message: 'load-balancer-api-external: tcp connection to aa50f1043216944b980ae0cca8d6495a-52d24c534d2d3655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:30:48Z"
    - latency: 9.055997ms
      message: 'load-balancer-api-external: resolved host name aa50f1043216944b980ae0cca8d6495a-52d24c534d2d3655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:30:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T17:28:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-56-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-56.ec2.internal
      uid: 4b7f058a-b8fa-4524-9c2a-323559f950bb
    resourceVersion: "14007"
    uid: fd8e14c7-94d5-4c93-8960-18560e621341
  spec:
    sourcePod: network-check-source-dbd9cf844-vxt5g
    targetEndpoint: aa50f1043216944b980ae0cca8d6495a-52d24c534d2d3655.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T17:34:48Z"
      message: 'load-balancer-api-internal: tcp connection to aa50f1043216944b980ae0cca8d6495a-52d24c534d2d3655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.652433ms
      message: 'load-balancer-api-internal: tcp connection to aa50f1043216944b980ae0cca8d6495a-52d24c534d2d3655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:34:48Z"
    - latency: 7.47722ms
      message: 'load-balancer-api-internal: resolved host name aa50f1043216944b980ae0cca8d6495a-52d24c534d2d3655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:34:48Z"
    - latency: 3.391327ms
      message: 'load-balancer-api-internal: tcp connection to aa50f1043216944b980ae0cca8d6495a-52d24c534d2d3655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:33:48Z"
    - latency: 8.90597ms
      message: 'load-balancer-api-internal: resolved host name aa50f1043216944b980ae0cca8d6495a-52d24c534d2d3655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:33:48Z"
    - latency: 7.079306ms
      message: 'load-balancer-api-internal: tcp connection to aa50f1043216944b980ae0cca8d6495a-52d24c534d2d3655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:32:48Z"
    - latency: 8.749624ms
      message: 'load-balancer-api-internal: resolved host name aa50f1043216944b980ae0cca8d6495a-52d24c534d2d3655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:32:48Z"
    - latency: 4.699005ms
      message: 'load-balancer-api-internal: tcp connection to aa50f1043216944b980ae0cca8d6495a-52d24c534d2d3655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:31:48Z"
    - latency: 9.174861ms
      message: 'load-balancer-api-internal: resolved host name aa50f1043216944b980ae0cca8d6495a-52d24c534d2d3655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:31:48Z"
    - latency: 3.876208ms
      message: 'load-balancer-api-internal: tcp connection to aa50f1043216944b980ae0cca8d6495a-52d24c534d2d3655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:30:48Z"
    - latency: 9.110485ms
      message: 'load-balancer-api-internal: resolved host name aa50f1043216944b980ae0cca8d6495a-52d24c534d2d3655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:30:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T17:28:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-56-to-network-check-target-ip-10-0-128-56
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-56.ec2.internal
      uid: 4b7f058a-b8fa-4524-9c2a-323559f950bb
    resourceVersion: "12394"
    uid: bcf0aa56-cd31-4ea7-9f9c-b03fbe34863d
  spec:
    sourcePod: network-check-source-dbd9cf844-vxt5g
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T17:28:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-56-to-network-check-target-ip-10-0-131-225
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-56.ec2.internal
      uid: 4b7f058a-b8fa-4524-9c2a-323559f950bb
    resourceVersion: "12392"
    uid: 99b67bb6-8826-4e9e-a6d8-6d365717b5b1
  spec:
    sourcePod: network-check-source-dbd9cf844-vxt5g
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T17:28:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-56-to-network-check-target-ip-10-0-140-198
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-56.ec2.internal
      uid: 4b7f058a-b8fa-4524-9c2a-323559f950bb
    resourceVersion: "12393"
    uid: 238b31bd-3561-4ec3-ad5a-a025b69c07fe
  spec:
    sourcePod: network-check-source-dbd9cf844-vxt5g
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T17:28:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-56-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-56.ec2.internal
      uid: 4b7f058a-b8fa-4524-9c2a-323559f950bb
    resourceVersion: "14006"
    uid: 4f8f6478-dd9f-4a8e-9cbf-551c5f942a7b
  spec:
    sourcePod: network-check-source-dbd9cf844-vxt5g
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T17:34:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 965.838µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:34:48Z"
    - latency: 2.468093ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:34:48Z"
    - latency: 815.007µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:33:48Z"
    - latency: 4.523292ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:33:48Z"
    - latency: 812.231µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:32:48Z"
    - latency: 1.663461ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:32:48Z"
    - latency: 797.315µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:31:48Z"
    - latency: 1.999571ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:31:48Z"
    - latency: 1.096828ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T17:30:48Z"
    - latency: 2.44427ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T17:30:48Z"
kind: List
metadata:
  resourceVersion: ""