apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T03:25:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-28-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-28.ec2.internal
      uid: 2a1f98a7-b25a-4cb9-bd8c-9d4248a60ea8
    resourceVersion: "15134"
    uid: b60aa839-c8ba-4920-b571-4b7ab9f3dd5c
  spec:
    sourcePod: network-check-source-685456655f-65tf2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T03:32:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 925.668µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:32:09Z"
    - latency: 994.581µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:31:09Z"
    - latency: 1.137557ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:30:09Z"
    - latency: 1.204275ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:29:09Z"
    - latency: 1.058474ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:28:09Z"
    - latency: 4.541477ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:27:09Z"
    - latency: 945.312µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:26:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T03:25:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-28-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-28.ec2.internal
      uid: 2a1f98a7-b25a-4cb9-bd8c-9d4248a60ea8
    resourceVersion: "14803"
    uid: aacb1f57-e6a8-4a5b-990f-7b2b48c9ff0f
  spec:
    sourcePod: network-check-source-685456655f-65tf2
    targetEndpoint: a6b240079babc4a8bbd6b9acf8de4610-9752a8fa3b0a0997.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T03:31:09Z"
      message: 'load-balancer-api-external: tcp connection to a6b240079babc4a8bbd6b9acf8de4610-9752a8fa3b0a0997.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.271433ms
      message: 'load-balancer-api-external: tcp connection to a6b240079babc4a8bbd6b9acf8de4610-9752a8fa3b0a0997.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:31:09Z"
    - latency: 6.459129ms
      message: 'load-balancer-api-external: resolved host name a6b240079babc4a8bbd6b9acf8de4610-9752a8fa3b0a0997.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:31:09Z"
    - latency: 4.751033ms
      message: 'load-balancer-api-external: tcp connection to a6b240079babc4a8bbd6b9acf8de4610-9752a8fa3b0a0997.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:30:09Z"
    - latency: 9.395258ms
      message: 'load-balancer-api-external: resolved host name a6b240079babc4a8bbd6b9acf8de4610-9752a8fa3b0a0997.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:30:09Z"
    - latency: 4.45009ms
      message: 'load-balancer-api-external: tcp connection to a6b240079babc4a8bbd6b9acf8de4610-9752a8fa3b0a0997.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:29:09Z"
    - latency: 6.203732ms
      message: 'load-balancer-api-external: resolved host name a6b240079babc4a8bbd6b9acf8de4610-9752a8fa3b0a0997.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:29:09Z"
    - latency: 6.294336ms
      message: 'load-balancer-api-external: tcp connection to a6b240079babc4a8bbd6b9acf8de4610-9752a8fa3b0a0997.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:28:09Z"
    - latency: 6.630681ms
      message: 'load-balancer-api-external: resolved host name a6b240079babc4a8bbd6b9acf8de4610-9752a8fa3b0a0997.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:28:09Z"
    - latency: 5.139687ms
      message: 'load-balancer-api-external: tcp connection to a6b240079babc4a8bbd6b9acf8de4610-9752a8fa3b0a0997.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:27:09Z"
    - latency: 9.590221ms
      message: 'load-balancer-api-external: resolved host name a6b240079babc4a8bbd6b9acf8de4610-9752a8fa3b0a0997.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:27:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T03:25:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-28-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-28.ec2.internal
      uid: 2a1f98a7-b25a-4cb9-bd8c-9d4248a60ea8
    resourceVersion: "14802"
    uid: e703a4c1-0795-4130-8d0d-13c71f2a1f41
  spec:
    sourcePod: network-check-source-685456655f-65tf2
    targetEndpoint: a6b240079babc4a8bbd6b9acf8de4610-9752a8fa3b0a0997.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T03:31:09Z"
      message: 'load-balancer-api-internal: tcp connection to a6b240079babc4a8bbd6b9acf8de4610-9752a8fa3b0a0997.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.308799ms
      message: 'load-balancer-api-internal: tcp connection to a6b240079babc4a8bbd6b9acf8de4610-9752a8fa3b0a0997.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:31:09Z"
    - latency: 6.376527ms
      message: 'load-balancer-api-internal: resolved host name a6b240079babc4a8bbd6b9acf8de4610-9752a8fa3b0a0997.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:31:09Z"
    - latency: 4.999391ms
      message: 'load-balancer-api-internal: tcp connection to a6b240079babc4a8bbd6b9acf8de4610-9752a8fa3b0a0997.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:30:09Z"
    - latency: 9.331273ms
      message: 'load-balancer-api-internal: resolved host name a6b240079babc4a8bbd6b9acf8de4610-9752a8fa3b0a0997.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:30:09Z"
    - latency: 4.440134ms
      message: 'load-balancer-api-internal: tcp connection to a6b240079babc4a8bbd6b9acf8de4610-9752a8fa3b0a0997.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:29:09Z"
    - latency: 6.153756ms
      message: 'load-balancer-api-internal: resolved host name a6b240079babc4a8bbd6b9acf8de4610-9752a8fa3b0a0997.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:29:09Z"
    - latency: 4.513384ms
      message: 'load-balancer-api-internal: tcp connection to a6b240079babc4a8bbd6b9acf8de4610-9752a8fa3b0a0997.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:28:09Z"
    - latency: 6.664902ms
      message: 'load-balancer-api-internal: resolved host name a6b240079babc4a8bbd6b9acf8de4610-9752a8fa3b0a0997.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:28:09Z"
    - latency: 5.153634ms
      message: 'load-balancer-api-internal: tcp connection to a6b240079babc4a8bbd6b9acf8de4610-9752a8fa3b0a0997.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:27:09Z"
    - latency: 9.614873ms
      message: 'load-balancer-api-internal: resolved host name a6b240079babc4a8bbd6b9acf8de4610-9752a8fa3b0a0997.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:27:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T03:25:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-28-to-network-check-target-ip-10-0-136-28
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-28.ec2.internal
      uid: 2a1f98a7-b25a-4cb9-bd8c-9d4248a60ea8
    resourceVersion: "15131"
    uid: 31e1c8c7-4efa-4a89-a887-ff7d5bf11981
  spec:
    sourcePod: network-check-source-685456655f-65tf2
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T03:32:09Z"
      message: 'network-check-target-ip-10-0-136-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.270303ms
      message: 'network-check-target-ip-10-0-136-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:32:09Z"
    - latency: 1.074262ms
      message: 'network-check-target-ip-10-0-136-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:31:09Z"
    - latency: 943.139µs
      message: 'network-check-target-ip-10-0-136-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:30:09Z"
    - latency: 834.962µs
      message: 'network-check-target-ip-10-0-136-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:29:09Z"
    - latency: 1.237945ms
      message: 'network-check-target-ip-10-0-136-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:28:09Z"
    - latency: 1.380652ms
      message: 'network-check-target-ip-10-0-136-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:27:09Z"
    - latency: 1.618015ms
      message: 'network-check-target-ip-10-0-136-28: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:26:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T03:25:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-28-to-network-check-target-ip-10-0-140-178
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-28.ec2.internal
      uid: 2a1f98a7-b25a-4cb9-bd8c-9d4248a60ea8
    resourceVersion: "15133"
    uid: 61684c44-fedc-4321-940f-d5eaa254f8d7
  spec:
    sourcePod: network-check-source-685456655f-65tf2
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T03:32:09Z"
      message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.541885ms
      message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:32:09Z"
    - latency: 1.83203ms
      message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:31:09Z"
    - latency: 2.20764ms
      message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:30:09Z"
    - latency: 2.232073ms
      message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:29:09Z"
    - latency: 1.840468ms
      message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:28:09Z"
    - latency: 5.794077ms
      message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:27:09Z"
    - latency: 2.058861ms
      message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:26:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T03:25:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-28-to-network-check-target-ip-10-0-143-165
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-28.ec2.internal
      uid: 2a1f98a7-b25a-4cb9-bd8c-9d4248a60ea8
    resourceVersion: "15132"
    uid: 8d90a8e6-22e8-48b8-9c5f-a85e05c49d42
  spec:
    sourcePod: network-check-source-685456655f-65tf2
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T03:32:09Z"
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.50957ms
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:32:09Z"
    - latency: 1.926893ms
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:31:09Z"
    - latency: 1.903447ms
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:30:09Z"
    - latency: 1.706486ms
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:29:09Z"
    - latency: 1.962321ms
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:28:09Z"
    - latency: 5.566848ms
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:27:09Z"
    - latency: 2.049286ms
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:26:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T03:25:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-28-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-28.ec2.internal
      uid: 2a1f98a7-b25a-4cb9-bd8c-9d4248a60ea8
    resourceVersion: "14801"
    uid: abc8ab35-4aaf-4c61-b16f-af9fb2256cb5
  spec:
    sourcePod: network-check-source-685456655f-65tf2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T03:31:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 944.98µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:31:09Z"
    - latency: 1.810411ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:31:09Z"
    - latency: 1.108097ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:30:09Z"
    - latency: 1.883447ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:30:09Z"
    - latency: 1.142072ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:29:09Z"
    - latency: 1.662265ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:29:09Z"
    - latency: 772.174µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:28:09Z"
    - latency: 1.707389ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:28:09Z"
    - latency: 1.189917ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:27:09Z"
    - latency: 4.904373ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:27:09Z"
kind: List
metadata:
  resourceVersion: ""