apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T05:46:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-202-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-202.ec2.internal
      uid: 71c925ea-2cb6-4794-b9bf-e0229fd8821b
    resourceVersion: "10717"
    uid: 3249175d-3ce1-4e14-85ad-a28f895a0b28
  spec:
    sourcePod: network-check-source-65bdbbff45-7bszh
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T05:46:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-202-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-202.ec2.internal
      uid: 71c925ea-2cb6-4794-b9bf-e0229fd8821b
    resourceVersion: "14470"
    uid: 4c73cfb7-c155-4e59-975f-dfebfa4c5669
  spec:
    sourcePod: network-check-source-65bdbbff45-7bszh
    targetEndpoint: a58a1d71412234abf9c9008f70e3d561-3093ee16e92f3bfb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-01T05:52:36Z"
      message: 'load-balancer-api-external: tcp connection to a58a1d71412234abf9c9008f70e3d561-3093ee16e92f3bfb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.070673ms
      message: 'load-balancer-api-external: tcp connection to a58a1d71412234abf9c9008f70e3d561-3093ee16e92f3bfb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:52:36Z"
    - latency: 6.878739ms
      message: 'load-balancer-api-external: resolved host name a58a1d71412234abf9c9008f70e3d561-3093ee16e92f3bfb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:52:36Z"
    - latency: 4.989234ms
      message: 'load-balancer-api-external: tcp connection to a58a1d71412234abf9c9008f70e3d561-3093ee16e92f3bfb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:51:36Z"
    - latency: 6.532005ms
      message: 'load-balancer-api-external: resolved host name a58a1d71412234abf9c9008f70e3d561-3093ee16e92f3bfb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:51:36Z"
    - latency: 5.438215ms
      message: 'load-balancer-api-external: tcp connection to a58a1d71412234abf9c9008f70e3d561-3093ee16e92f3bfb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:50:36Z"
    - latency: 11.764487ms
      message: 'load-balancer-api-external: resolved host name a58a1d71412234abf9c9008f70e3d561-3093ee16e92f3bfb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:50:36Z"
    - latency: 5.250254ms
      message: 'load-balancer-api-external: tcp connection to a58a1d71412234abf9c9008f70e3d561-3093ee16e92f3bfb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:49:36Z"
    - latency: 6.819454ms
      message: 'load-balancer-api-external: resolved host name a58a1d71412234abf9c9008f70e3d561-3093ee16e92f3bfb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:49:36Z"
    - latency: 5.216623ms
      message: 'load-balancer-api-external: tcp connection to a58a1d71412234abf9c9008f70e3d561-3093ee16e92f3bfb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:48:36Z"
    - latency: 6.869509ms
      message: 'load-balancer-api-external: resolved host name a58a1d71412234abf9c9008f70e3d561-3093ee16e92f3bfb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:48:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T05:46:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-202-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-202.ec2.internal
      uid: 71c925ea-2cb6-4794-b9bf-e0229fd8821b
    resourceVersion: "14469"
    uid: 3807e28e-ac7d-4cc7-af7c-a575883e2cc2
  spec:
    sourcePod: network-check-source-65bdbbff45-7bszh
    targetEndpoint: a58a1d71412234abf9c9008f70e3d561-3093ee16e92f3bfb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-01T05:52:36Z"
      message: 'load-balancer-api-internal: tcp connection to a58a1d71412234abf9c9008f70e3d561-3093ee16e92f3bfb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.105776ms
      message: 'load-balancer-api-internal: tcp connection to a58a1d71412234abf9c9008f70e3d561-3093ee16e92f3bfb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:52:36Z"
    - latency: 6.975949ms
      message: 'load-balancer-api-internal: resolved host name a58a1d71412234abf9c9008f70e3d561-3093ee16e92f3bfb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:52:36Z"
    - latency: 4.951586ms
      message: 'load-balancer-api-internal: tcp connection to a58a1d71412234abf9c9008f70e3d561-3093ee16e92f3bfb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:51:36Z"
    - latency: 6.558141ms
      message: 'load-balancer-api-internal: resolved host name a58a1d71412234abf9c9008f70e3d561-3093ee16e92f3bfb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:51:36Z"
    - latency: 5.449853ms
      message: 'load-balancer-api-internal: tcp connection to a58a1d71412234abf9c9008f70e3d561-3093ee16e92f3bfb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:50:36Z"
    - latency: 11.797688ms
      message: 'load-balancer-api-internal: resolved host name a58a1d71412234abf9c9008f70e3d561-3093ee16e92f3bfb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:50:36Z"
    - latency: 5.279527ms
      message: 'load-balancer-api-internal: tcp connection to a58a1d71412234abf9c9008f70e3d561-3093ee16e92f3bfb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:49:36Z"
    - latency: 6.851396ms
      message: 'load-balancer-api-internal: resolved host name a58a1d71412234abf9c9008f70e3d561-3093ee16e92f3bfb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:49:36Z"
    - latency: 4.200412ms
      message: 'load-balancer-api-internal: tcp connection to a58a1d71412234abf9c9008f70e3d561-3093ee16e92f3bfb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:48:36Z"
    - latency: 6.843507ms
      message: 'load-balancer-api-internal: resolved host name a58a1d71412234abf9c9008f70e3d561-3093ee16e92f3bfb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:48:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T05:46:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-202-to-network-check-target-ip-10-0-129-202
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-202.ec2.internal
      uid: 71c925ea-2cb6-4794-b9bf-e0229fd8821b
    resourceVersion: "10714"
    uid: 4ebfc462-aae5-4310-a121-5707c2670809
  spec:
    sourcePod: network-check-source-65bdbbff45-7bszh
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T05:46:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-202-to-network-check-target-ip-10-0-130-55
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-202.ec2.internal
      uid: 71c925ea-2cb6-4794-b9bf-e0229fd8821b
    resourceVersion: "10716"
    uid: f5a18679-c7f2-40af-adb7-347a6207fa48
  spec:
    sourcePod: network-check-source-65bdbbff45-7bszh
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T05:46:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-202-to-network-check-target-ip-10-0-142-152
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-202.ec2.internal
      uid: 71c925ea-2cb6-4794-b9bf-e0229fd8821b
    resourceVersion: "10715"
    uid: 9de4fbe9-f189-4bd5-a405-d7bb892e3865
  spec:
    sourcePod: network-check-source-65bdbbff45-7bszh
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T05:46:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-202-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-202.ec2.internal
      uid: 71c925ea-2cb6-4794-b9bf-e0229fd8821b
    resourceVersion: "14468"
    uid: ab8e0100-5142-4d44-aec3-be0b32072959
  spec:
    sourcePod: network-check-source-65bdbbff45-7bszh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-01T05:52:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.242515ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:52:36Z"
    - latency: 1.804677ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:52:36Z"
    - latency: 945.712µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:51:36Z"
    - latency: 1.948096ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:51:36Z"
    - latency: 766.177µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:50:36Z"
    - latency: 6.160968ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:50:36Z"
    - latency: 816.633µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:49:36Z"
    - latency: 1.899062ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:49:36Z"
    - latency: 956.578µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:48:36Z"
    - latency: 1.698493ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:48:36Z"
kind: List
metadata:
  resourceVersion: ""