apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:30:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-129-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-129.ec2.internal
      uid: dd1075a9-fe82-47e6-ba70-ab6771edfb3d
    resourceVersion: "22235"
    uid: 90273d82-661a-4a8f-93b6-f8ba5cce79b1
  spec:
    sourcePod: network-check-source-56499946bc-v98d7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:37:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.124847ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:37:40Z"
    - latency: 1.129789ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:36:40Z"
    - latency: 1.236232ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:35:40Z"
    - latency: 1.133838ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:34:40Z"
    - latency: 1.123648ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:33:40Z"
    - latency: 986.349µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:32:40Z"
    - latency: 1.293232ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:31:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:30:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-129-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-129.ec2.internal
      uid: dd1075a9-fe82-47e6-ba70-ab6771edfb3d
    resourceVersion: "21359"
    uid: 4e175761-f238-4bfd-9290-c3172fbda833
  spec:
    sourcePod: network-check-source-56499946bc-v98d7
    targetEndpoint: a517aff71f74d467391f7b420fecb6a2-669fa764dd4ac33a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:36:40Z"
      message: 'load-balancer-api-external: tcp connection to a517aff71f74d467391f7b420fecb6a2-669fa764dd4ac33a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.106868ms
      message: 'load-balancer-api-external: tcp connection to a517aff71f74d467391f7b420fecb6a2-669fa764dd4ac33a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:36:40Z"
    - latency: 7.391498ms
      message: 'load-balancer-api-external: resolved host name a517aff71f74d467391f7b420fecb6a2-669fa764dd4ac33a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:36:40Z"
    - latency: 4.67981ms
      message: 'load-balancer-api-external: tcp connection to a517aff71f74d467391f7b420fecb6a2-669fa764dd4ac33a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:35:40Z"
    - latency: 10.067641ms
      message: 'load-balancer-api-external: resolved host name a517aff71f74d467391f7b420fecb6a2-669fa764dd4ac33a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:35:40Z"
    - latency: 4.910814ms
      message: 'load-balancer-api-external: tcp connection to a517aff71f74d467391f7b420fecb6a2-669fa764dd4ac33a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:34:40Z"
    - latency: 6.845274ms
      message: 'load-balancer-api-external: resolved host name a517aff71f74d467391f7b420fecb6a2-669fa764dd4ac33a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:34:40Z"
    - latency: 5.044878ms
      message: 'load-balancer-api-external: tcp connection to a517aff71f74d467391f7b420fecb6a2-669fa764dd4ac33a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:33:40Z"
    - latency: 7.101853ms
      message: 'load-balancer-api-external: resolved host name a517aff71f74d467391f7b420fecb6a2-669fa764dd4ac33a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:33:40Z"
    - latency: 5.994003ms
      message: 'load-balancer-api-external: tcp connection to a517aff71f74d467391f7b420fecb6a2-669fa764dd4ac33a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:32:40Z"
    - latency: 9.218736ms
      message: 'load-balancer-api-external: resolved host name a517aff71f74d467391f7b420fecb6a2-669fa764dd4ac33a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:32:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:30:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-129-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-129.ec2.internal
      uid: dd1075a9-fe82-47e6-ba70-ab6771edfb3d
    resourceVersion: "21358"
    uid: 84ce75c9-8cca-43e1-9e50-95bde66727e9
  spec:
    sourcePod: network-check-source-56499946bc-v98d7
    targetEndpoint: a517aff71f74d467391f7b420fecb6a2-669fa764dd4ac33a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:36:40Z"
      message: 'load-balancer-api-internal: tcp connection to a517aff71f74d467391f7b420fecb6a2-669fa764dd4ac33a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.109104ms
      message: 'load-balancer-api-internal: tcp connection to a517aff71f74d467391f7b420fecb6a2-669fa764dd4ac33a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:36:40Z"
    - latency: 7.416422ms
      message: 'load-balancer-api-internal: resolved host name a517aff71f74d467391f7b420fecb6a2-669fa764dd4ac33a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:36:40Z"
    - latency: 6.744685ms
      message: 'load-balancer-api-internal: tcp connection to a517aff71f74d467391f7b420fecb6a2-669fa764dd4ac33a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:35:40Z"
    - latency: 10.004264ms
      message: 'load-balancer-api-internal: resolved host name a517aff71f74d467391f7b420fecb6a2-669fa764dd4ac33a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:35:40Z"
    - latency: 4.068057ms
      message: 'load-balancer-api-internal: tcp connection to a517aff71f74d467391f7b420fecb6a2-669fa764dd4ac33a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:34:40Z"
    - latency: 6.757902ms
      message: 'load-balancer-api-internal: resolved host name a517aff71f74d467391f7b420fecb6a2-669fa764dd4ac33a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:34:40Z"
    - latency: 4.572969ms
      message: 'load-balancer-api-internal: tcp connection to a517aff71f74d467391f7b420fecb6a2-669fa764dd4ac33a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:33:40Z"
    - latency: 6.99152ms
      message: 'load-balancer-api-internal: resolved host name a517aff71f74d467391f7b420fecb6a2-669fa764dd4ac33a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:33:40Z"
    - latency: 4.535104ms
      message: 'load-balancer-api-internal: tcp connection to a517aff71f74d467391f7b420fecb6a2-669fa764dd4ac33a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:32:40Z"
    - latency: 9.301917ms
      message: 'load-balancer-api-internal: resolved host name a517aff71f74d467391f7b420fecb6a2-669fa764dd4ac33a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:32:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:30:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-129-to-network-check-target-ip-10-0-129-25
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-129.ec2.internal
      uid: dd1075a9-fe82-47e6-ba70-ab6771edfb3d
    resourceVersion: "22233"
    uid: 8a236d5f-20b6-4340-8826-d1e235224abc
  spec:
    sourcePod: network-check-source-56499946bc-v98d7
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:37:40Z"
      message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.881515ms
      message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:37:40Z"
    - latency: 2.185816ms
      message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:36:40Z"
    - latency: 2.189775ms
      message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:35:40Z"
    - latency: 2.15782ms
      message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:34:40Z"
    - latency: 2.072737ms
      message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:33:40Z"
    - latency: 2.311611ms
      message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:32:40Z"
    - latency: 2.47149ms
      message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:31:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:30:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-129-to-network-check-target-ip-10-0-140-200
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-129.ec2.internal
      uid: dd1075a9-fe82-47e6-ba70-ab6771edfb3d
    resourceVersion: "22232"
    uid: 577677f8-7819-4e0f-968f-b598267c2d9b
  spec:
    sourcePod: network-check-source-56499946bc-v98d7
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:37:40Z"
      message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.868577ms
      message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:37:40Z"
    - latency: 2.515171ms
      message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:36:40Z"
    - latency: 1.879031ms
      message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:35:40Z"
    - latency: 1.915457ms
      message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:34:40Z"
    - latency: 1.883329ms
      message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:33:40Z"
    - latency: 2.181633ms
      message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:32:40Z"
    - latency: 1.937496ms
      message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:31:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:30:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-129-to-network-check-target-ip-10-0-143-129
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-129.ec2.internal
      uid: dd1075a9-fe82-47e6-ba70-ab6771edfb3d
    resourceVersion: "22234"
    uid: b4d3b0bf-697e-457a-bf81-7ed1aa3ef782
  spec:
    sourcePod: network-check-source-56499946bc-v98d7
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:37:40Z"
      message: 'network-check-target-ip-10-0-143-129: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 808.866µs
      message: 'network-check-target-ip-10-0-143-129: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:37:40Z"
    - latency: 946.379µs
      message: 'network-check-target-ip-10-0-143-129: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:36:40Z"
    - latency: 960.383µs
      message: 'network-check-target-ip-10-0-143-129: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:35:40Z"
    - latency: 894.8µs
      message: 'network-check-target-ip-10-0-143-129: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:34:40Z"
    - latency: 822.021µs
      message: 'network-check-target-ip-10-0-143-129: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:33:40Z"
    - latency: 840.071µs
      message: 'network-check-target-ip-10-0-143-129: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:32:40Z"
    - latency: 1.970966ms
      message: 'network-check-target-ip-10-0-143-129: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:31:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:30:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-129-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-129.ec2.internal
      uid: dd1075a9-fe82-47e6-ba70-ab6771edfb3d
    resourceVersion: "21357"
    uid: 319be436-4ebb-4abf-b1b9-2ce25fe1c53a
  spec:
    sourcePod: network-check-source-56499946bc-v98d7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:36:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 808.694µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:36:40Z"
    - latency: 2.079467ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:36:40Z"
    - latency: 862.593µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:35:40Z"
    - latency: 1.732314ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:35:40Z"
    - latency: 1.026363ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:34:40Z"
    - latency: 1.877045ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:34:40Z"
    - latency: 832.011µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:33:40Z"
    - latency: 1.69717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:33:40Z"
    - latency: 889.526µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:32:40Z"
    - latency: 1.906959ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:32:40Z"
kind: List
metadata:
  resourceVersion: ""