apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:09:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-89-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-89.ec2.internal
      uid: 24942e8c-fc51-4c08-b6bb-523414b1774a
    resourceVersion: "15309"
    uid: f1576fb3-50ad-4cee-95d0-3dc5b3eda0d7
  spec:
    sourcePod: network-check-source-7d88cb55d8-fz9km
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T15:16:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.109235ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:16:56Z"
    - latency: 968.477µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:15:56Z"
    - latency: 1.026764ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:14:56Z"
    - latency: 906.761µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:13:56Z"
    - latency: 1.07605ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:12:56Z"
    - latency: 1.217008ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:11:56Z"
    - latency: 1.072918ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:10:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:09:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-89-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-89.ec2.internal
      uid: 24942e8c-fc51-4c08-b6bb-523414b1774a
    resourceVersion: "17034"
    uid: 3c140101-9645-41a8-ac59-29a13e577dff
  spec:
    sourcePod: network-check-source-7d88cb55d8-fz9km
    targetEndpoint: a9205a9b698a044c68825063332f86c4-305dddf79d8f7c03.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T15:15:56Z"
      message: 'load-balancer-api-external: tcp connection to a9205a9b698a044c68825063332f86c4-305dddf79d8f7c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.964283ms
      message: 'load-balancer-api-external: tcp connection to a9205a9b698a044c68825063332f86c4-305dddf79d8f7c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:21:56Z"
    - latency: 9.091028ms
      message: 'load-balancer-api-external: resolved host name a9205a9b698a044c68825063332f86c4-305dddf79d8f7c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:21:56Z"
    - latency: 4.535133ms
      message: 'load-balancer-api-external: tcp connection to a9205a9b698a044c68825063332f86c4-305dddf79d8f7c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:20:56Z"
    - latency: 10.069995ms
      message: 'load-balancer-api-external: resolved host name a9205a9b698a044c68825063332f86c4-305dddf79d8f7c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:20:56Z"
    - latency: 4.000849ms
      message: 'load-balancer-api-external: tcp connection to a9205a9b698a044c68825063332f86c4-305dddf79d8f7c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:19:56Z"
    - latency: 8.004318ms
      message: 'load-balancer-api-external: resolved host name a9205a9b698a044c68825063332f86c4-305dddf79d8f7c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:19:56Z"
    - latency: 3.880964ms
      message: 'load-balancer-api-external: tcp connection to a9205a9b698a044c68825063332f86c4-305dddf79d8f7c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:18:56Z"
    - latency: 9.278502ms
      message: 'load-balancer-api-external: resolved host name a9205a9b698a044c68825063332f86c4-305dddf79d8f7c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:18:56Z"
    - latency: 4.348302ms
      message: 'load-balancer-api-external: tcp connection to a9205a9b698a044c68825063332f86c4-305dddf79d8f7c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:17:56Z"
    - latency: 8.867203ms
      message: 'load-balancer-api-external: resolved host name a9205a9b698a044c68825063332f86c4-305dddf79d8f7c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:17:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:09:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-89-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-89.ec2.internal
      uid: 24942e8c-fc51-4c08-b6bb-523414b1774a
    resourceVersion: "17035"
    uid: 1294146c-729e-44bb-af61-2668652f382e
  spec:
    sourcePod: network-check-source-7d88cb55d8-fz9km
    targetEndpoint: a9205a9b698a044c68825063332f86c4-305dddf79d8f7c03.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T15:15:56Z"
      message: 'load-balancer-api-internal: tcp connection to a9205a9b698a044c68825063332f86c4-305dddf79d8f7c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.973246ms
      message: 'load-balancer-api-internal: tcp connection to a9205a9b698a044c68825063332f86c4-305dddf79d8f7c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:21:56Z"
    - latency: 9.161667ms
      message: 'load-balancer-api-internal: resolved host name a9205a9b698a044c68825063332f86c4-305dddf79d8f7c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:21:56Z"
    - latency: 4.603692ms
      message: 'load-balancer-api-internal: tcp connection to a9205a9b698a044c68825063332f86c4-305dddf79d8f7c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:20:56Z"
    - latency: 10.018371ms
      message: 'load-balancer-api-internal: resolved host name a9205a9b698a044c68825063332f86c4-305dddf79d8f7c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:20:56Z"
    - latency: 4.015362ms
      message: 'load-balancer-api-internal: tcp connection to a9205a9b698a044c68825063332f86c4-305dddf79d8f7c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:19:56Z"
    - latency: 7.956175ms
      message: 'load-balancer-api-internal: resolved host name a9205a9b698a044c68825063332f86c4-305dddf79d8f7c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:19:56Z"
    - latency: 4.682494ms
      message: 'load-balancer-api-internal: tcp connection to a9205a9b698a044c68825063332f86c4-305dddf79d8f7c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:18:56Z"
    - latency: 9.201874ms
      message: 'load-balancer-api-internal: resolved host name a9205a9b698a044c68825063332f86c4-305dddf79d8f7c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:18:56Z"
    - latency: 4.281253ms
      message: 'load-balancer-api-internal: tcp connection to a9205a9b698a044c68825063332f86c4-305dddf79d8f7c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:17:56Z"
    - latency: 8.906789ms
      message: 'load-balancer-api-internal: resolved host name a9205a9b698a044c68825063332f86c4-305dddf79d8f7c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:17:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:09:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-89-to-network-check-target-ip-10-0-131-89
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-89.ec2.internal
      uid: 24942e8c-fc51-4c08-b6bb-523414b1774a
    resourceVersion: "15306"
    uid: 643c8638-3743-40c8-9fb8-e8ff7d500f7b
  spec:
    sourcePod: network-check-source-7d88cb55d8-fz9km
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T15:16:56Z"
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.471181ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:16:56Z"
    - latency: 1.016666ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:15:56Z"
    - latency: 1.264389ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:14:56Z"
    - latency: 869.722µs
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:13:56Z"
    - latency: 990.183µs
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:12:56Z"
    - latency: 1.300642ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:11:56Z"
    - latency: 1.826495ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:10:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:09:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-89-to-network-check-target-ip-10-0-135-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-89.ec2.internal
      uid: 24942e8c-fc51-4c08-b6bb-523414b1774a
    resourceVersion: "15307"
    uid: fe62a444-fa65-4b55-af46-fd5fe78cb83a
  spec:
    sourcePod: network-check-source-7d88cb55d8-fz9km
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T15:16:56Z"
      message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.355395ms
      message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:16:56Z"
    - latency: 2.496811ms
      message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:15:56Z"
    - latency: 2.529982ms
      message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:14:56Z"
    - latency: 2.266806ms
      message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:13:56Z"
    - latency: 2.493941ms
      message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:12:56Z"
    - latency: 2.556134ms
      message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:11:56Z"
    - latency: 2.583221ms
      message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:10:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:09:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-89-to-network-check-target-ip-10-0-140-209
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-89.ec2.internal
      uid: 24942e8c-fc51-4c08-b6bb-523414b1774a
    resourceVersion: "15308"
    uid: 32baf763-821f-4993-a493-b463999514d7
  spec:
    sourcePod: network-check-source-7d88cb55d8-fz9km
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T15:16:56Z"
      message: 'network-check-target-ip-10-0-140-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.742933ms
      message: 'network-check-target-ip-10-0-140-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:16:56Z"
    - latency: 2.081873ms
      message: 'network-check-target-ip-10-0-140-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:15:56Z"
    - latency: 2.274214ms
      message: 'network-check-target-ip-10-0-140-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:14:56Z"
    - latency: 2.313925ms
      message: 'network-check-target-ip-10-0-140-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:13:56Z"
    - latency: 2.413445ms
      message: 'network-check-target-ip-10-0-140-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:12:56Z"
    - latency: 2.553615ms
      message: 'network-check-target-ip-10-0-140-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:11:56Z"
    - latency: 2.093028ms
      message: 'network-check-target-ip-10-0-140-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:10:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:09:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-89-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-89.ec2.internal
      uid: 24942e8c-fc51-4c08-b6bb-523414b1774a
    resourceVersion: "17033"
    uid: 324396cc-54d6-40e0-9f46-1878e5f5a932
  spec:
    sourcePod: network-check-source-7d88cb55d8-fz9km
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T15:15:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 818.078µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:21:56Z"
    - latency: 1.677543ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:21:56Z"
    - latency: 1.205452ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:20:56Z"
    - latency: 1.681703ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:20:56Z"
    - latency: 823.875µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:19:56Z"
    - latency: 1.586597ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:19:56Z"
    - latency: 1.032635ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:18:56Z"
    - latency: 2.070849ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:18:56Z"
    - latency: 1.078152ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:17:56Z"
    - latency: 2.043378ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:17:56Z"
kind: List
metadata:
  resourceVersion: ""