Organizing DAGs in different ways would provide benefits from the point of view of their management, making it possible to reflect the operating model of a system or an organization. An orchestrator could provide support to help establish relationships between DAGs; but, as far as the authors know, this requirement has not been addressed yet. Kubernetes provides a resource called Deployment that allows for defining a list of containers and accordingly parameterizing them to deploy an application. A single container, or a group of containers sharing resources, is hosted inside what Kubernetes calls a Pod, the smallest deployable computing unit in Kubernetes. Thus, a Pod represents a microservice. The developer is responsible for translating the design of the application as a collection of microservices to a list of containers in a Deployment. Therefore, although Kubernetes can manage all the microservices that comprise an application, it is not aware of their collective representation as an application. In this sense, since Kubernetes cannot handle the application itself as a first-level entity, neither can it handle the organizational structure of a set of interrelated applications and leverage it for application management. In this context, this work focuses on integrating the application concept into container orchestrators, which would enable application-aware platforms; that is, platforms with built-in intelligence that could treat applications as first-level entities, providing automated and more efficient management. Application-aware orchestration may include monitoring the status of the microservices that compose the application as well as managing their lifecycle during the deployment and execution of the application. This work contributes an application-aware Fog platform aligned with OpenFog. More precisely, the contribution of this paper is twofold: (a) proposal of a novel hierarchical application structure, which extends the typical conception of applications as DAGs, with user-defined N levels from the application management point of view (herein, the so-called \"Hierarchical Application Management Structure\", HAMS) and (b) integrating the previous proposal in Kubernetes. As a result, Kubernetes will be aware of the user-defined concepts and levels in which the application management hierarchy is structured, managing their execution as if they were native Kubernetes objects. All of this provides an OpenFog Technology Ready platform which, along with the case study presented, classifies as a Technology Readiness Level of four. The rest of the article is structured as follows. Section 2 presents a survey section that analyzes the contributions as well as limitations of the related state-of-the-art work. Section 3 presents our OpenFog-compliant system architecture and the Kubernetes extension methods for its implementation, followed by a description of the available testbed and the designed applications. Section 4 describes the platform resulting from the implementation of our proposal in Kubernetes. Section 5 discusses the usage of the platform and the deployment of the case study. Finally, Section 6 presents the conclusions and comments on future work.