apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:39:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-74-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-74.ec2.internal
      uid: 4a864c02-753a-4ae3-bcb5-8561b7212160
    resourceVersion: "22853"
    uid: 8e89f5d3-dc83-4809-9eb2-8e6a3034680e
  spec:
    sourcePod: network-check-source-56499946bc-qgm9j
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:46:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.590119ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:46:09Z"
    - latency: 1.067637ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:45:09Z"
    - latency: 1.069526ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:44:09Z"
    - latency: 909.663µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:43:09Z"
    - latency: 943.624µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:42:09Z"
    - latency: 1.125325ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:41:09Z"
    - latency: 1.112871ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:40:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:39:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-74-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-74.ec2.internal
      uid: 4a864c02-753a-4ae3-bcb5-8561b7212160
    resourceVersion: "21816"
    uid: 57fccc57-8368-4dc1-a602-9a86fa5c7df7
  spec:
    sourcePod: network-check-source-56499946bc-qgm9j
    targetEndpoint: a583b133831ff488b992bd981a386506-a260bd53b926b82a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:45:09Z"
      message: 'load-balancer-api-external: tcp connection to a583b133831ff488b992bd981a386506-a260bd53b926b82a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 9.136603ms
      message: 'load-balancer-api-external: tcp connection to a583b133831ff488b992bd981a386506-a260bd53b926b82a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:45:09Z"
    - latency: 9.218667ms
      message: 'load-balancer-api-external: resolved host name a583b133831ff488b992bd981a386506-a260bd53b926b82a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:45:09Z"
    - latency: 5.860569ms
      message: 'load-balancer-api-external: tcp connection to a583b133831ff488b992bd981a386506-a260bd53b926b82a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:44:09Z"
    - latency: 8.61456ms
      message: 'load-balancer-api-external: resolved host name a583b133831ff488b992bd981a386506-a260bd53b926b82a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:44:09Z"
    - latency: 5.824577ms
      message: 'load-balancer-api-external: tcp connection to a583b133831ff488b992bd981a386506-a260bd53b926b82a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:43:09Z"
    - latency: 8.119525ms
      message: 'load-balancer-api-external: resolved host name a583b133831ff488b992bd981a386506-a260bd53b926b82a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:43:09Z"
    - latency: 4.861496ms
      message: 'load-balancer-api-external: tcp connection to a583b133831ff488b992bd981a386506-a260bd53b926b82a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:42:09Z"
    - latency: 8.561529ms
      message: 'load-balancer-api-external: resolved host name a583b133831ff488b992bd981a386506-a260bd53b926b82a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:42:09Z"
    - latency: 7.62803ms
      message: 'load-balancer-api-external: tcp connection to a583b133831ff488b992bd981a386506-a260bd53b926b82a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:41:09Z"
    - latency: 7.60909ms
      message: 'load-balancer-api-external: resolved host name a583b133831ff488b992bd981a386506-a260bd53b926b82a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:41:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:39:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-74-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-74.ec2.internal
      uid: 4a864c02-753a-4ae3-bcb5-8561b7212160
    resourceVersion: "21815"
    uid: 2eef85c1-d262-443f-8d0a-59c923f8f312
  spec:
    sourcePod: network-check-source-56499946bc-qgm9j
    targetEndpoint: a583b133831ff488b992bd981a386506-a260bd53b926b82a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:45:09Z"
      message: 'load-balancer-api-internal: tcp connection to a583b133831ff488b992bd981a386506-a260bd53b926b82a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.217521ms
      message: 'load-balancer-api-internal: tcp connection to a583b133831ff488b992bd981a386506-a260bd53b926b82a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:45:09Z"
    - latency: 9.33011ms
      message: 'load-balancer-api-internal: resolved host name a583b133831ff488b992bd981a386506-a260bd53b926b82a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:45:09Z"
    - latency: 5.850347ms
      message: 'load-balancer-api-internal: tcp connection to a583b133831ff488b992bd981a386506-a260bd53b926b82a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:44:09Z"
    - latency: 8.593256ms
      message: 'load-balancer-api-internal: resolved host name a583b133831ff488b992bd981a386506-a260bd53b926b82a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:44:09Z"
    - latency: 5.824894ms
      message: 'load-balancer-api-internal: tcp connection to a583b133831ff488b992bd981a386506-a260bd53b926b82a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:43:09Z"
    - latency: 8.074087ms
      message: 'load-balancer-api-internal: resolved host name a583b133831ff488b992bd981a386506-a260bd53b926b82a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:43:09Z"
    - latency: 4.827686ms
      message: 'load-balancer-api-internal: tcp connection to a583b133831ff488b992bd981a386506-a260bd53b926b82a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:42:09Z"
    - latency: 8.679329ms
      message: 'load-balancer-api-internal: resolved host name a583b133831ff488b992bd981a386506-a260bd53b926b82a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:42:09Z"
    - latency: 8.993618ms
      message: 'load-balancer-api-internal: tcp connection to a583b133831ff488b992bd981a386506-a260bd53b926b82a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:41:09Z"
    - latency: 7.563315ms
      message: 'load-balancer-api-internal: resolved host name a583b133831ff488b992bd981a386506-a260bd53b926b82a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:41:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:39:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-74-to-network-check-target-ip-10-0-128-74
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-74.ec2.internal
      uid: 4a864c02-753a-4ae3-bcb5-8561b7212160
    resourceVersion: "22851"
    uid: 98f73654-53d4-4697-b3a9-4d97d1d07d82
  spec:
    sourcePod: network-check-source-56499946bc-qgm9j
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:46:09Z"
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 830.147µs
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:46:09Z"
    - latency: 935.394µs
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:45:09Z"
    - latency: 1.293459ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:44:09Z"
    - latency: 912.962µs
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:43:09Z"
    - latency: 1.360892ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:42:09Z"
    - latency: 1.247859ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:41:09Z"
    - latency: 1.534557ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:40:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:39:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-74-to-network-check-target-ip-10-0-132-167
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-74.ec2.internal
      uid: 4a864c02-753a-4ae3-bcb5-8561b7212160
    resourceVersion: "22852"
    uid: 17706032-17b5-487e-8616-a5acb120812d
  spec:
    sourcePod: network-check-source-56499946bc-qgm9j
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:46:09Z"
      message: 'network-check-target-ip-10-0-132-167: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.376934ms
      message: 'network-check-target-ip-10-0-132-167: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:46:09Z"
    - latency: 2.099539ms
      message: 'network-check-target-ip-10-0-132-167: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:45:09Z"
    - latency: 2.387963ms
      message: 'network-check-target-ip-10-0-132-167: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:44:09Z"
    - latency: 2.468036ms
      message: 'network-check-target-ip-10-0-132-167: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:43:09Z"
    - latency: 2.348812ms
      message: 'network-check-target-ip-10-0-132-167: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:42:09Z"
    - latency: 2.260687ms
      message: 'network-check-target-ip-10-0-132-167: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:41:09Z"
    - latency: 2.617559ms
      message: 'network-check-target-ip-10-0-132-167: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:40:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:39:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-74-to-network-check-target-ip-10-0-138-21
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-74.ec2.internal
      uid: 4a864c02-753a-4ae3-bcb5-8561b7212160
    resourceVersion: "22850"
    uid: a11ed3cf-2df2-45a2-94f2-ce92b2ccd2ed
  spec:
    sourcePod: network-check-source-56499946bc-qgm9j
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:46:09Z"
      message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.42897ms
      message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:46:09Z"
    - latency: 2.285935ms
      message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:45:09Z"
    - latency: 2.259168ms
      message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:44:09Z"
    - latency: 2.133057ms
      message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:43:09Z"
    - latency: 2.319998ms
      message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:42:09Z"
    - latency: 2.445978ms
      message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:41:09Z"
    - latency: 2.371571ms
      message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:40:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:39:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-74-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-74.ec2.internal
      uid: 4a864c02-753a-4ae3-bcb5-8561b7212160
    resourceVersion: "21814"
    uid: 755f1349-3ab0-4fe9-b2ac-162f44c56c0c
  spec:
    sourcePod: network-check-source-56499946bc-qgm9j
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:45:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 719.807µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:45:09Z"
    - latency: 2.15721ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:45:09Z"
    - latency: 903.723µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:44:09Z"
    - latency: 1.649097ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:44:09Z"
    - latency: 970.218µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:43:09Z"
    - latency: 1.511151ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:43:09Z"
    - latency: 906.111µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:42:09Z"
    - latency: 1.879883ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:42:09Z"
    - latency: 880.906µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:41:09Z"
    - latency: 1.737295ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:41:09Z"
kind: List
metadata:
  resourceVersion: ""