apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T03:07:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-228-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-228.ec2.internal
      uid: ef423bcf-1234-40cd-b94e-a4141e6e413e
    resourceVersion: "10783"
    uid: 86d8f4bd-a5a4-466b-8e6f-f5a7494319ce
  spec:
    sourcePod: network-check-source-7cbc45fddc-jfvrl
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T03:07:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-228-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-228.ec2.internal
      uid: ef423bcf-1234-40cd-b94e-a4141e6e413e
    resourceVersion: "14235"
    uid: 5d0a6eac-5241-4b74-8ce7-f9df2fd95a41
  spec:
    sourcePod: network-check-source-7cbc45fddc-jfvrl
    targetEndpoint: ad6945c7f077e40f0988f45c4dfe153c-f89fa388bd0ce23b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T03:13:17Z"
      message: 'load-balancer-api-external: tcp connection to ad6945c7f077e40f0988f45c4dfe153c-f89fa388bd0ce23b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.883926ms
      message: 'load-balancer-api-external: tcp connection to ad6945c7f077e40f0988f45c4dfe153c-f89fa388bd0ce23b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:13:17Z"
    - latency: 8.482335ms
      message: 'load-balancer-api-external: resolved host name ad6945c7f077e40f0988f45c4dfe153c-f89fa388bd0ce23b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:13:17Z"
    - latency: 4.289591ms
      message: 'load-balancer-api-external: tcp connection to ad6945c7f077e40f0988f45c4dfe153c-f89fa388bd0ce23b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:12:17Z"
    - latency: 8.615575ms
      message: 'load-balancer-api-external: resolved host name ad6945c7f077e40f0988f45c4dfe153c-f89fa388bd0ce23b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:12:17Z"
    - latency: 4.365956ms
      message: 'load-balancer-api-external: tcp connection to ad6945c7f077e40f0988f45c4dfe153c-f89fa388bd0ce23b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:11:17Z"
    - latency: 8.353636ms
      message: 'load-balancer-api-external: resolved host name ad6945c7f077e40f0988f45c4dfe153c-f89fa388bd0ce23b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:11:17Z"
    - latency: 4.595385ms
      message: 'load-balancer-api-external: tcp connection to ad6945c7f077e40f0988f45c4dfe153c-f89fa388bd0ce23b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:10:17Z"
    - latency: 7.387391ms
      message: 'load-balancer-api-external: resolved host name ad6945c7f077e40f0988f45c4dfe153c-f89fa388bd0ce23b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:10:17Z"
    - latency: 5.073248ms
      message: 'load-balancer-api-external: tcp connection to ad6945c7f077e40f0988f45c4dfe153c-f89fa388bd0ce23b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:09:17Z"
    - latency: 7.304296ms
      message: 'load-balancer-api-external: resolved host name ad6945c7f077e40f0988f45c4dfe153c-f89fa388bd0ce23b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:09:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T03:07:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-228-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-228.ec2.internal
      uid: ef423bcf-1234-40cd-b94e-a4141e6e413e
    resourceVersion: "14236"
    uid: bf3476e5-76c4-4ec2-ad83-930ad8f08cab
  spec:
    sourcePod: network-check-source-7cbc45fddc-jfvrl
    targetEndpoint: ad6945c7f077e40f0988f45c4dfe153c-f89fa388bd0ce23b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T03:13:17Z"
      message: 'load-balancer-api-internal: tcp connection to ad6945c7f077e40f0988f45c4dfe153c-f89fa388bd0ce23b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.915409ms
      message: 'load-balancer-api-internal: tcp connection to ad6945c7f077e40f0988f45c4dfe153c-f89fa388bd0ce23b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:13:17Z"
    - latency: 8.443606ms
      message: 'load-balancer-api-internal: resolved host name ad6945c7f077e40f0988f45c4dfe153c-f89fa388bd0ce23b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:13:17Z"
    - latency: 3.920364ms
      message: 'load-balancer-api-internal: tcp connection to ad6945c7f077e40f0988f45c4dfe153c-f89fa388bd0ce23b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:12:17Z"
    - latency: 8.680696ms
      message: 'load-balancer-api-internal: resolved host name ad6945c7f077e40f0988f45c4dfe153c-f89fa388bd0ce23b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:12:17Z"
    - latency: 4.338962ms
      message: 'load-balancer-api-internal: tcp connection to ad6945c7f077e40f0988f45c4dfe153c-f89fa388bd0ce23b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:11:17Z"
    - latency: 8.371129ms
      message: 'load-balancer-api-internal: resolved host name ad6945c7f077e40f0988f45c4dfe153c-f89fa388bd0ce23b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:11:17Z"
    - latency: 4.609248ms
      message: 'load-balancer-api-internal: tcp connection to ad6945c7f077e40f0988f45c4dfe153c-f89fa388bd0ce23b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:10:17Z"
    - latency: 7.312116ms
      message: 'load-balancer-api-internal: resolved host name ad6945c7f077e40f0988f45c4dfe153c-f89fa388bd0ce23b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:10:17Z"
    - latency: 5.085561ms
      message: 'load-balancer-api-internal: tcp connection to ad6945c7f077e40f0988f45c4dfe153c-f89fa388bd0ce23b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:09:17Z"
    - latency: 7.238786ms
      message: 'load-balancer-api-internal: resolved host name ad6945c7f077e40f0988f45c4dfe153c-f89fa388bd0ce23b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:09:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T03:07:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-228-to-network-check-target-ip-10-0-137-88
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-228.ec2.internal
      uid: ef423bcf-1234-40cd-b94e-a4141e6e413e
    resourceVersion: "10791"
    uid: f5931667-b76f-4677-9e77-957c2a4a4528
  spec:
    sourcePod: network-check-source-7cbc45fddc-jfvrl
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T03:07:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-228-to-network-check-target-ip-10-0-139-228
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-228.ec2.internal
      uid: ef423bcf-1234-40cd-b94e-a4141e6e413e
    resourceVersion: "10789"
    uid: 54f4cb7e-3f93-482a-8216-ab07a9596ae0
  spec:
    sourcePod: network-check-source-7cbc45fddc-jfvrl
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T03:07:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-228-to-network-check-target-ip-10-0-142-11
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-228.ec2.internal
      uid: ef423bcf-1234-40cd-b94e-a4141e6e413e
    resourceVersion: "10790"
    uid: 639f614a-c3d8-4ce4-9a37-6ede39f31968
  spec:
    sourcePod: network-check-source-7cbc45fddc-jfvrl
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T03:07:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-228-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-228.ec2.internal
      uid: ef423bcf-1234-40cd-b94e-a4141e6e413e
    resourceVersion: "14234"
    uid: 78e89382-00cc-4f60-b726-64d449dd7c68
  spec:
    sourcePod: network-check-source-7cbc45fddc-jfvrl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T03:13:17Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 946.292µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:13:17Z"
    - latency: 1.942128ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:13:17Z"
    - latency: 951.803µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:12:17Z"
    - latency: 1.74835ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:12:17Z"
    - latency: 839.907µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:11:17Z"
    - latency: 2.094774ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:11:17Z"
    - latency: 1.01239ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:10:17Z"
    - latency: 1.923596ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:10:17Z"
    - latency: 1.08335ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:09:17Z"
    - latency: 1.594159ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:09:17Z"
kind: List
metadata:
  resourceVersion: ""