apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:13:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-25-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-25.ec2.internal
      uid: b0251a96-da67-4661-b60d-690791a8cdf9
    resourceVersion: "16145"
    uid: c5b0cd9a-7a39-4271-8029-86f231976c31
  spec:
    sourcePod: network-check-source-869dcfcdcd-rhpkz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T13:20:17Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 861.96µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:20:17Z"
    - latency: 974.086µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:19:17Z"
    - latency: 1.252776ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:18:17Z"
    - latency: 1.115485ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:17:17Z"
    - latency: 870.243µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:16:17Z"
    - latency: 8.424399ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:15:17Z"
    - latency: 985.362µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:14:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:13:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-25-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-25.ec2.internal
      uid: b0251a96-da67-4661-b60d-690791a8cdf9
    resourceVersion: "15705"
    uid: bf858a05-cc73-48bd-9d74-ec73c08d64e1
  spec:
    sourcePod: network-check-source-869dcfcdcd-rhpkz
    targetEndpoint: a15e27fca507f47498b99e22b948bb9a-1f91b4c64f2109c8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T13:19:17Z"
      message: 'load-balancer-api-external: tcp connection to a15e27fca507f47498b99e22b948bb9a-1f91b4c64f2109c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.569938ms
      message: 'load-balancer-api-external: tcp connection to a15e27fca507f47498b99e22b948bb9a-1f91b4c64f2109c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:19:17Z"
    - latency: 7.993249ms
      message: 'load-balancer-api-external: resolved host name a15e27fca507f47498b99e22b948bb9a-1f91b4c64f2109c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:19:17Z"
    - latency: 4.182643ms
      message: 'load-balancer-api-external: tcp connection to a15e27fca507f47498b99e22b948bb9a-1f91b4c64f2109c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:18:17Z"
    - latency: 9.832148ms
      message: 'load-balancer-api-external: resolved host name a15e27fca507f47498b99e22b948bb9a-1f91b4c64f2109c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:18:17Z"
    - latency: 5.089223ms
      message: 'load-balancer-api-external: tcp connection to a15e27fca507f47498b99e22b948bb9a-1f91b4c64f2109c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:17:17Z"
    - latency: 7.91367ms
      message: 'load-balancer-api-external: resolved host name a15e27fca507f47498b99e22b948bb9a-1f91b4c64f2109c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:17:17Z"
    - latency: 5.786175ms
      message: 'load-balancer-api-external: tcp connection to a15e27fca507f47498b99e22b948bb9a-1f91b4c64f2109c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:16:17Z"
    - latency: 8.151494ms
      message: 'load-balancer-api-external: resolved host name a15e27fca507f47498b99e22b948bb9a-1f91b4c64f2109c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:16:17Z"
    - latency: 3.656333ms
      message: 'load-balancer-api-external: tcp connection to a15e27fca507f47498b99e22b948bb9a-1f91b4c64f2109c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:15:17Z"
    - latency: 14.973055ms
      message: 'load-balancer-api-external: resolved host name a15e27fca507f47498b99e22b948bb9a-1f91b4c64f2109c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:15:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:13:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-25-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-25.ec2.internal
      uid: b0251a96-da67-4661-b60d-690791a8cdf9
    resourceVersion: "15706"
    uid: 60933469-6f70-401b-ad32-9f2796a1dfae
  spec:
    sourcePod: network-check-source-869dcfcdcd-rhpkz
    targetEndpoint: a15e27fca507f47498b99e22b948bb9a-1f91b4c64f2109c8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T13:19:17Z"
      message: 'load-balancer-api-internal: tcp connection to a15e27fca507f47498b99e22b948bb9a-1f91b4c64f2109c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.589951ms
      message: 'load-balancer-api-internal: tcp connection to a15e27fca507f47498b99e22b948bb9a-1f91b4c64f2109c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:19:17Z"
    - latency: 7.968752ms
      message: 'load-balancer-api-internal: resolved host name a15e27fca507f47498b99e22b948bb9a-1f91b4c64f2109c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:19:17Z"
    - latency: 4.190585ms
      message: 'load-balancer-api-internal: tcp connection to a15e27fca507f47498b99e22b948bb9a-1f91b4c64f2109c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:18:17Z"
    - latency: 9.810416ms
      message: 'load-balancer-api-internal: resolved host name a15e27fca507f47498b99e22b948bb9a-1f91b4c64f2109c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:18:17Z"
    - latency: 5.096063ms
      message: 'load-balancer-api-internal: tcp connection to a15e27fca507f47498b99e22b948bb9a-1f91b4c64f2109c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:17:17Z"
    - latency: 7.868686ms
      message: 'load-balancer-api-internal: resolved host name a15e27fca507f47498b99e22b948bb9a-1f91b4c64f2109c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:17:17Z"
    - latency: 5.80025ms
      message: 'load-balancer-api-internal: tcp connection to a15e27fca507f47498b99e22b948bb9a-1f91b4c64f2109c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:16:17Z"
    - latency: 8.038705ms
      message: 'load-balancer-api-internal: resolved host name a15e27fca507f47498b99e22b948bb9a-1f91b4c64f2109c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:16:17Z"
    - latency: 3.67191ms
      message: 'load-balancer-api-internal: tcp connection to a15e27fca507f47498b99e22b948bb9a-1f91b4c64f2109c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:15:17Z"
    - latency: 14.908581ms
      message: 'load-balancer-api-internal: resolved host name a15e27fca507f47498b99e22b948bb9a-1f91b4c64f2109c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:15:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:13:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-25-to-network-check-target-ip-10-0-128-4
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-25.ec2.internal
      uid: b0251a96-da67-4661-b60d-690791a8cdf9
    resourceVersion: "16144"
    uid: 6363c7cb-3392-4b69-868c-85c3ed293598
  spec:
    sourcePod: network-check-source-869dcfcdcd-rhpkz
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T13:20:17Z"
      message: 'network-check-target-ip-10-0-128-4: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.915081ms
      message: 'network-check-target-ip-10-0-128-4: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:20:17Z"
    - latency: 2.075249ms
      message: 'network-check-target-ip-10-0-128-4: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:19:17Z"
    - latency: 2.149165ms
      message: 'network-check-target-ip-10-0-128-4: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:18:17Z"
    - latency: 1.988088ms
      message: 'network-check-target-ip-10-0-128-4: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:17:17Z"
    - latency: 1.938447ms
      message: 'network-check-target-ip-10-0-128-4: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:16:17Z"
    - latency: 8.640757ms
      message: 'network-check-target-ip-10-0-128-4: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:15:17Z"
    - latency: 2.170779ms
      message: 'network-check-target-ip-10-0-128-4: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:14:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:13:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-25-to-network-check-target-ip-10-0-129-104
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-25.ec2.internal
      uid: b0251a96-da67-4661-b60d-690791a8cdf9
    resourceVersion: "16143"
    uid: 7c872339-b042-4cef-bd51-f47f4c33ad3e
  spec:
    sourcePod: network-check-source-869dcfcdcd-rhpkz
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T13:20:17Z"
      message: 'network-check-target-ip-10-0-129-104: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.025346ms
      message: 'network-check-target-ip-10-0-129-104: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:20:17Z"
    - latency: 2.023173ms
      message: 'network-check-target-ip-10-0-129-104: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:19:17Z"
    - latency: 2.350525ms
      message: 'network-check-target-ip-10-0-129-104: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:18:17Z"
    - latency: 2.255162ms
      message: 'network-check-target-ip-10-0-129-104: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:17:17Z"
    - latency: 2.117654ms
      message: 'network-check-target-ip-10-0-129-104: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:16:17Z"
    - latency: 8.670519ms
      message: 'network-check-target-ip-10-0-129-104: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:15:17Z"
    - latency: 2.633588ms
      message: 'network-check-target-ip-10-0-129-104: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:14:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:13:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-25-to-network-check-target-ip-10-0-138-25
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-25.ec2.internal
      uid: b0251a96-da67-4661-b60d-690791a8cdf9
    resourceVersion: "16142"
    uid: 2c818239-5631-4ad4-a96f-0f07e04c350e
  spec:
    sourcePod: network-check-source-869dcfcdcd-rhpkz
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T13:20:17Z"
      message: 'network-check-target-ip-10-0-138-25: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 826.291µs
      message: 'network-check-target-ip-10-0-138-25: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:20:17Z"
    - latency: 780.77µs
      message: 'network-check-target-ip-10-0-138-25: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:19:17Z"
    - latency: 972.48µs
      message: 'network-check-target-ip-10-0-138-25: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:18:17Z"
    - latency: 983.035µs
      message: 'network-check-target-ip-10-0-138-25: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:17:17Z"
    - latency: 1.32796ms
      message: 'network-check-target-ip-10-0-138-25: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:16:17Z"
    - latency: 869.315µs
      message: 'network-check-target-ip-10-0-138-25: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:15:17Z"
    - latency: 1.627448ms
      message: 'network-check-target-ip-10-0-138-25: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:14:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:13:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-25-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-25.ec2.internal
      uid: b0251a96-da67-4661-b60d-690791a8cdf9
    resourceVersion: "15704"
    uid: da6c7fe5-0cf1-408c-89bd-75a574f35e5a
  spec:
    sourcePod: network-check-source-869dcfcdcd-rhpkz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T13:19:17Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 774.825µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:19:17Z"
    - latency: 1.668925ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:19:17Z"
    - latency: 803.095µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:18:17Z"
    - latency: 2.820977ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:18:17Z"
    - latency: 955.476µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:17:17Z"
    - latency: 1.833869ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:17:17Z"
    - latency: 826.395µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:16:17Z"
    - latency: 1.868294ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:16:17Z"
    - latency: 914.943µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:15:17Z"
    - latency: 8.356336ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:15:17Z"
kind: List
metadata:
  resourceVersion: ""