apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T10:36:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-0-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-0.ec2.internal
      uid: b043f519-e6b5-404a-885e-cce5b72dce04
    resourceVersion: "14334"
    uid: 54ed3573-4210-40ab-9507-0f1ccc1034bd
  spec:
    sourcePod: network-check-source-65bdbbff45-xdk84
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T10:43:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.143148ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:43:26Z"
    - latency: 865.608µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:42:26Z"
    - latency: 1.353751ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:41:26Z"
    - latency: 897.344µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:40:26Z"
    - latency: 1.034867ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:39:26Z"
    - latency: 866.953µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:38:26Z"
    - latency: 1.49921ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:37:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T10:36:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-0-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-0.ec2.internal
      uid: b043f519-e6b5-404a-885e-cce5b72dce04
    resourceVersion: "14000"
    uid: f806e486-8e50-4832-8a97-f1d68b73c8f4
  spec:
    sourcePod: network-check-source-65bdbbff45-xdk84
    targetEndpoint: ae3c2960a932d4a64ac054bfc6d40994-42f3f97fe9f08f23.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T10:42:26Z"
      message: 'load-balancer-api-external: tcp connection to ae3c2960a932d4a64ac054bfc6d40994-42f3f97fe9f08f23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.413198ms
      message: 'load-balancer-api-external: tcp connection to ae3c2960a932d4a64ac054bfc6d40994-42f3f97fe9f08f23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:42:26Z"
    - latency: 6.105317ms
      message: 'load-balancer-api-external: resolved host name ae3c2960a932d4a64ac054bfc6d40994-42f3f97fe9f08f23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T10:42:26Z"
    - latency: 4.119965ms
      message: 'load-balancer-api-external: tcp connection to ae3c2960a932d4a64ac054bfc6d40994-42f3f97fe9f08f23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:41:26Z"
    - latency: 7.005412ms
      message: 'load-balancer-api-external: resolved host name ae3c2960a932d4a64ac054bfc6d40994-42f3f97fe9f08f23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T10:41:26Z"
    - latency: 6.686371ms
      message: 'load-balancer-api-external: tcp connection to ae3c2960a932d4a64ac054bfc6d40994-42f3f97fe9f08f23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:40:26Z"
    - latency: 7.285661ms
      message: 'load-balancer-api-external: resolved host name ae3c2960a932d4a64ac054bfc6d40994-42f3f97fe9f08f23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T10:40:26Z"
    - latency: 5.663804ms
      message: 'load-balancer-api-external: tcp connection to ae3c2960a932d4a64ac054bfc6d40994-42f3f97fe9f08f23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:39:26Z"
    - latency: 7.099502ms
      message: 'load-balancer-api-external: resolved host name ae3c2960a932d4a64ac054bfc6d40994-42f3f97fe9f08f23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T10:39:26Z"
    - latency: 5.650585ms
      message: 'load-balancer-api-external: tcp connection to ae3c2960a932d4a64ac054bfc6d40994-42f3f97fe9f08f23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:38:26Z"
    - latency: 6.47146ms
      message: 'load-balancer-api-external: resolved host name ae3c2960a932d4a64ac054bfc6d40994-42f3f97fe9f08f23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T10:38:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T10:36:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-0-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-0.ec2.internal
      uid: b043f519-e6b5-404a-885e-cce5b72dce04
    resourceVersion: "13999"
    uid: 83a5b04e-af2c-4e79-8423-4e93f1d91e48
  spec:
    sourcePod: network-check-source-65bdbbff45-xdk84
    targetEndpoint: ae3c2960a932d4a64ac054bfc6d40994-42f3f97fe9f08f23.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T10:42:26Z"
      message: 'load-balancer-api-internal: tcp connection to ae3c2960a932d4a64ac054bfc6d40994-42f3f97fe9f08f23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.677792ms
      message: 'load-balancer-api-internal: tcp connection to ae3c2960a932d4a64ac054bfc6d40994-42f3f97fe9f08f23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:42:26Z"
    - latency: 6.130235ms
      message: 'load-balancer-api-internal: resolved host name ae3c2960a932d4a64ac054bfc6d40994-42f3f97fe9f08f23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T10:42:26Z"
    - latency: 4.35669ms
      message: 'load-balancer-api-internal: tcp connection to ae3c2960a932d4a64ac054bfc6d40994-42f3f97fe9f08f23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:41:26Z"
    - latency: 7.028394ms
      message: 'load-balancer-api-internal: resolved host name ae3c2960a932d4a64ac054bfc6d40994-42f3f97fe9f08f23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T10:41:26Z"
    - latency: 6.686107ms
      message: 'load-balancer-api-internal: tcp connection to ae3c2960a932d4a64ac054bfc6d40994-42f3f97fe9f08f23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:40:26Z"
    - latency: 7.34158ms
      message: 'load-balancer-api-internal: resolved host name ae3c2960a932d4a64ac054bfc6d40994-42f3f97fe9f08f23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T10:40:26Z"
    - latency: 5.549072ms
      message: 'load-balancer-api-internal: tcp connection to ae3c2960a932d4a64ac054bfc6d40994-42f3f97fe9f08f23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:39:26Z"
    - latency: 7.156403ms
      message: 'load-balancer-api-internal: resolved host name ae3c2960a932d4a64ac054bfc6d40994-42f3f97fe9f08f23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T10:39:26Z"
    - latency: 5.884749ms
      message: 'load-balancer-api-internal: tcp connection to ae3c2960a932d4a64ac054bfc6d40994-42f3f97fe9f08f23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:38:26Z"
    - latency: 6.488671ms
      message: 'load-balancer-api-internal: resolved host name ae3c2960a932d4a64ac054bfc6d40994-42f3f97fe9f08f23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T10:38:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T10:36:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-0-to-network-check-target-ip-10-0-130-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-0.ec2.internal
      uid: b043f519-e6b5-404a-885e-cce5b72dce04
    resourceVersion: "14331"
    uid: e9fa5023-f304-46d5-8a1e-dd5f8a8a5f6e
  spec:
    sourcePod: network-check-source-65bdbbff45-xdk84
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T10:43:26Z"
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.867561ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:43:26Z"
    - latency: 2.095043ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:42:26Z"
    - latency: 1.83675ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:41:26Z"
    - latency: 1.836307ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:40:26Z"
    - latency: 1.814123ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:39:26Z"
    - latency: 1.873154ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:38:26Z"
    - latency: 2.071671ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:37:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T10:36:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-0-to-network-check-target-ip-10-0-136-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-0.ec2.internal
      uid: b043f519-e6b5-404a-885e-cce5b72dce04
    resourceVersion: "14333"
    uid: 9b6e243a-5d6d-4b48-a389-0fd21449f49e
  spec:
    sourcePod: network-check-source-65bdbbff45-xdk84
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T10:43:26Z"
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.195609ms
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:43:26Z"
    - latency: 854.552µs
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:42:26Z"
    - latency: 934.34µs
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:41:26Z"
    - latency: 923.357µs
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:40:26Z"
    - latency: 977.336µs
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:39:26Z"
    - latency: 1.48471ms
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:38:26Z"
    - latency: 2.546133ms
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:37:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T10:36:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-0-to-network-check-target-ip-10-0-143-67
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-0.ec2.internal
      uid: b043f519-e6b5-404a-885e-cce5b72dce04
    resourceVersion: "14332"
    uid: 9a815c16-508e-47bd-8231-74487e35b1ef
  spec:
    sourcePod: network-check-source-65bdbbff45-xdk84
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T10:43:26Z"
      message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.901055ms
      message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:43:26Z"
    - latency: 1.790376ms
      message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:42:26Z"
    - latency: 2.048197ms
      message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:41:26Z"
    - latency: 1.9099ms
      message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:40:26Z"
    - latency: 2.227415ms
      message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:39:26Z"
    - latency: 2.112009ms
      message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:38:26Z"
    - latency: 2.142953ms
      message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:37:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T10:36:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-0-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-0.ec2.internal
      uid: b043f519-e6b5-404a-885e-cce5b72dce04
    resourceVersion: "13998"
    uid: 0fe306ac-9c47-463e-989f-05cfa4531446
  spec:
    sourcePod: network-check-source-65bdbbff45-xdk84
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T10:42:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.045483ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:42:26Z"
    - latency: 1.78919ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T10:42:26Z"
    - latency: 933.802µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:41:26Z"
    - latency: 2.108606ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T10:41:26Z"
    - latency: 900.543µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:40:26Z"
    - latency: 2.249578ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T10:40:26Z"
    - latency: 780.446µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:39:26Z"
    - latency: 2.049301ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T10:39:26Z"
    - latency: 903.8µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T10:38:26Z"
    - latency: 2.031218ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T10:38:26Z"
kind: List
metadata:
  resourceVersion: ""