apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T14:57:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-64-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-64.ec2.internal
      uid: 6c0987f0-be45-4f5c-8afb-110d723688c2
    resourceVersion: "22371"
    uid: aa6f4280-40d9-42f6-a587-f5138f14598e
  spec:
    sourcePod: network-check-source-56499946bc-8cxbn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:04:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 983.928µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:04:40Z"
    - latency: 853.757µ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:40Z"
    - latency: 1.136974ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:02:40Z"
    - latency: 1.015541ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:01:40Z"
    - latency: 980.043µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:00:40Z"
    - latency: 798.403µ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:40Z"
    - latency: 947.722µ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:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T14:57:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-64-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-64.ec2.internal
      uid: 6c0987f0-be45-4f5c-8afb-110d723688c2
    resourceVersion: "26882"
    uid: 8658fd6f-4300-4b21-ba0c-941025cf2dd0
  spec:
    sourcePod: network-check-source-56499946bc-8cxbn
    targetEndpoint: a510bfb6ca8454e5c95eb0c41e43c109-4be09fb1e334b937.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:03:40Z"
      message: 'load-balancer-api-external: tcp connection to a510bfb6ca8454e5c95eb0c41e43c109-4be09fb1e334b937.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.232712ms
      message: 'load-balancer-api-external: tcp connection to a510bfb6ca8454e5c95eb0c41e43c109-4be09fb1e334b937.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:09:40Z"
    - latency: 7.264791ms
      message: 'load-balancer-api-external: resolved host name a510bfb6ca8454e5c95eb0c41e43c109-4be09fb1e334b937.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:09:40Z"
    - latency: 8.102835ms
      message: 'load-balancer-api-external: tcp connection to a510bfb6ca8454e5c95eb0c41e43c109-4be09fb1e334b937.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:08:40Z"
    - latency: 6.20243ms
      message: 'load-balancer-api-external: resolved host name a510bfb6ca8454e5c95eb0c41e43c109-4be09fb1e334b937.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:08:40Z"
    - latency: 4.710687ms
      message: 'load-balancer-api-external: tcp connection to a510bfb6ca8454e5c95eb0c41e43c109-4be09fb1e334b937.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:07:40Z"
    - latency: 8.259249ms
      message: 'load-balancer-api-external: resolved host name a510bfb6ca8454e5c95eb0c41e43c109-4be09fb1e334b937.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:07:40Z"
    - latency: 5.299728ms
      message: 'load-balancer-api-external: tcp connection to a510bfb6ca8454e5c95eb0c41e43c109-4be09fb1e334b937.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:06:40Z"
    - latency: 7.057161ms
      message: 'load-balancer-api-external: resolved host name a510bfb6ca8454e5c95eb0c41e43c109-4be09fb1e334b937.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:06:40Z"
    - latency: 5.57209ms
      message: 'load-balancer-api-external: tcp connection to a510bfb6ca8454e5c95eb0c41e43c109-4be09fb1e334b937.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:05:40Z"
    - latency: 7.005419ms
      message: 'load-balancer-api-external: resolved host name a510bfb6ca8454e5c95eb0c41e43c109-4be09fb1e334b937.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:05:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T14:57:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-64-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-64.ec2.internal
      uid: 6c0987f0-be45-4f5c-8afb-110d723688c2
    resourceVersion: "26881"
    uid: f2ec7f98-9720-43af-9b6a-0709e181c6a5
  spec:
    sourcePod: network-check-source-56499946bc-8cxbn
    targetEndpoint: a510bfb6ca8454e5c95eb0c41e43c109-4be09fb1e334b937.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:03:40Z"
      message: 'load-balancer-api-internal: tcp connection to a510bfb6ca8454e5c95eb0c41e43c109-4be09fb1e334b937.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.275007ms
      message: 'load-balancer-api-internal: tcp connection to a510bfb6ca8454e5c95eb0c41e43c109-4be09fb1e334b937.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:09:40Z"
    - latency: 7.305576ms
      message: 'load-balancer-api-internal: resolved host name a510bfb6ca8454e5c95eb0c41e43c109-4be09fb1e334b937.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:09:40Z"
    - latency: 4.396237ms
      message: 'load-balancer-api-internal: tcp connection to a510bfb6ca8454e5c95eb0c41e43c109-4be09fb1e334b937.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:08:40Z"
    - latency: 6.234911ms
      message: 'load-balancer-api-internal: resolved host name a510bfb6ca8454e5c95eb0c41e43c109-4be09fb1e334b937.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:08:40Z"
    - latency: 4.673994ms
      message: 'load-balancer-api-internal: tcp connection to a510bfb6ca8454e5c95eb0c41e43c109-4be09fb1e334b937.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:07:40Z"
    - latency: 8.313729ms
      message: 'load-balancer-api-internal: resolved host name a510bfb6ca8454e5c95eb0c41e43c109-4be09fb1e334b937.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:07:40Z"
    - latency: 5.773894ms
      message: 'load-balancer-api-internal: tcp connection to a510bfb6ca8454e5c95eb0c41e43c109-4be09fb1e334b937.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:06:40Z"
    - latency: 7.084893ms
      message: 'load-balancer-api-internal: resolved host name a510bfb6ca8454e5c95eb0c41e43c109-4be09fb1e334b937.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:06:40Z"
    - latency: 5.553645ms
      message: 'load-balancer-api-internal: tcp connection to a510bfb6ca8454e5c95eb0c41e43c109-4be09fb1e334b937.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:05:40Z"
    - latency: 7.014532ms
      message: 'load-balancer-api-internal: resolved host name a510bfb6ca8454e5c95eb0c41e43c109-4be09fb1e334b937.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:05:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T14:57:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-64-to-network-check-target-ip-10-0-132-64
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-64.ec2.internal
      uid: 6c0987f0-be45-4f5c-8afb-110d723688c2
    resourceVersion: "22368"
    uid: 7c672c0c-af55-47f3-8162-43eded6af1db
  spec:
    sourcePod: network-check-source-56499946bc-8cxbn
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:04:40Z"
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 747.351µs
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:04:40Z"
    - latency: 1.586378ms
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:03:40Z"
    - latency: 817.202µs
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:02:40Z"
    - latency: 1.488569ms
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:01:40Z"
    - latency: 1.357279ms
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:00:40Z"
    - latency: 705.812µs
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:59:40Z"
    - latency: 1.606922ms
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:58:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T14:57:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-64-to-network-check-target-ip-10-0-138-55
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-64.ec2.internal
      uid: 6c0987f0-be45-4f5c-8afb-110d723688c2
    resourceVersion: "22370"
    uid: e402528f-9339-4c57-8294-cebf45e81937
  spec:
    sourcePod: network-check-source-56499946bc-8cxbn
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:04:40Z"
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.183934ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:04:40Z"
    - latency: 2.4007ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:03:40Z"
    - latency: 2.167844ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:02:40Z"
    - latency: 2.356624ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:01:40Z"
    - latency: 2.165662ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:00:40Z"
    - latency: 2.185835ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:59:40Z"
    - latency: 2.193442ms
      message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:58:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T14:57:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-64-to-network-check-target-ip-10-0-140-104
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-64.ec2.internal
      uid: 6c0987f0-be45-4f5c-8afb-110d723688c2
    resourceVersion: "22369"
    uid: c2bcb44f-540b-4bd4-bb28-7f185d508de0
  spec:
    sourcePod: network-check-source-56499946bc-8cxbn
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:04:40Z"
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.912851ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:04:40Z"
    - latency: 1.967675ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:03:40Z"
    - latency: 1.918991ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:02:40Z"
    - latency: 1.896608ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:01:40Z"
    - latency: 1.537325ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:00:40Z"
    - latency: 1.663578ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:59:40Z"
    - latency: 1.840033ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:58:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T14:57:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-64-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-64.ec2.internal
      uid: 6c0987f0-be45-4f5c-8afb-110d723688c2
    resourceVersion: "26880"
    uid: b77d0652-01ca-408c-8776-ad870901efdb
  spec:
    sourcePod: network-check-source-56499946bc-8cxbn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:03:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 884.128µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:09:40Z"
    - latency: 1.670849ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:09:40Z"
    - latency: 1.048879ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:08:40Z"
    - latency: 1.607632ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:08:40Z"
    - latency: 926.739µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:07:40Z"
    - latency: 1.684268ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:07:40Z"
    - latency: 911.535µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:06:40Z"
    - latency: 1.705476ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:06:40Z"
    - latency: 835.765µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:05:40Z"
    - latency: 1.873903ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:05:40Z"
kind: List
metadata:
  resourceVersion: ""