apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:24:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-238-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-238.ec2.internal
      uid: 4161b15f-415b-42db-9e21-91a19175cf83
    resourceVersion: "22841"
    uid: 1f2680f6-8d42-4664-a293-f4a540152198
  spec:
    sourcePod: network-check-source-56499946bc-fkr66
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:31:22Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.257849ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:31:22Z"
    - latency: 1.158121ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:30:22Z"
    - latency: 1.041241ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:29:22Z"
    - latency: 946.254µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:28:22Z"
    - latency: 1.167024ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:27:22Z"
    - latency: 862.635µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:26:22Z"
    - latency: 901.363µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:25:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:24:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-238-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-238.ec2.internal
      uid: 4161b15f-415b-42db-9e21-91a19175cf83
    resourceVersion: "21916"
    uid: 986949aa-b428-463d-828e-d4ff48dd3efb
  spec:
    sourcePod: network-check-source-56499946bc-fkr66
    targetEndpoint: a17a3511dbb4541399d3f2d65266f570-484118f6b2536028.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:30:22Z"
      message: 'load-balancer-api-external: tcp connection to a17a3511dbb4541399d3f2d65266f570-484118f6b2536028.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.250523ms
      message: 'load-balancer-api-external: tcp connection to a17a3511dbb4541399d3f2d65266f570-484118f6b2536028.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:30:22Z"
    - latency: 8.604275ms
      message: 'load-balancer-api-external: resolved host name a17a3511dbb4541399d3f2d65266f570-484118f6b2536028.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:30:22Z"
    - latency: 5.411617ms
      message: 'load-balancer-api-external: tcp connection to a17a3511dbb4541399d3f2d65266f570-484118f6b2536028.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:29:22Z"
    - latency: 8.980197ms
      message: 'load-balancer-api-external: resolved host name a17a3511dbb4541399d3f2d65266f570-484118f6b2536028.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:29:22Z"
    - latency: 4.549299ms
      message: 'load-balancer-api-external: tcp connection to a17a3511dbb4541399d3f2d65266f570-484118f6b2536028.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:28:22Z"
    - latency: 9.699871ms
      message: 'load-balancer-api-external: resolved host name a17a3511dbb4541399d3f2d65266f570-484118f6b2536028.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:28:22Z"
    - latency: 4.514659ms
      message: 'load-balancer-api-external: tcp connection to a17a3511dbb4541399d3f2d65266f570-484118f6b2536028.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:27:22Z"
    - latency: 8.61383ms
      message: 'load-balancer-api-external: resolved host name a17a3511dbb4541399d3f2d65266f570-484118f6b2536028.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:27:22Z"
    - latency: 5.594401ms
      message: 'load-balancer-api-external: tcp connection to a17a3511dbb4541399d3f2d65266f570-484118f6b2536028.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:26:22Z"
    - latency: 6.625799ms
      message: 'load-balancer-api-external: resolved host name a17a3511dbb4541399d3f2d65266f570-484118f6b2536028.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:26:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:24:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-238-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-238.ec2.internal
      uid: 4161b15f-415b-42db-9e21-91a19175cf83
    resourceVersion: "21915"
    uid: c12aa1a0-e5fd-453f-a5a2-3dc3f36782c9
  spec:
    sourcePod: network-check-source-56499946bc-fkr66
    targetEndpoint: a17a3511dbb4541399d3f2d65266f570-484118f6b2536028.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:30:22Z"
      message: 'load-balancer-api-internal: tcp connection to a17a3511dbb4541399d3f2d65266f570-484118f6b2536028.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.000288ms
      message: 'load-balancer-api-internal: tcp connection to a17a3511dbb4541399d3f2d65266f570-484118f6b2536028.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:30:22Z"
    - latency: 8.637362ms
      message: 'load-balancer-api-internal: resolved host name a17a3511dbb4541399d3f2d65266f570-484118f6b2536028.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:30:22Z"
    - latency: 5.40109ms
      message: 'load-balancer-api-internal: tcp connection to a17a3511dbb4541399d3f2d65266f570-484118f6b2536028.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:29:22Z"
    - latency: 9.017422ms
      message: 'load-balancer-api-internal: resolved host name a17a3511dbb4541399d3f2d65266f570-484118f6b2536028.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:29:22Z"
    - latency: 4.562622ms
      message: 'load-balancer-api-internal: tcp connection to a17a3511dbb4541399d3f2d65266f570-484118f6b2536028.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:28:22Z"
    - latency: 9.749129ms
      message: 'load-balancer-api-internal: resolved host name a17a3511dbb4541399d3f2d65266f570-484118f6b2536028.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:28:22Z"
    - latency: 5.065812ms
      message: 'load-balancer-api-internal: tcp connection to a17a3511dbb4541399d3f2d65266f570-484118f6b2536028.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:27:22Z"
    - latency: 8.714541ms
      message: 'load-balancer-api-internal: resolved host name a17a3511dbb4541399d3f2d65266f570-484118f6b2536028.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:27:22Z"
    - latency: 5.347292ms
      message: 'load-balancer-api-internal: tcp connection to a17a3511dbb4541399d3f2d65266f570-484118f6b2536028.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:26:22Z"
    - latency: 6.672172ms
      message: 'load-balancer-api-internal: resolved host name a17a3511dbb4541399d3f2d65266f570-484118f6b2536028.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:26:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:24:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-238-to-network-check-target-ip-10-0-128-178
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-238.ec2.internal
      uid: 4161b15f-415b-42db-9e21-91a19175cf83
    resourceVersion: "22840"
    uid: 13a75ef2-af1a-43fe-8350-0733cb23ee92
  spec:
    sourcePod: network-check-source-56499946bc-fkr66
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:31:22Z"
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.393504ms
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:31:22Z"
    - latency: 2.120029ms
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:30:22Z"
    - latency: 2.245388ms
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:29:22Z"
    - latency: 2.187856ms
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:28:22Z"
    - latency: 2.099286ms
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:27:22Z"
    - latency: 2.168371ms
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:26:22Z"
    - latency: 1.942781ms
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:25:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:24:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-238-to-network-check-target-ip-10-0-129-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-238.ec2.internal
      uid: 4161b15f-415b-42db-9e21-91a19175cf83
    resourceVersion: "22838"
    uid: 7699c47d-e218-494f-9292-4e97de0b6517
  spec:
    sourcePod: network-check-source-56499946bc-fkr66
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:31:22Z"
      message: 'network-check-target-ip-10-0-129-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.374526ms
      message: 'network-check-target-ip-10-0-129-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:31:22Z"
    - latency: 913.919µs
      message: 'network-check-target-ip-10-0-129-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:30:22Z"
    - latency: 1.163085ms
      message: 'network-check-target-ip-10-0-129-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:29:22Z"
    - latency: 923.376µs
      message: 'network-check-target-ip-10-0-129-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:28:22Z"
    - latency: 810.617µs
      message: 'network-check-target-ip-10-0-129-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:27:22Z"
    - latency: 1.177947ms
      message: 'network-check-target-ip-10-0-129-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:26:22Z"
    - latency: 1.502729ms
      message: 'network-check-target-ip-10-0-129-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:25:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:24:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-238-to-network-check-target-ip-10-0-139-232
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-238.ec2.internal
      uid: 4161b15f-415b-42db-9e21-91a19175cf83
    resourceVersion: "22839"
    uid: 1913bd1f-b692-47cc-b733-01868834fcfd
  spec:
    sourcePod: network-check-source-56499946bc-fkr66
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:31:22Z"
      message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.76064ms
      message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:31:22Z"
    - latency: 2.208118ms
      message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:30:22Z"
    - latency: 2.217018ms
      message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:29:22Z"
    - latency: 2.064772ms
      message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:28:22Z"
    - latency: 1.841246ms
      message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:27:22Z"
    - latency: 2.108755ms
      message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:26:22Z"
    - latency: 2.12216ms
      message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:25:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:24:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-238-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-238.ec2.internal
      uid: 4161b15f-415b-42db-9e21-91a19175cf83
    resourceVersion: "21914"
    uid: ccd22031-7dad-4ac0-bcb9-d33a202738ca
  spec:
    sourcePod: network-check-source-56499946bc-fkr66
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:30:22Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 908.599µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:30:22Z"
    - latency: 1.968701ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:30:22Z"
    - latency: 1.184777ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:29:22Z"
    - latency: 1.56953ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:29:22Z"
    - latency: 808.209µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:28:22Z"
    - latency: 1.822872ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:28:22Z"
    - latency: 975.353µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:27:22Z"
    - latency: 1.678689ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:27:22Z"
    - latency: 1.008935ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:26:22Z"
    - latency: 1.687857ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:26:22Z"
kind: List
metadata:
  resourceVersion: ""