apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T06:25:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-116-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-116.ec2.internal
      uid: dd80c570-1eb1-4df4-9c9c-5f88c5511675
    resourceVersion: "11992"
    uid: 8cc9b40c-2f7c-409f-8ecb-4c3d44637115
  spec:
    sourcePod: network-check-source-6f8b768455-nbrsv
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T06:25:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-116-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-116.ec2.internal
      uid: dd80c570-1eb1-4df4-9c9c-5f88c5511675
    resourceVersion: "15435"
    uid: e87fe7f8-cff5-495f-8702-f5dd9c0eeed9
  spec:
    sourcePod: network-check-source-6f8b768455-nbrsv
    targetEndpoint: aca6abbc7887d41c291eca44a898910f-dbacfa66505143e0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T06:31:07Z"
      message: 'load-balancer-api-external: tcp connection to aca6abbc7887d41c291eca44a898910f-dbacfa66505143e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.406652ms
      message: 'load-balancer-api-external: tcp connection to aca6abbc7887d41c291eca44a898910f-dbacfa66505143e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:31:07Z"
    - latency: 6.686455ms
      message: 'load-balancer-api-external: resolved host name aca6abbc7887d41c291eca44a898910f-dbacfa66505143e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:31:07Z"
    - latency: 4.844465ms
      message: 'load-balancer-api-external: tcp connection to aca6abbc7887d41c291eca44a898910f-dbacfa66505143e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:30:07Z"
    - latency: 6.593364ms
      message: 'load-balancer-api-external: resolved host name aca6abbc7887d41c291eca44a898910f-dbacfa66505143e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:30:07Z"
    - latency: 5.228932ms
      message: 'load-balancer-api-external: tcp connection to aca6abbc7887d41c291eca44a898910f-dbacfa66505143e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:29:07Z"
    - latency: 6.586704ms
      message: 'load-balancer-api-external: resolved host name aca6abbc7887d41c291eca44a898910f-dbacfa66505143e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:29:07Z"
    - latency: 4.435561ms
      message: 'load-balancer-api-external: tcp connection to aca6abbc7887d41c291eca44a898910f-dbacfa66505143e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:28:07Z"
    - latency: 6.059973ms
      message: 'load-balancer-api-external: resolved host name aca6abbc7887d41c291eca44a898910f-dbacfa66505143e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:28:07Z"
    - latency: 3.261793ms
      message: 'load-balancer-api-external: tcp connection to aca6abbc7887d41c291eca44a898910f-dbacfa66505143e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:27:07Z"
    - latency: 6.121307ms
      message: 'load-balancer-api-external: resolved host name aca6abbc7887d41c291eca44a898910f-dbacfa66505143e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:27:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T06:25:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-116-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-116.ec2.internal
      uid: dd80c570-1eb1-4df4-9c9c-5f88c5511675
    resourceVersion: "15434"
    uid: d62b6639-dff6-4325-988f-3b6ba5d22a3b
  spec:
    sourcePod: network-check-source-6f8b768455-nbrsv
    targetEndpoint: aca6abbc7887d41c291eca44a898910f-dbacfa66505143e0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T06:31:07Z"
      message: 'load-balancer-api-internal: tcp connection to aca6abbc7887d41c291eca44a898910f-dbacfa66505143e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.961374ms
      message: 'load-balancer-api-internal: tcp connection to aca6abbc7887d41c291eca44a898910f-dbacfa66505143e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:31:07Z"
    - latency: 6.57581ms
      message: 'load-balancer-api-internal: resolved host name aca6abbc7887d41c291eca44a898910f-dbacfa66505143e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:31:07Z"
    - latency: 4.856907ms
      message: 'load-balancer-api-internal: tcp connection to aca6abbc7887d41c291eca44a898910f-dbacfa66505143e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:30:07Z"
    - latency: 6.543518ms
      message: 'load-balancer-api-internal: resolved host name aca6abbc7887d41c291eca44a898910f-dbacfa66505143e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:30:07Z"
    - latency: 5.203644ms
      message: 'load-balancer-api-internal: tcp connection to aca6abbc7887d41c291eca44a898910f-dbacfa66505143e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:29:07Z"
    - latency: 6.502297ms
      message: 'load-balancer-api-internal: resolved host name aca6abbc7887d41c291eca44a898910f-dbacfa66505143e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:29:07Z"
    - latency: 4.362944ms
      message: 'load-balancer-api-internal: tcp connection to aca6abbc7887d41c291eca44a898910f-dbacfa66505143e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:28:07Z"
    - latency: 5.94946ms
      message: 'load-balancer-api-internal: resolved host name aca6abbc7887d41c291eca44a898910f-dbacfa66505143e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:28:07Z"
    - latency: 4.297906ms
      message: 'load-balancer-api-internal: tcp connection to aca6abbc7887d41c291eca44a898910f-dbacfa66505143e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:27:07Z"
    - latency: 6.056418ms
      message: 'load-balancer-api-internal: resolved host name aca6abbc7887d41c291eca44a898910f-dbacfa66505143e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:27:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T06:25:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-116-to-network-check-target-ip-10-0-132-173
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-116.ec2.internal
      uid: dd80c570-1eb1-4df4-9c9c-5f88c5511675
    resourceVersion: "11997"
    uid: d5028456-cb9d-4b84-b7c8-ecc85b08d670
  spec:
    sourcePod: network-check-source-6f8b768455-nbrsv
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T06:25:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-116-to-network-check-target-ip-10-0-134-58
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-116.ec2.internal
      uid: dd80c570-1eb1-4df4-9c9c-5f88c5511675
    resourceVersion: "11999"
    uid: 94b7f556-ab1e-42d8-9d96-44c0f3747222
  spec:
    sourcePod: network-check-source-6f8b768455-nbrsv
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T06:25:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-116-to-network-check-target-ip-10-0-137-116
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-116.ec2.internal
      uid: dd80c570-1eb1-4df4-9c9c-5f88c5511675
    resourceVersion: "11998"
    uid: 974f6ddc-ecaf-4201-ad0e-e2d52e61ddb0
  spec:
    sourcePod: network-check-source-6f8b768455-nbrsv
    targetEndpoint: 10.133.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T06:25:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-116-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-116.ec2.internal
      uid: dd80c570-1eb1-4df4-9c9c-5f88c5511675
    resourceVersion: "15433"
    uid: 014e9c2a-ef22-4e9a-b07c-2b67c68b32a6
  spec:
    sourcePod: network-check-source-6f8b768455-nbrsv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T06:31:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.104598ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:31:07Z"
    - latency: 1.639655ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:31:07Z"
    - latency: 900.398µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:30:07Z"
    - latency: 1.718329ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:30:07Z"
    - latency: 911.77µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:29:07Z"
    - latency: 1.647113ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:29:07Z"
    - latency: 1.066607ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:28:07Z"
    - latency: 1.619548ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:28:07Z"
    - latency: 790.5µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:27:07Z"
    - latency: 1.732292ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:27:07Z"
kind: List
metadata:
  resourceVersion: ""