apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T14:56:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-199-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-199.ec2.internal
      uid: b3a08503-3f11-409f-baba-d8316d75472e
    resourceVersion: "23331"
    uid: f6afccb1-3220-4eb3-af6b-d8b6342eb686
  spec:
    sourcePod: network-check-source-56499946bc-f24dp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:03:30Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 833.056µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:03:29Z"
    - latency: 1.308349ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:02:29Z"
    - latency: 2.247836ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:01:29Z"
    - latency: 1.088242ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:00:29Z"
    - latency: 800.058µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:59:29Z"
    - latency: 861.923µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:58:29Z"
    - latency: 837.897µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:57:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T14:56:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-199-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-199.ec2.internal
      uid: b3a08503-3f11-409f-baba-d8316d75472e
    resourceVersion: "22338"
    uid: 8c8b26fc-5ce6-48c3-9e66-b02f00731dad
  spec:
    sourcePod: network-check-source-56499946bc-f24dp
    targetEndpoint: ae4a1e751e26a4805ac4477c480b8019-17a7800559aba308.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:02:30Z"
      message: 'load-balancer-api-external: tcp connection to ae4a1e751e26a4805ac4477c480b8019-17a7800559aba308.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.735432ms
      message: 'load-balancer-api-external: tcp connection to ae4a1e751e26a4805ac4477c480b8019-17a7800559aba308.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:02:29Z"
    - latency: 6.574808ms
      message: 'load-balancer-api-external: resolved host name ae4a1e751e26a4805ac4477c480b8019-17a7800559aba308.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:02:29Z"
    - latency: 3.742659ms
      message: 'load-balancer-api-external: tcp connection to ae4a1e751e26a4805ac4477c480b8019-17a7800559aba308.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:01:30Z"
    - latency: 9.386706ms
      message: 'load-balancer-api-external: resolved host name ae4a1e751e26a4805ac4477c480b8019-17a7800559aba308.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:01:29Z"
    - latency: 6.083182ms
      message: 'load-balancer-api-external: tcp connection to ae4a1e751e26a4805ac4477c480b8019-17a7800559aba308.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:00:30Z"
    - latency: 10.944313ms
      message: 'load-balancer-api-external: resolved host name ae4a1e751e26a4805ac4477c480b8019-17a7800559aba308.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:00:29Z"
    - latency: 5.206938ms
      message: 'load-balancer-api-external: tcp connection to ae4a1e751e26a4805ac4477c480b8019-17a7800559aba308.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:59:29Z"
    - latency: 8.312602ms
      message: 'load-balancer-api-external: resolved host name ae4a1e751e26a4805ac4477c480b8019-17a7800559aba308.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:59:29Z"
    - latency: 4.584451ms
      message: 'load-balancer-api-external: tcp connection to ae4a1e751e26a4805ac4477c480b8019-17a7800559aba308.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:58:30Z"
    - latency: 9.907705ms
      message: 'load-balancer-api-external: resolved host name ae4a1e751e26a4805ac4477c480b8019-17a7800559aba308.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:58:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T14:56:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-199-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-199.ec2.internal
      uid: b3a08503-3f11-409f-baba-d8316d75472e
    resourceVersion: "22337"
    uid: 48106635-0c7e-4f0d-a030-4cfb99501358
  spec:
    sourcePod: network-check-source-56499946bc-f24dp
    targetEndpoint: ae4a1e751e26a4805ac4477c480b8019-17a7800559aba308.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:02:30Z"
      message: 'load-balancer-api-internal: tcp connection to ae4a1e751e26a4805ac4477c480b8019-17a7800559aba308.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.724352ms
      message: 'load-balancer-api-internal: tcp connection to ae4a1e751e26a4805ac4477c480b8019-17a7800559aba308.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:02:29Z"
    - latency: 6.532006ms
      message: 'load-balancer-api-internal: resolved host name ae4a1e751e26a4805ac4477c480b8019-17a7800559aba308.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:02:29Z"
    - latency: 4.953185ms
      message: 'load-balancer-api-internal: tcp connection to ae4a1e751e26a4805ac4477c480b8019-17a7800559aba308.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:01:30Z"
    - latency: 9.501577ms
      message: 'load-balancer-api-internal: resolved host name ae4a1e751e26a4805ac4477c480b8019-17a7800559aba308.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:01:29Z"
    - latency: 6.112223ms
      message: 'load-balancer-api-internal: tcp connection to ae4a1e751e26a4805ac4477c480b8019-17a7800559aba308.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:00:30Z"
    - latency: 10.996007ms
      message: 'load-balancer-api-internal: resolved host name ae4a1e751e26a4805ac4477c480b8019-17a7800559aba308.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:00:29Z"
    - latency: 5.19947ms
      message: 'load-balancer-api-internal: tcp connection to ae4a1e751e26a4805ac4477c480b8019-17a7800559aba308.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:59:29Z"
    - latency: 8.253067ms
      message: 'load-balancer-api-internal: resolved host name ae4a1e751e26a4805ac4477c480b8019-17a7800559aba308.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:59:29Z"
    - latency: 4.655728ms
      message: 'load-balancer-api-internal: tcp connection to ae4a1e751e26a4805ac4477c480b8019-17a7800559aba308.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:58:30Z"
    - latency: 9.87384ms
      message: 'load-balancer-api-internal: resolved host name ae4a1e751e26a4805ac4477c480b8019-17a7800559aba308.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:58:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T14:56:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-199-to-network-check-target-ip-10-0-128-44
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-199.ec2.internal
      uid: b3a08503-3f11-409f-baba-d8316d75472e
    resourceVersion: "23329"
    uid: 2266d568-123a-4e18-b0cc-f569d9584682
  spec:
    sourcePod: network-check-source-56499946bc-f24dp
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:03:29Z"
      message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.963049ms
      message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:03:29Z"
    - latency: 2.195322ms
      message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:02:29Z"
    - latency: 2.562166ms
      message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:01:29Z"
    - latency: 2.619664ms
      message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:00:29Z"
    - latency: 2.072062ms
      message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:59:29Z"
    - latency: 3.249729ms
      message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:58:29Z"
    - latency: 2.144988ms
      message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:57:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T14:56:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-199-to-network-check-target-ip-10-0-131-199
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-199.ec2.internal
      uid: b3a08503-3f11-409f-baba-d8316d75472e
    resourceVersion: "23328"
    uid: 336762ec-fe51-428f-9e49-ab1b576ba680
  spec:
    sourcePod: network-check-source-56499946bc-f24dp
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:03:29Z"
      message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 695.346µs
      message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:03:29Z"
    - latency: 891.088µs
      message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:02:29Z"
    - latency: 2.358518ms
      message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:01:29Z"
    - latency: 1.611833ms
      message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:00:29Z"
    - latency: 813.128µs
      message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:59:29Z"
    - latency: 787.737µs
      message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:58:29Z"
    - latency: 1.792171ms
      message: 'network-check-target-ip-10-0-131-199: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:57:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T14:56:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-199-to-network-check-target-ip-10-0-141-121
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-199.ec2.internal
      uid: b3a08503-3f11-409f-baba-d8316d75472e
    resourceVersion: "23330"
    uid: 06ca69fe-3612-44a6-a9d5-070768fe6b96
  spec:
    sourcePod: network-check-source-56499946bc-f24dp
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:03:29Z"
      message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.388831ms
      message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:03:29Z"
    - latency: 2.199889ms
      message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:02:29Z"
    - latency: 2.519188ms
      message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:01:29Z"
    - latency: 2.403615ms
      message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:00:29Z"
    - latency: 2.078504ms
      message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:59:29Z"
    - latency: 3.443263ms
      message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:58:29Z"
    - latency: 2.281496ms
      message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:57:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T14:56:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-199-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-199.ec2.internal
      uid: b3a08503-3f11-409f-baba-d8316d75472e
    resourceVersion: "22336"
    uid: b66df88e-5b48-4324-9421-fd86482f9ce5
  spec:
    sourcePod: network-check-source-56499946bc-f24dp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:02:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.072735ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:02:29Z"
    - latency: 1.955977ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:02:29Z"
    - latency: 950.187µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:01:29Z"
    - latency: 2.5353ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:01:29Z"
    - latency: 5.059515ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:00:29Z"
    - latency: 2.617876ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:00:29Z"
    - latency: 862.444µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:59:29Z"
    - latency: 1.720166ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:59:29Z"
    - latency: 1.924085ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:58:29Z"
    - latency: 2.514646ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:58:29Z"
kind: List
metadata:
  resourceVersion: ""