apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T18:34:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-117-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-117.ec2.internal
      uid: 5ff0f5a6-002b-4c17-89e8-ed1fabd74aa1
    resourceVersion: "14806"
    uid: b8079678-bece-416f-a2eb-4ff25654f44c
  spec:
    sourcePod: network-check-source-65bdbbff45-zdq2d
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T18:41:31Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.793568ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:41:31Z"
    - latency: 1.126272ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:40:31Z"
    - latency: 1.008982ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:39:31Z"
    - latency: 829.341µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:38:31Z"
    - latency: 893.06µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:37:31Z"
    - latency: 830.838µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:36:31Z"
    - latency: 996.666µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:35:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T18:34:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-117-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-117.ec2.internal
      uid: 5ff0f5a6-002b-4c17-89e8-ed1fabd74aa1
    resourceVersion: "14303"
    uid: 55b4ee1d-7408-45df-a902-a64e0434fc05
  spec:
    sourcePod: network-check-source-65bdbbff45-zdq2d
    targetEndpoint: aec1671db9bf042fdb7966b525d188b2-32f160e0e95b4a6e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T18:40:31Z"
      message: 'load-balancer-api-external: tcp connection to aec1671db9bf042fdb7966b525d188b2-32f160e0e95b4a6e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.930885ms
      message: 'load-balancer-api-external: tcp connection to aec1671db9bf042fdb7966b525d188b2-32f160e0e95b4a6e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:40:31Z"
    - latency: 7.667888ms
      message: 'load-balancer-api-external: resolved host name aec1671db9bf042fdb7966b525d188b2-32f160e0e95b4a6e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:40:31Z"
    - latency: 6.226065ms
      message: 'load-balancer-api-external: tcp connection to aec1671db9bf042fdb7966b525d188b2-32f160e0e95b4a6e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:39:31Z"
    - latency: 8.650165ms
      message: 'load-balancer-api-external: resolved host name aec1671db9bf042fdb7966b525d188b2-32f160e0e95b4a6e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:39:31Z"
    - latency: 4.633209ms
      message: 'load-balancer-api-external: tcp connection to aec1671db9bf042fdb7966b525d188b2-32f160e0e95b4a6e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:38:31Z"
    - latency: 8.166345ms
      message: 'load-balancer-api-external: resolved host name aec1671db9bf042fdb7966b525d188b2-32f160e0e95b4a6e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:38:31Z"
    - latency: 5.011055ms
      message: 'load-balancer-api-external: tcp connection to aec1671db9bf042fdb7966b525d188b2-32f160e0e95b4a6e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:37:31Z"
    - latency: 8.369635ms
      message: 'load-balancer-api-external: resolved host name aec1671db9bf042fdb7966b525d188b2-32f160e0e95b4a6e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:37:31Z"
    - latency: 4.543579ms
      message: 'load-balancer-api-external: tcp connection to aec1671db9bf042fdb7966b525d188b2-32f160e0e95b4a6e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:36:31Z"
    - latency: 9.282972ms
      message: 'load-balancer-api-external: resolved host name aec1671db9bf042fdb7966b525d188b2-32f160e0e95b4a6e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:36:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T18:34:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-117-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-117.ec2.internal
      uid: 5ff0f5a6-002b-4c17-89e8-ed1fabd74aa1
    resourceVersion: "14302"
    uid: 0fc9643d-bded-45ac-b2d2-da6e54f2db90
  spec:
    sourcePod: network-check-source-65bdbbff45-zdq2d
    targetEndpoint: aec1671db9bf042fdb7966b525d188b2-32f160e0e95b4a6e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T18:40:31Z"
      message: 'load-balancer-api-internal: tcp connection to aec1671db9bf042fdb7966b525d188b2-32f160e0e95b4a6e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.92524ms
      message: 'load-balancer-api-internal: tcp connection to aec1671db9bf042fdb7966b525d188b2-32f160e0e95b4a6e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:40:31Z"
    - latency: 7.779942ms
      message: 'load-balancer-api-internal: resolved host name aec1671db9bf042fdb7966b525d188b2-32f160e0e95b4a6e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:40:31Z"
    - latency: 5.082242ms
      message: 'load-balancer-api-internal: tcp connection to aec1671db9bf042fdb7966b525d188b2-32f160e0e95b4a6e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:39:31Z"
    - latency: 8.703423ms
      message: 'load-balancer-api-internal: resolved host name aec1671db9bf042fdb7966b525d188b2-32f160e0e95b4a6e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:39:31Z"
    - latency: 4.113135ms
      message: 'load-balancer-api-internal: tcp connection to aec1671db9bf042fdb7966b525d188b2-32f160e0e95b4a6e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:38:31Z"
    - latency: 8.227509ms
      message: 'load-balancer-api-internal: resolved host name aec1671db9bf042fdb7966b525d188b2-32f160e0e95b4a6e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:38:31Z"
    - latency: 5.044516ms
      message: 'load-balancer-api-internal: tcp connection to aec1671db9bf042fdb7966b525d188b2-32f160e0e95b4a6e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:37:31Z"
    - latency: 8.440626ms
      message: 'load-balancer-api-internal: resolved host name aec1671db9bf042fdb7966b525d188b2-32f160e0e95b4a6e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:37:31Z"
    - latency: 4.549713ms
      message: 'load-balancer-api-internal: tcp connection to aec1671db9bf042fdb7966b525d188b2-32f160e0e95b4a6e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:36:31Z"
    - latency: 9.384282ms
      message: 'load-balancer-api-internal: resolved host name aec1671db9bf042fdb7966b525d188b2-32f160e0e95b4a6e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:36:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T18:34:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-117-to-network-check-target-ip-10-0-128-11
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-117.ec2.internal
      uid: 5ff0f5a6-002b-4c17-89e8-ed1fabd74aa1
    resourceVersion: "14803"
    uid: e6788ecb-ba0d-4e7e-aece-3dc0aeb7031d
  spec:
    sourcePod: network-check-source-65bdbbff45-zdq2d
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T18:41:31Z"
      message: 'network-check-target-ip-10-0-128-11: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.905783ms
      message: 'network-check-target-ip-10-0-128-11: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:41:31Z"
    - latency: 1.874242ms
      message: 'network-check-target-ip-10-0-128-11: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:40:31Z"
    - latency: 1.82349ms
      message: 'network-check-target-ip-10-0-128-11: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:39:31Z"
    - latency: 1.730657ms
      message: 'network-check-target-ip-10-0-128-11: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:38:31Z"
    - latency: 1.836438ms
      message: 'network-check-target-ip-10-0-128-11: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:37:31Z"
    - latency: 1.798406ms
      message: 'network-check-target-ip-10-0-128-11: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:36:31Z"
    - latency: 2.130857ms
      message: 'network-check-target-ip-10-0-128-11: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:35:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T18:34:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-117-to-network-check-target-ip-10-0-129-117
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-117.ec2.internal
      uid: 5ff0f5a6-002b-4c17-89e8-ed1fabd74aa1
    resourceVersion: "14804"
    uid: a288616d-e59c-436c-8b64-2bce77e5828a
  spec:
    sourcePod: network-check-source-65bdbbff45-zdq2d
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T18:41:31Z"
      message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.374929ms
      message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:41:31Z"
    - latency: 1.318276ms
      message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:40:31Z"
    - latency: 901.182µs
      message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:39:31Z"
    - latency: 844.906µs
      message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:38:31Z"
    - latency: 1.202327ms
      message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:37:31Z"
    - latency: 1.544212ms
      message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:36:31Z"
    - latency: 1.249733ms
      message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:35:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T18:34:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-117-to-network-check-target-ip-10-0-129-137
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-117.ec2.internal
      uid: 5ff0f5a6-002b-4c17-89e8-ed1fabd74aa1
    resourceVersion: "14805"
    uid: 0b469de6-37bc-4111-8b0b-63a736aec616
  spec:
    sourcePod: network-check-source-65bdbbff45-zdq2d
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T18:41:31Z"
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.339881ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:41:31Z"
    - latency: 2.252778ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:40:31Z"
    - latency: 2.131677ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:39:31Z"
    - latency: 2.062226ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:38:31Z"
    - latency: 1.875834ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:37:31Z"
    - latency: 1.860371ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:36:31Z"
    - latency: 2.231368ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:35:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T18:34:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-117-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-117.ec2.internal
      uid: 5ff0f5a6-002b-4c17-89e8-ed1fabd74aa1
    resourceVersion: "14301"
    uid: d574b72e-8534-4dee-8403-da724e3d8bf0
  spec:
    sourcePod: network-check-source-65bdbbff45-zdq2d
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T18:40:31Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 909.412µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:40:31Z"
    - latency: 1.730177ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:40:31Z"
    - latency: 802.268µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:39:31Z"
    - latency: 2.067713ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:39:31Z"
    - latency: 802.238µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:38:31Z"
    - latency: 1.762436ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:38:31Z"
    - latency: 964.87µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:37:31Z"
    - latency: 1.882961ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:37:31Z"
    - latency: 1.182946ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T18:36:31Z"
    - latency: 1.954355ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T18:36:31Z"
kind: List
metadata:
  resourceVersion: ""