bibliography.bib

@article{deshpande_survey_2020,
	title = {A {Survey} on {Internet} of {Things} ({IoT}), {Industrial} {IoT} ({IIoT}) and {Industry} 4.0},
	volume = {175},
	doi = {10.5120/ijca2020920790},
	abstract = {Internet of Things (IoT) is one of the emerging technologies comprises of ‘things’ capable of identifying, sensing, communicating, processing, and actuating the data gathered from the environment. IoT plays an important role in various sectors including healthcare, medical, education, smart cities, and also it contributes in developing smart industries as part of the industrial revolution ‘Industry 4.0’ with the use of Industrial Internet of Things (IIoT) technology. This paper provides an in-detail overview of IoT with its functioning, architecture, applications, middleware framework, protocols, and its integration with other key enabling technologies. This paper also provides an overview of the industrial revolution - industry 1.0 to 4.0 and the Industrial Internet of Things (IIoT) with its applications, architecture, and messaging protocols. Finally, paper covers research challenges in IoT and IIoT.},
	journal = {International Journal of Computer Applications},
	author = {Deshpande, Sujit and Jogdand, Rashmi},
	month = oct,
	year = {2020},
	pages = {20--27},
	file = {Full Text PDF:files/2/Deshpande und Jogdand - 2020 - A Survey on Internet of Things (IoT), Industrial I.pdf:application/pdf},
}

@article{choudhari_survey_2017,
	title = {Survey {Paper} on {Internet} of {Things}: {IoT}},
	language = {en},
	author = {Choudhari, Suraj and Rasal, Tejas and Suryawanshi, Shubham and Mane, Mayur and Yedge, Satish},
	year = {2017},
	file = {Choudhari et al. - 2017 - Survey Paper on Internet of Things IoT.pdf:files/4/Choudhari et al. - 2017 - Survey Paper on Internet of Things IoT.pdf:application/pdf},
}

@article{salih_comprehensive_2022,
	title = {A {Comprehensive} {Survey} on the {Internet} of {Things} with the {Industrial} {Marketplace}},
	volume = {22},
	copyright = {http://creativecommons.org/licenses/by/3.0/},
	issn = {1424-8220},
	url = {https://www.mdpi.com/1424-8220/22/3/730},
	doi = {10.3390/s22030730},
	abstract = {There is no doubt that new technology has become one of the crucial parts of most people’s lives around the world. By and large, in this era, the Internet and the Internet of Things (IoT) have become the most indispensable parts of our lives. Recently, IoT technologies have been regarded as the most broadly used tools among other technologies. The tools and the facilities of IoT technologies within the marketplace are part of Industry 4.0. The marketplace is too regarded as a new area that can be used with IoT technologies. One of the main purposes of this paper is to highlight using IoT technologies in Industry 4.0, and the Industrial Internet of Things (IIoT) is another feature revised. This paper focuses on the value of the IoT in the industrial domain in general; it reviews the IoT and focuses on its benefits and drawbacks, and presents some of the IoT applications, such as in transportation and healthcare. In addition, the trends and facts that are related to the IoT technologies on the marketplace are reviewed. Finally, the role of IoT in telemedicine and healthcare and the benefits of IoT technologies for COVID-19 are presented as well.},
	language = {en},
	number = {3},
	urldate = {2023-07-09},
	journal = {Sensors},
	author = {Salih, Kazhan Othman Mohammed and Rashid, Tarik A. and Radovanovic, Dalibor and Bacanin, Nebojsa},
	month = jan,
	year = {2022},
	note = {Number: 3
Publisher: Multidisciplinary Digital Publishing Institute},
	keywords = {COVID-19, IIoT, Industry 4.0, IoT, IoT applications, marketplace, telemedicine},
	pages = {730},
	file = {Full Text PDF:files/7/Salih et al. - 2022 - A Comprehensive Survey on the Internet of Things w.pdf:application/pdf},
}

@misc{ibm_betting_edge_computing,
	title = {Why organizations are betting on edge computing  {Insights} from the edge},
        author = {{IBM}},
	language = {en},
	file = {Why organizations are betting on edge computing  I.pdf:files/25/Why organizations are betting on edge computing  I.pdf:application/pdf},
        year = 2020
}

@misc{youtube_ibm_technology_what_2019,
	title = {What is edge computing?},
	url = {https://www.youtube.com/watch?v=cEOUeItHDdo},
	abstract = {Learn more about Edge Computing: https://ibm.co/2kMm7yp
Check out IBM Edge Application Manager: http://ibm.biz/ibm-edge-app-manager
Register for Edge Computing and Automation webinar: http://ibm.biz/edge-and-automation-we...

Earn a badge with FREE Kubernetes labs: http://ibm.biz/k8-labs-at-no-cost

Edge computing places workloads closer to where data is created and where actions need to be taken. It addresses the unprecedented scale and complexity of data created by connected devices. As more and more data comes in from remote IoT edge devices and servers, it’s important to act on the data quickly. Acting quickly can help companies seize new business opportunities, increase operational efficiency and improve customer experiences.

In this video, Rob High, IBM Fellow and CTO, provides insights into the basic concepts and key use cases of edge computing.

Get started for free on IBM Cloud: http://ibm.biz/ibm-cloud-free-tier
Subscribe to see more videos like this in the future → http://ibm.biz/subscribe-now

\#edgecomputing \#5g \#IBMCloud},
	urldate = {2023-07-21},
	author = {{IBM Technology}},
	month = oct,
	year = {2019},
}

@misc{atos_2021_2021,
	title = {A 2021 perspective on edge computing},
	author = {{Atos}},
	language = {en},
	year = {2021},
	file = {2021 - A 2021 perspective on edge computing.pdf:files/28/2021 - A 2021 perspective on edge computing.pdf:application/pdf},
}

@article{perez_edge_2022,
	title = {Edge computing},
	volume = {104},
	issn = {1436-5057},
	url = {https://doi.org/10.1007/s00607-022-01104-2},
	doi = {10.1007/s00607-022-01104-2},
	abstract = {IoT edge computing is a new computing paradigm “in the IoT domain” for performing calculations and processing at the edge of the network, closer to the user and the source of the data. This paradigm is relatively recent, and, together with cloud and fog computing, there may be some confusion about its meaning and implications. This paper aims to help practitioners and researchers better understand what the industry thinks about what IoT edge computing is, and the expected benefits and challenges associated with this paradigm. We conducted a survey using a semi-structured in-depth questionnaire to collect qualitative data from relevant stakeholders from 29 multinational companies and qualitatively analyzed these data using the Constructivist Grounded Theory (Charmaz) method. Several researchers participated in the coding process (collaborative coding). To ensure consensus on the constructs that support the theory and thus improve the rigor of qualitative research, we conducted an intercoder agreement analysis. From the analysis, we have derived a substantive and analytic theory of what companies perceive about IoT edge computing, its benefits and challenges. The theory is substantive in that the scope of validity refers to the 29 surveys processed and analytic in that it analyzes “what is” rather than explaining causality or attempting predictive generalizations. A public repository with all the data related to the information capture process and the products resulting from the analysis of this information is publicly available. This study aims to strengthen the evidence and support practitioners in making better informed decisions about why companies are adopting edge computing and the current challenges they face. Additionally, the testing theory phase shows that the results are aligned with the ISO/IEC TR 30164 standard.},
	language = {en},
	number = {12},
	urldate = {2023-07-21},
	journal = {Computing},
	author = {Pérez, Jorge and Díaz, Jessica and Berrocal, Javier and López-Viana, Ramón and González-Prieto, Ángel},
	month = dec,
	year = {2022},
	keywords = {IoT, 68-02, 68Qxx, Edge Computing, Grounded Theory, Inter-rater Agreement, Inter-rater Reliability},
	pages = {2711--2747},
	annote = {A grounded theory study
},
	file = {Full Text PDF:files/31/Pérez et al. - 2022 - Edge computing.pdf:application/pdf},
}

@misc{redhat_path_gitops,
	title = {The {Path} to {GitOps}},
	url = {https://developers.redhat.com/e-books/path-gitops},
	abstract = {This book outlines the tools, workflows, and structures teams need to have in place in order to enable a complete GitOps workflow for practitioners who are just},
        author = {{RedHat}},
	language = {en},
	urldate = {2023-07-21},
	journal = {Red Hat Developer},
	month = jul,
	year = {2022},
	file = {2022 - The Path to GitOps.pdf:files/37/2022 - The Path to GitOps.pdf:application/pdf;Snapshot:files/36/path-gitops.html:text/html},
}

@inproceedings{lopez-viana_continuous_2022,
	title = {Continuous {Deployment} in {IoT} {Edge} {Computing} : {A} {GitOps} implementation},
	shorttitle = {Continuous {Deployment} in {IoT} {Edge} {Computing}},
	doi = {10.23919/CISTI54924.2022.9820108},
	abstract = {Edge computing (EC) is a recent computing paradigm in the IoT domain for performing calculations and processing at the edge of the network, closer to the user instead of moving all data to the cloud. In this way, EC practitioners aim to replicate the benefits of cloud computing but closer to the source of the data, reducing the latency imposed by the distance between the cloud and the end devices, the network overhead, and the security and privacy risk that this offloading entails. But not only that. EC practitioners also aim to replicate best practices used on cloud-native development and operation. In this regard, GitOps is one of the main trends in the DevOps ecosystem for Continuous Deployment (CD) that promotes infrastructure automation in highly distributed applications, accelerating value delivery while avoiding error-prone manual processes. Till now, GitOps has been mainly related to Kubernetes—a widely used container orchestration platform to run distributed applications resiliently. In this regard, more and more IoT EC solutions are implementing container orchestration solutions like Kubernetes, thus, it is worthwhile identifying the benefits that GitOps adoption could leverage at the Edge and how possible challenges and drawbacks could be addressed. This paper presents a proof of concept based on tools included in the Cloud Native Computing Foundation (CNCF) landscape to check the feasibility of applying GtiOps in IoT EC solutions. Several drawbacks were detected mainly due to the used tooling, such as lack of automatic provisioning of physical infrastructure, tight coupled to Kubernetes descriptors for declaring workloads, and limitations on the edge devices that can be supported.},
	booktitle = {2022 17th {Iberian} {Conference} on {Information} {Systems} and {Technologies} ({CISTI})},
	author = {López-Viana, Ramón and Díaz, Jessica and Pérez, Jorge E.},
	month = jun,
	year = {2022},
	note = {ISSN: 2166-0727},
	keywords = {IoT, Automation, Cloud computing, Containers, DevOps, Ecosystems, GitOps, Image edge detection, IoT Edge Computing, Pipelines, Runtime environment},
	pages = {1--6},
	file = {IEEE Xplore Full Text PDF:files/39/López-Viana et al. - 2022 - Continuous Deployment in IoT Edge Computing  A Gi.pdf:application/pdf},
}

@misc{telekom_gitops_k8s_scale,
	title = {Deutsche {Telekom} uses {Weave} {GitOps} to deliver edge {Kubernetes} at scale},
	url = {https://www.weave.works/blog/kubernetes-and-gitops-support-deutsche-telekom-5g},
        author = {{WeaveWorks}},
	abstract = {Deutsche Telekom, the first global Telco running Kubernetes across both its core and edge sites to deliver multiple use cases through a single, telco-grade platform, the company’s collaboration with Weaveworks marks a milestone in the mobile industry. Dubbed Liquid Metal, it is a fully open, GitOps-enabled, distributed Kubernetes Cluster-as-a-Service (CaaS) platform, operating at massive scale.},
	language = {en},
	urldate = {2023-07-27},
	file = {Snapshot:files/41/kubernetes-and-gitops-support-deutsche-telekom-5g.html:text/html},
        year = 2021
}

@misc{weaveworks_gitops_edge_all_clouds,
	title = {{GitOps} across the {Edge} and all {Clouds}},
	url = {https://www.weave.worksurl!},
	abstract = {In this two-part series we discuss why Kubernetes is vital for telcos to set up operations at the edge, and how GitOps is key to managing and scaling Kubernetes at the edge. Together, they make for a comprehensive strategy for telcos looking to rollout 5G services in the near future.},
	language = {en},
	urldate = {2023-07-27},
	file = {Snapshot:files/43/gitops-across-the-edge-and-all-clouds.html:text/html},
        year = 2021,
        author = {{WeaveWorks}}
}

@misc{alamoush_adapting_2022,
	title = {Adapting {Kubernetes} to {IIoT} and {Industry} 4.0 protocols - {An} initial performance analysis},
	copyright = {Creative Commons Attribution 4.0 International, Open Access},
	url = {https://zenodo.org/record/7158281},
	doi = {10.5281/ZENODO.7158281},
	abstract = {Kubernetes (K8s) is one of the most frequently used container orchestration tools offering, as it offers a rich set of functions to manage containerized applications, it is customizable and extensible. Container virtualization of applications and their orchestration on heterogeneous resources including edge devices is a recent trend in Industrial Internet of Things (IIoT)/Industry 4.0, where K8s is also applied. However, IIoT/Industry 4.0 is a domain with high standardization requirements. Besides equipment standards, e.g., for electrical control cabinets, there are also demands to standardize network protocols, data formats or information models. Such standards can foster interoperability and reduce complexity or deployment/integration costs. Here, the proprietary communication protocol of K8s and similar orchestrators can be an obstacle for adoption.},
	language = {en},
	urldate = {2023-07-29},
	author = {Alamoush, Ahmad and Eichelberger, Holger},
	month = oct,
	note = {Publisher: Zenodo},
	file = {Alamoush und Eichelberger - 2022 - Adapting Kubernetes to IIoT and Industry 4.0 proto.pdf:files/44/Alamoush und Eichelberger - 2022 - Adapting Kubernetes to IIoT and Industry 4.0 proto.pdf:application/pdf},
        year = 2022
}

@misc{simpkins_opportunities_2022,
	title = {Opportunities and {Challenges} in {Edge} {Computing} {Under} {Kubernetes}},
	url = {https://training.linuxfoundation.org/blog/opportunities-and-challenges-in-edge-computing-under-kubernetes/},
	abstract = {By Bob Reselman Today edge computing is commonplace on the technology landscape. It seems as if it’s everywhere, from point of sale systems to red-light cameras at traffic stops, even...},
	language = {en-US},
	urldate = {2023-07-29},
	journal = {Linux Foundation - Training},
	author = {Simpkins, Mary},
	month = mar,
	year = {2022},
	file = {Snapshot:files/47/opportunities-and-challenges-in-edge-computing-under-kubernetes.html:text/html},
}

@article{cilic_performance_2023,
	title = {Performance {Evaluation} of {Container} {Orchestration} {Tools} in {Edge} {Computing} {Environments}},
	volume = {23},
	copyright = {http://creativecommons.org/licenses/by/3.0/},
	issn = {1424-8220},
	url = {https://www.mdpi.com/1424-8220/23/8/4008},
	doi = {10.3390/s23084008},
	abstract = {Edge computing is a viable approach to improve service delivery and performance parameters by extending the cloud with resources placed closer to a given service environment. Numerous research papers in the literature have already identified the key benefits of this architectural approach. However, most results are based on simulations performed in closed network environments. This paper aims to analyze the existing implementations of processing environments containing edge resources, taking into account the targeted quality of service (QoS) parameters and the utilized orchestration platforms. Based on this analysis, the most popular edge orchestration platforms are evaluated in terms of their workflow that allows the inclusion of remote devices in the processing environment and their ability to adapt the logic of the scheduling algorithms to improve the targeted QoS attributes. The experimental results compare the performance of the platforms and show the current state of their readiness for edge computing in real network and execution environments. These findings suggest that Kubernetes and its distributions have the potential to provide effective scheduling across the resources on the network’s edge. However, some challenges still have to be addressed to completely adapt these tools for such a dynamic and distributed execution environment as edge computing implies.},
	language = {en},
	number = {8},
	urldate = {2023-07-31},
	journal = {Sensors},
	author = {Čilić, Ivan and Krivić, Petar and Podnar Žarko, Ivana and Kušek, Mario},
	month = jan,
	year = {2023},
	note = {Number: 8
Publisher: Multidisciplinary Digital Publishing Institute},
	keywords = {container, edge computing, Internet of Things (IoT), ioFog, K3s, KubeEdge, Kubernetes, service orchestration, service scheduling},
	pages = {4008},
	file = {Full Text PDF:files/49/Čilić et al. - 2023 - Performance Evaluation of Container Orchestration .pdf:application/pdf},
}

@misc{google_container_optimized,
	title = {Container-{Optimized} {OS} {Overview}},
	url = {https://cloud.google.com/container-optimized-os/docs/concepts/features-and-benefits},
        author = {{Google}},
	language = {en},
	urldate = {2023-07-31},
	journal = {Google Cloud},
	file = {Snapshot:files/51/features-and-benefits.html:text/html},
        year = 2023
}

@misc{umh_automation_pyramid,
	title = {2.1 {Automation} pyramid},
	url = {https://learn.umh.app/lesson/introduction-into-it-ot-automation-pyramid/},
	abstract = {One of the central frameworks in the world of OT, is the automation pyramid, international standards ISA-95 or IEC62264. This framework will be briefly explained in this section.},
        author = {{United Manufacturing Hub}},
	language = {en},
	urldate = {2023-08-03},
	journal = {United Manufacturing Learning Hub},
	month = feb,
	year = {2023},
	file = {Snapshot:files/53/introduction-into-it-ot-automation-pyramid.html:text/html},
}

@article{martinez_automation_2021,
	title = {Automation {Pyramid} as {Constructor} for a {Complete} {Digital} {Twin}, {Case} {Study}: {A} {Didactic} {Manufacturing} {System}},
	volume = {21},
	issn = {1424-8220},
	shorttitle = {Automation {Pyramid} as {Constructor} for a {Complete} {Digital} {Twin}, {Case} {Study}},
	url = {https://www.mdpi.com/1424-8220/21/14/4656},
	doi = {10.3390/s21144656},
	abstract = {Nowadays, the concept of Industry 4.0 aims to improve factories’ competitiveness. Usually, manufacturing production is guided by standards to segment and distribute its processes and implementations. However, industry 4.0 requires innovative proposals for disruptive technologies that engage the entire production process in factories, not just a partial improvement. One of these disruptive technologies is the Digital Twin (DT). This advanced virtual model runs in real-time and can predict, detect, and classify normal and abnormal operating conditions in factory processes. The Automation Pyramid (AP) is a conceptual element that enables the efficient distribution and connection of different actuators in enterprises, from the shop floor to the decision-making levels. When a DT is deployed into a manufacturing system, generally, the DT focuses on the low-level that is named field level, which includes the physical devices such as controllers, sensors, and so on. Thus, the partial automation based on the DT is accomplished, and the information between all manufacturing stages could be decremented. Hence, to achieve a complete improvement of the manufacturing system, all the automation pyramid levels must be included in the DT concept. An artificial intelligent management system could create an interconnection between them that can manage the information. As a result, this paper proposed a complete DT structure covering all automation pyramid stages using Artificial Intelligence (AI) to model each stage of the AP based on the Digital Twin concept. This work proposes a virtual model for each level of the traditional AP and the interactions among them to flow and control information efficiently. Therefore, the proposed model is a valuable tool in improving all levels of an industrial process. In addition, It is presented a case study where the DT concept for modular workstations underpins the development of technologies within the framework of the Automation Pyramid model is implemented into a didactic manufacturing system.},
	language = {en},
	number = {14},
	urldate = {2023-08-05},
	journal = {Sensors},
	author = {Martinez, Edwin Mauricio and Ponce, Pedro and Macias, Israel and Molina, Arturo},
	month = jul,
	year = {2021},
	pages = {4656},
	file = {Martinez et al. - 2021 - Automation Pyramid as Constructor for a Complete D.pdf:files/54/Martinez et al. - 2021 - Automation Pyramid as Constructor for a Complete D.pdf:application/pdf},
}

@misc{manditereza_key_nodate,
	title = {The {Key} {Differences} {Between} {OPC} {UA} {And} {MQTT} {Sparkplug}},
	url = {https://www.hivemq.com/article/iiot-protocols-opcua-vs-mqtt-sparkplug-digital-transformation/},
	abstract = {OPC UA vs. MQTT Sparkplug: Which IIoT protocol helps with digital transformation and connects industrial data sources of all kinds, bringing OT/IT interoperability.},
	language = {en},
	urldate = {2023-08-07},
	author = {Manditereza, Kudzai and HiveMQ},
	file = {Snapshot:files/57/iiot-protocols-opcua-vs-mqtt-sparkplug-digital-transformation.html:text/html},
        year = 2022
}

@misc{hivemq_opcua_vs_mqtt_sparkplug,
	title = {A {Comparison} of {OPC} {UA} and {MQTT} {Sparkplug}},
	url = {https://www.hivemq.com/iiot-protocols-opc-ua-mqtt-sparkplug-comparison/},
	abstract = {IIoT protocol comparison: OPC UA is a common communication protocol for production environments. MQTT is extremely lightweight and easy to implement. Sparkplug is an open standard that adopts characteristics of MQTT.},
	language = {en},
	urldate = {2023-08-14},
	author = {{HiveMQ}},
	file = {Snapshot:files/59/iiot-protocols-opc-ua-mqtt-sparkplug-comparison.html:text/html},
        year = 2021
}

@misc{koschnick_industrie_nodate,
	title = {Industrie 4.0: {Das} {Referenzarchitekturmodell} {Industrie} 4.0 ({RAMI} 4.0)},
	url = {https://www.zvei.org/fileadmin/user_upload/Presse_und_Medien/Publikationen/2015/april/Das_Referenzarchitekturmodell_Industrie_4.0__RAMI_4.0_/Faktenblatt-Industrie4_0-RAMI-4_0.pdf},
	abstract = {RAMI 4.0 führt erstmals die wesentlichen Elemente von Industrie 4.0 in einem dreidimensionalen Schichtenmodell zusammen. Anhand dieses Gerüsts kann Industrie-4.0-Technologie
systematisch eingeordnet und weiterentwickelt werden.},
	language = {de},
	author = {Koschnick, Gunther and Hankel, Martin and Rexroth, Bosch},
	file = {Koschnick et al. - RAMI 4.0 führt erstmals die wesentlichen Elemente .pdf:files/64/Koschnick et al. - RAMI 4.0 führt erstmals die wesentlichen Elemente .pdf:application/pdf},
        year = 2015         
}

@misc{iiot_consort_iira,
	title = {The {Industrial} {Internet} {Reference} {Architecture}},
	url = {https://www.iiconsortium.org/iira/},
	abstract = {The Industrial Internet Reference Architecture v 1.9 IIRA FAQ IIRA Insights: Mapping to the IIRA: First Insights Applying the IIRA: […]},
	language = {en-US},
	urldate = {2023-08-18},
	journal = {Industry IoT Consortium},
	file = {Snapshot:files/67/iira.html:text/html},
        author = {{Industry IIoT Consortium}}
}

@misc{azure_iiot_overview,
	title = {Azure {Industrial} {IoT} {Overview}},
	url = {https://learn.microsoft.com/en-us/azure/industrial-iot/overview-what-is-industrial-iot},
	abstract = {This article provides an overview of Industrial IoT. It explains the shop floor connectivity and security components in IIoT.},
	language = {en-us},
	urldate = {2023-08-22},
	author = {{Microsoft}},
	month = nov,
	year = {2022},
	file = {Snapshot:files/69/overview-what-is-industrial-iot.html:text/html},
}

@misc{microsoft_industrial_connectivity,
	title = {Industrial {IoT} connectivity patterns - {Azure} {Architecture} {Center}},
	url = {https://learn.microsoft.com/en-us/azure/architecture/guide/iiot-patterns/iiot-connectivity-patterns},
	abstract = {Learn about several common connectivity patterns to build, deploy, and manage Industrial IoT (IIoT) solutions.},
	language = {en-us},
	urldate = {2023-08-22},
	author = {{Microsoft}},
	file = {Snapshot:files/75/iiot-connectivity-patterns.html:text/html},
        year = 2023
}

@misc{iot_edge_docs,
	title = {Azure {IoT} {Edge} documentation},
	url = {https://learn.microsoft.com/en-us/azure/iot-edge/?view=iotedge-1.4},
	abstract = {Azure IoT Edge extends IoT Hub. Analyze device data locally instead of in the cloud to send less data to the cloud, react to events quickly, and operate offline.},
	language = {en-us},
	urldate = {2023-08-24},
	author = {{Microsoft}},
	file = {Snapshot:files/79/iot-edge.html:text/html},
        year = 2022
}

@misc{microsoft_azure_iot_reference,
	title = {Microsoft {Azure} {IoT} {Reference} {Architecture}},
	url = {https://download.microsoft.com/download/A/4/D/A4DAD253-BC21-41D3-B9D9-87D2AE6F0719/Microsoft_Azure_IoT_Reference_Architecture.pdf},
        author = {{Microsoft Azure}},
	abstract = {The purpose of the document is to provide an overview of the recommended architecture and implementation technology choices for how to build Azure IoT solutions. This architecture describes terminology, technology principles, common configuration environments, and composition of Azure IoT serv...},
	language = {en},
	urldate = {2023-08-24},
	file = {Snapshot:files/81/microsoft-azure-iot-reference-architecture.html:text/html},
        year = 2018
}

@misc{greengrass_vs_iot_edge,
	title = {{AWS} {IoT} {Greengrass} vs {Azure} {IoT} {Edge}},
	url = {https://blog.machex.com.sg/2021/06/18/iot-edge-computing-aws-iot-greengrass-vs-azure-iot-edge/},
	abstract = {Introduction Over the years, edge computing for Internet of Things (IoT) systems has become more prevalent due to reasons such as low latency, better control over security, cost savings, and greater reliability. Many companies in the industry has came up with services and tools to help organizations to effectively and reliably implement edge computing. As […]},
	language = {en-US},
	urldate = {2023-08-25},
        author = {{MaChecks}},
	month = jun,
	year = {2021},
	file = {Snapshot:files/84/iot-edge-computing-aws-iot-greengrass-vs-azure-iot-edge.html:text/html},
}

@misc{google_iot_core_eol,
	title = {End of {Google} {IoT} core's life – looking for alternatives?},
	url = {https://www.btelligent.com/en/blog/end-of-google-iot-core-life-are-you-looking-for-alternatives/},
	abstract = {Many Google cloud users are now asking themselves: What are my alternatives and how do I integrate them into my existent architecture?},
	language = {en},
	urldate = {2023-08-25},
	journal = {b.telligent},
	file = {Snapshot:files/86/end-of-google-iot-core-life-are-you-looking-for-alternatives.html:text/html},
        author = {{b.telligent}},
        year = 2022
}

@misc{reference_architecture_in_general,
	title = {Reference {Architecture} - {The} {Definitive} {Guide} {\textbar} {LeanIX}},
	url = {https://www.leanix.net/en/wiki/ea/reference-architecture},
	abstract = {Learn everything you need to know about reference architecture, including benefits, examples, and 5 drivers for Reference Architecture.},
	language = {en},
	urldate = {2023-08-31},
	author = {{LeanIX GmbH}},
	file = {Snapshot:files/88/reference-architecture.html:text/html},
        year = 2023
}

@misc{geiger_zones_2018,
	title = {Zones \& {Conduits}: {Das} {Schutzkonzept} aus der {IEC} 62443 einfach erklärt},
	shorttitle = {Zones \& {Conduits}},
	url = {https://www.sichere-industrie.de/zones-conduits/},
	abstract = {Zonen und sichere Zonenübergänge als wirksames Schutzkonzept der IEC 62443, das auch die stabile Basis Ihrer Zukunftsprojekte ist.},
	language = {de-DE},
	urldate = {2023-08-31},
	journal = {Sichere Industrie},
	author = {Geiger, Marcus},
	month = mar,
	year = {2018},
	file = {Snapshot:files/92/zones-conduits.html:text/html},
}

@misc{hivemq_essentials_uns,
	title = {{HiveMQ}: {Unified} {Namespace} ({UNS}) {Essentials}},
	url = {https://www.hivemq.com/unified-namespace-uns-essentials-iiot-industry-40/},
	abstract = {Get a quick introduction to Unified Namespace (UNS), what it is, and why does it matter to Industrial IoT (IIoT) and Industry 4.0 projects.},
	language = {en},
	urldate = {2023-09-01},
	author = {Manditereza, Kudzai},
	file = {Snapshot:files/96/unified-namespace-uns-essentials-iiot-industry-40.html:text/html},
        year = 2023
}

@misc{noauthor_mqtt_nodate,
	title = {{MQTT} {Specification}},
	url = {https://mqtt.org/mqtt-specification/},
	urldate = {2023-09-05},
	file = {MQTT Specification:files/100/mqtt-specification.html:text/html},
}

@misc{wolnisty_when_nodate,
	title = {When to use {OPC}-{UA} vs {OPC}-{DA}},
	url = {https://www.vertech.com/blog/opc-ua-vs-opc-da},
	abstract = {OPC DA. OPC UA. COM. DCOM. All the terms get confusing! We'll cover a brief history of OPC and explain how OPC DA and OPC UA compare.},
	language = {en-us},
	urldate = {2023-09-05},
	author = {Wolnisty, John},
	file = {Snapshot:files/102/opc-ua-vs-opc-da.html:text/html},
}

@misc{smart_manufacturing_using_isa95_mqtt,
	title = {Smart {Manufacturing} {Using} {ISA95}, {MQTT} {Sparkplug} and the {Unified} {Namespace}},
	url = {https://www.hivemq.com/solutions/manufacturing/smart-manufacturing-using-isa95-mqtt-sparkplug-and-uns/},
	abstract = {How an MQTT Broker can be used in smart manufacturing as a centralised server for coordinating the exchange of ISA95 models using Sparkplug and Unified Namespace.},
	language = {en},
	urldate = {2023-09-05},
	author = {Manditereza, Kudzai},
	file = {Snapshot:files/104/smart-manufacturing-using-isa95-mqtt-sparkplug-and-uns.html:text/html},
        year = 2021
}

@misc{does_mqtt_uns_solve,
	title = {Does {MQTT} {Unified} {Namespace} solve all your data integration issues? - {TQS}},
	shorttitle = {Does {MQTT} {Unified} {Namespace} solve all your data integration issues?},
	url = {https://tqsintegration.com/does-mqtt-unified-namespace-solve-all-your-data-integration-issues/},
	abstract = {It seems many companies think that Message Queuing Telemetry Transport (short MQTT) can solve all their data integration issues. And there has been a lot of industry chats about this topic. But can it},
	language = {en-US},
	urldate = {2023-09-05},
	journal = {TQS Integration},
	author = {Amort, Holger},
	month = may,
	year = {2021},
	note = {Section: Integration},
	file = {Snapshot:files/106/does-mqtt-unified-namespace-solve-all-your-data-integration-issues.html:text/html},
}

@misc{noauthor_distributed_nodate,
	title = {Distributed {Systems} {Observability} [{Book}]},
	url = {https://www.oreilly.com/library/view/distributed-systems-observability/9781492033431/},
	abstract = {Network infrastructure is in the midst of a paradigm shift. As systems become more distributed, methods for building and operating them are rapidly evolving—and that makes visibility into your services … - Selection from Distributed Systems Observability [Book]},
	language = {en},
	urldate = {2023-09-08},
	note = {ISBN: 9781492033424},
	file = {Snapshot:files/108/9781492033431.html:text/html},
}

@misc{owasp_top_ten,
	title = {{OWASP} {Top} {Ten} {\textbar} {OWASP} {Foundation}},
	url = {https://owasp.org/www-project-top-ten/},
	abstract = {The OWASP Top 10 is the reference standard for the most critical web application security risks. Adopting the OWASP Top 10 is perhaps the most effective first step towards changing your software development culture focused on producing secure code.},
	language = {en},
	urldate = {2023-09-08},
	file = {Snapshot:files/110/www-project-top-ten.html:text/html},
        year = 2023
}

@misc{building_future_on_metal,
	title = {Building the {Future} on {Bare} {Metal}},
	url = {https://www.openstack.org/use-cases/bare-metal/how-ironic-delivers-abstraction-and-automation-using-open-source-infrastructure/},
	abstract = {How Ironic Delivers Abstraction and Automation using Open Source Infrastructure},
	language = {de\_DE},
	urldate = {2023-09-19},
	journal = {OpenStack},
        author = {{OpenStack}},
	file = {Snapshot:files/116/how-ironic-delivers-abstraction-and-automation-using-open-source-infrastructure.html:text/html},
}

@misc{vs_anforderungsprofil,
	title = {{VS}-{Anforderungsprofil} {Hypervisor} für {Server} - {Supporting} {Document}},
	language = {en},
	file = {VS-Anforderungsprofil Hypervisor für Server - Supp.pdf:files/118/VS-Anforderungsprofil Hypervisor für Server - Supp.pdf:application/pdf},
        author = {{Bundesamt für Sicherheit in der Informationstechnik}},
        year = 2020,
        url = {https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Zulassung/VS-Anforderungsprofile/BSI-VS-AP-0019_SupportDok.pdf?__blob=publicationFile&v=3}
}

@misc{baremetal_vs_hypervisor,
	title = {Bare {Metal} vs {Hypervisor}: {Which} {Is} {Right} {For} {Your} {Project}?},
	shorttitle = {Bare {Metal} vs {Hypervisor}},
	url = {https://blog.servermania.com/bare-metal-vs-hypervisor-which-is-right-for-your-project},
	abstract = {Bare metal vs hypervisor is a fundamental infrastructure hosting distinction that every CEO and CIO should understand.},
	language = {en},
	urldate = {2023-09-22},
	file = {Snapshot:files/121/bare-metal-vs-hypervisor-which-is-right-for-your-project.html:text/html},
        author = {Milad Karimyar},
        year = 2023
}

@misc{gardener_capi,
	title = {{GitHub}: gardener/docs/concepts/cluster-api.md at master · gardener/gardener},
	url = {https://github.com/gardener/gardener/blob/master/docs/concepts/cluster-api.md},
	abstract = {Kubernetes-native system managing the full lifecycle of conformant Kubernetes clusters as a service on Alicloud, AWS, Azure, GCP, OpenStack, vSphere, KubeVirt, Hetzner, EquinixMetal, MetalStack, an...},
	language = {en},
	urldate = {2023-09-22},
	journal = {GitHub},
	file = {Snapshot:files/123/cluster-api.html:text/html},
        year = 2023,
        author = {Gardener}
}

@misc{efficient_k8s_capi,
	title = {{Efficient} {Kubernetes} {Cluster} {Management}: {Building} {Infrastructure}-{Agnostic} {Clusters} with {Cluster} {API}},
	url = {https://www.suse.com/c/rancher_blog/kubernetes-cluster-management-building-infrastructure-agnostic-clusters-with-cluster-api/},
	urldate = {2023-09-22},
	file = {Efficient kubernetes cluster management with CAPI | SUSE Communities:files/125/kubernetes-cluster-management-building-infrastructure-agnostic-clusters-with-cluster-api.html:text/html},
        year = 2023
}

@misc{metal3_introduction,
	title = {Introduction - {Metal}³ user-guide},
	url = {https://book.metal3.io/introduction},
	urldate = {2023-09-22},
	file = {Introduction - Metal³ user-guide:files/129/introduction.html:text/html},
}


@misc{baudoin_industrial_nodate,
	title = {The {Industrial} {Internet} of {Things} {Vocabulary}},
	language = {en},
	author = {Baudoin, Claude and Bournival, Erin and Guerrero, Ruben},
	file = {Baudoin et al. - The Industrial Internet of Things Vocabulary.pdf:files/130/Baudoin et al. - The Industrial Internet of Things Vocabulary.pdf:application/pdf},
        year = 2010
}


@misc{opc_foundation_interop,
	title = {OPC Unified Architecture - Interoperability for Industrie 4.0 and the Internet of Things},
	url = {https://opcfoundation.org/wp-content/uploads/2023/05/OPC-UA-Interoperability-For-Industrie4-and-IoT-EN.pdf},
	language = {en},
	urldate = {2023-08-07},
	author = {{OPC Foundation}},
	file = {Snapshot:files/57/iiot-protocols-opcua-vs-mqtt-sparkplug-digital-transformation.html:text/html},
        year = 2023
}

@misc{mqtt_topics_best_practices,
	title = {{MQTT} {Topics}, {Wildcards}, \& {Best} {Practices} – {MQTT} {Essentials}: {Part} 5},
	shorttitle = {{MQTT} {Topics}, {Wildcards}, \& {Best} {Practices} – {MQTT} {Essentials}},
	url = {https://www.hivemq.com/blog/mqtt-essentials-part-5-mqtt-topics-best-practices/},
	abstract = {Learn about MQTT Topics, naming conventions, MQTT \$SYS topics, MQTT Prefix, MQTT Topic Wildcards, and more in this MQTT Essentials article.},
	language = {en},
	urldate = {2023-11-14},
	author = {Team, HiveMQ},
	file = {Snapshot:files/134/mqtt-essentials-part-5-mqtt-topics-best-practices.html:text/html},
        year = 2019
}


@misc{rami_img_source,
	title = {{RAMI} 4.0: {Ein} {Referenzarchitekturmodell} als {Kommunikationsgrundlage} in der {Industrie} 4.0},
	shorttitle = {{RAMI} 4.0},
	url = {https://www.dke.de/rami40},
	abstract = {RAMI 4.0 ist eine dreidimensionale Landkarte und beschreibt eine strukturierte Herangehensweise an das Thema Industrie 4.0},
	language = {de},
	urldate = {2023-11-16},
        author = {{DKE - VDE Verband der Elektrotechnik Elektronik Informationstechnik e.V.}},
	file = {Snapshot:files/136/rami40.html:text/html},
        year = 2022
}

@misc{building_iiot,
	title = {{MaibornWolff GmbH: Building IIoT 2023: "One size fits all"-Architektur für Industrial-IoT-Plattformen}},
	language = {de},
        author = {Wöhrl, Sebastian and Jäckle, Marc},
        year = 2023
}


@misc{rinke_was_2022,
	title = {Was ist {OPC} {UA}? {Die} wichtigsten {Begriffe} im Überblick},
	shorttitle = {Was ist {OPC} {UA}?},
	url = {https://www.opc-router.de/was-ist-opc-ua/},
	abstract = {OPC steht für Open Platform Communications und ist eines der wichtigsten Kommunikationsprotokolle für Industrie 4.0 und das IoT.},
	language = {de-DE},
	urldate = {2023-11-29},
	journal = {Systemintegration mit dem OPC Router},
	author = {Rinke, Alexandra},
	month = apr,
	year = {2022},
	file = {Snapshot:files/140/was-ist-opc-ua.html:text/html},
}


@misc{sematext_structured_logging,
	title = {What {Is} {Structured} {Logging} and {Why} {You} {Should} {Use} {It}},
	url = {https://sematext.com/glossary/structured-logging/},
	abstract = {Find out what structured logging is and why developers need it. Examples of structured logs and top tools that help leverage them for faster troubleshooting.},
	language = {en-US},
	urldate = {2023-12-01},
	journal = {Sematext},
	file = {Snapshot:files/142/structured-logging.html:text/html},
        author = {{Sematext}},
        year = 2023
}


@misc{need_for_observability,
	title = {{The} {Need} for {Observability} - {Distributed} {Systems} {Observability} [{Book}]},
	url = {https://www.oreilly.com/library/view/distributed-systems-observability/9781492033431/ch01.html},
	abstract = {The Need for Observability Infrastructure software is in the midst of a paradigm shift. Containers, orchestrators, microservices architectures, service meshes, immutable infrastructure, and functions-as-a-service (also known as “serverless”) … - Selection from Distributed Systems Observability [Book]},
	language = {en},
	urldate = {2023-12-01},
	note = {ISBN: 9781492033424},
	file = {Snapshot:files/144/ch01.html:text/html},
        author = {Cindy Sridharan},
        year = 2018
}


@misc{rancher_platform,
	title = {Rancher - {Enterprise Kubernetes Management}},
	url = {http://www.rancher.com},
	abstract = {Rancher, the open-source multi-cluster orchestration platform, lets operations teams deploy, manage and secure enterprise Kubernetes. Request a demo!},
	language = {en-US},
	urldate = {2023-12-03},
	journal = {Rancher Labs},
	file = {Snapshot:files/147/www.rancher.com.html:text/html},
        author = {{Rancher Labs}},
        year = 2023
}


@misc{mercedes_kubecon_700,
	title = {{Mercedes}-{Benz}: {How} to {Migrate} 700 {Kubernetes} {Clusters} to {ClusterAPI} with zero downtime},
        author = {Giese, Tobias AND Schneeweiss, Sean},
	shorttitle = {{KubeCon} + {CloudNativeCon} {Europe} 2022},
	url = {https://kccnceu2022.sched.com/event/yttp/how-to-migrate-700-kubernetes-clusters-to-cluster-api-with-zero-downtime-tobias-giese-sean-schneeweiss-mercedes-benz-tech-innovation},
	abstract = {Cluster API promises "to simplify provisioning, upgrading, and operating multiple Kubernetes clusters." Do you find it challenging to migrate your existing Kubernetes cluster provisioning to Cluster API? Would you like to benefit from all the features that Cluster API offers and manage your infrastructure the Kubernetes style? At Mercedes-Benz, we run and operate more than 700 Kubernetes clusters and 3,500 machines all over the world in on-premises OpenStack data centers. By migrating to Cluster API, we replaced our legacy provisioning, consisting of Terraform, custom self-written tools and Kubernetes operators. Expect valuable insights on what it takes to transfer production systems into the control of Cluster API with zero downtime and zero customer impact. Get to know the technical challenges of migrating, how they can be solved and how to extend Cluster API functionality to fit your needs.
},
	urldate = {2023-12-04},
	file = {Snapshot:files/151/how-to-migrate-700-kubernetes-clusters-to-cluster-api-with-zero-downtime-tobias-giese-sean-schn.html:text/html},
        year = 2022
}


@misc{spectrocloud_2022,
	title = {{CNCF} {On}-{Demand} {Webinar}: {Cluster} {API} and {GitOps}: the key to {Kubernetes} lifecycle management},
	shorttitle = {{CNCF} {On}-{Demand} {Webinar}},
	url = {https://www.cncf.io/online-programs/cncf-on-demand-webinar-cluster-api-and-gitops-the-key-to-kubernetes-lifecycle-management/},
	abstract = {There are many different ways you can bootstrap Kubernetes clusters, with various degrees of complexity. Modern Kubernetes installers automate manual tasks but generally, the more they abstract away…},
	language = {en-US},
	urldate = {2023-12-07},
	journal = {CNCF},
	month = apr,
	year = {2023},
	file = {Snapshot:files/153/cncf-on-demand-webinar-cluster-api-and-gitops-the-key-to-kubernetes-lifecycle-management.html:text/html},
        author = {{spectro cloud}}
}


@misc{capi_github,
	title = {{GitHub}: Cluster {API}},
	copyright = {Apache-2.0},
	url = {https://github.com/kubernetes-sigs/cluster-api},
	abstract = {Home for Cluster API, a subproject of sig-cluster-lifecycle},
	urldate = {2023-12-07},
	publisher = {Kubernetes SIGs},
        author = {Kubernetes SIGs},
	month = dec,
	keywords = {k8s-sig-cluster-lifecycle},
        year = 2023
}


@misc{k8s_operator_pattern,
	title = {{Kubernetes} {Documentation}: {Operator} pattern},
	url = {https://kubernetes.io/docs/concepts/extend-kubernetes/operator/},
	abstract = {Operators are software extensions to Kubernetes that make use of custom resources to manage applications and their components. Operators follow Kubernetes principles, notably the control loop.
Motivation The operator pattern aims to capture the key aim of a human operator who is managing a service or set of services. Human operators who look after specific applications and services have deep knowledge of how the system ought to behave, how to deploy it, and how to react if there are problems.},
	language = {en},
	urldate = {2023-12-07},
	journal = {Kubernetes},
	file = {Snapshot:files/156/operator.html:text/html},
        author = {{Kubernetes SIGs}},
        year = 2023
}


@misc{the_cluster_api_book,
	title = {Concepts - {The} {Cluster} {API} {Book}},
	url = {https://cluster-api.sigs.k8s.io/user/concepts},
	urldate = {2023-12-07},
	file = {Concepts - The Cluster API Book:files/158/concepts.html:text/html},
        author = {{Kubernetes SIGs}},
        year = 2023
}


@misc{cattle_not_pets,
	title = {{DevOps}: {What} {Does} {Cattle} {Not} {Pets} {Mean}?},
	shorttitle = {{DevOps}},
	url = {https://geektechstuff.com/2021/06/24/devops-what-does-cattle-not-pets-mean/},
	abstract = {In a DevOps sense, “cattle not pets” means creating services and / or infrastructure that can be maintained, destroyed and re-deployed with little human interaction. Why Cattle Not Pets…},
	language = {en},
	urldate = {2023-12-07},
	journal = {GeekTechStuff},
	author = {Geek\_Dude},
	month = jun,
	year = {2021},
	file = {Snapshot:files/160/devops-what-does-cattle-not-pets-mean.html:text/html},
}


@misc{was_ist_ipmi_datacenter,
	title = {Datacenter Insider: Was ist {IPMI}?},
	url = {https://www.datacenter-insider.de/was-ist-ipmi-a-b4d4dc0cb9eaa7bee59cf59da6646266/},
	abstract = {(Bild: gemeinfrei Pixabay) IPMI (Infrastructure Platform Management Interface) macht für den Administrator aus jedem Server ein offenes Buch – auch, wenn er ausgeschaltet oder ohne Betriebssystem ist. Außerdem kann der Admin seine Aufgaben aus der Ferne erledigen.},
	language = {de},
	urldate = {2023-12-11},
	journal = {DataCenter-Insider},
	author = {Rüdiger, Ariane},
	month = may,
	year = {2022},
	file = {Snapshot:files/165/was-ist-ipmi-a-b4d4dc0cb9eaa7bee59cf59da6646266.html:text/html},
}

@misc{dont_use_dhcp_options,
	title = {You want to {PXE} {Boot}? {Don}'t use {DHCP} {Options}.},
	shorttitle = {You want to {PXE} {Boot}?},
	url = {https://techcommunity.microsoft.com/t5/Configuration-Manager-Blog/You-want-to-PXE-Boot-Don-t-use-DHCP-Options/ba-p/275562},
	abstract = {You want to PXE Boot? Don't use DHCP Options.},
	language = {en},
	urldate = {2023-12-11},
	journal = {TECHCOMMUNITY.MICROSOFT.COM},
	file = {Snapshot:files/167/275562.html:text/html},
}

@misc{sidero_labs_docs,
	title = {Kubernetes on {Bare} {Metal}: {An} {Introduction} to {Sidero}},
	shorttitle = {Kubernetes on {Bare} {Metal}},
	url = {https://www.siderolabs.com/blog/kubernetes-on-bare-metal-sidero/},
	abstract = {Talos is awesome. An OS for Kubernetes thats completely API-driven and tailor-made just for running Kubernetes? I’ve wanted that long before I actually started working on it with the team. I want to run it everywhere. But the desire to run it everywhere is precisely where things get interesting. In the spirit of the OS […]},
	language = {en-US},
	urldate = {2023-12-11},
	journal = {Sidero Labs},
	author = {Smith, Spencer},
	month = oct,
	year = {2020},
	file = {Snapshot:files/168/kubernetes-on-bare-metal-sidero.html:text/html},
}

@misc{paragon_software_pc_deployment,
	title = {{PC Deployment} over {Network} using {PXE} {environment}},
	url = {https://download.paragon-software.com/doc/PCDeployment.pdf},
	language = {en},
	urldate = {2023-12-11},
	author = {{PARAGON Software}},
        year = 2005
}

@misc{pxe_ipmi_redfish_httpboot,
	title = {Firmware in the datacenter: Goodbye {PXE} and {IPMI}. Welcome {HTTP Boot} and {Redfish}!},
	url ={https://uefi.org/sites/default/files/resources/UEFI_Plugfest_May_2015_HTTP_Boot_Redfish_Samer_El-Haj_ver1.2.pdf},
	language = {en},
	urldate = {2023-12-12},
	author = {{Samer El-Haj-Mahmoud} Hewlett Packard},
        year = 2015
}


@misc{was_ist_bmc,
	title = {Datacenter Insider: Was ist ein {Baseboard} {Management} {Controller}?},
	url = {https://www.datacenter-insider.de/was-ist-ein-baseboard-management-controller-a-1101914/},
	abstract = {Ein moderner Server ist komplex. Um seinen Zustand stets aktuell überwachen und steuern zu können, ist ein Baseboard Management Controller (BMC) erforderlich.},
	language = {de},
	urldate = {2023-12-11},
	journal = {DataCenter-Insider},
	author = {Ostler, Ulrike and Hensel, Martin},
	month = mar,
	year = {2022},
	file = {Snapshot:files/171/was-ist-ein-baseboard-management-controller-a-1101914.html:text/html},
}


@misc{rancher_uses_clusterapi,
	title = {Launching {Kubernetes} with {Rancher} {\textbar} {Rancher}},
	url = {https://ranchermanager.docs.rancher.com/pages-for-subheaders/launch-kubernetes-with-rancher},
	abstract = {You can have Rancher launch a Kubernetes cluster using any nodes you want. When Rancher deploys Kubernetes onto these nodes, you can choose between Rancher Kubernetes Engine (RKE) or RKE2 distributions. Rancher can launch Kubernetes on any computers, including:},
	language = {en},
	urldate = {2023-12-12},
	month = aug,
	year = {2023},
	file = {Snapshot:files/174/launch-kubernetes-with-rancher.html:text/html},
        author = {Rancher Labs}
}

@misc{azure_capi_provider,
	title = {The {Cluster} {API} {Provider} {Azure} {Book}},
	url = {https://capz.sigs.k8s.io/topics/managedcluster.html},
	abstract = {Cluster API Provider Azure (CAPZ) supports managing Azure Kubernetes Service (AKS) clusters},
	language = {en},
	urldate = {2023-12-15},
        publisher = {Kubernetes SIGs},
        author = {Kubernetes SIGs},
	year = {2023}
}


@misc{canonical_maas,
	title = {Metal as a {Service}},
	url = {https://maas.io/},
	abstract = {MAAS (Metal as a Service) offers cloud style provisioning for physical servers. It is open source and free to use, with commercial support available from Canonical.},
	language = {en},
	urldate = {2023-12-16},
	journal = {MAAS},
	file = {Snapshot:files/176/maas.io.html:text/html},
	author = {{Canonical}},
        year = 2023
}

@misc{metal3_docs,
	title = {Metal {Kubed}},
	url = {https://metal3.io/},
	abstract = {Metal3.io aims to build on baremetal host provisioning technologies to provide a Kubernetes native API for managing bare metal hosts via a provisioning stack that is also running on Kubernetes.},
	language = {en},
	urldate = {2023-12-16},
	journal = {Metal³ - Metal Kubed},
	author = {Metal³-Metal Kubed website team},
	year = 2023,
	file = {Snapshot:files/179/metal3.io.html:text/html},
}

@misc{metal3_bare_metal_operator,
	title = {Baremetal {Operator} - {Metal}³ user-guide},
	url = {https://book.metal3.io/bmo/introduction.html#bare-metal-operator},
	urldate = {2023-12-16},
	file = {Baremetal Operator - Metal³ user-guide:files/180/introduction.html:text/html},
        year = 2023,
	author = {Metal³-Metal Kubed website team}
}

@misc{tinkerbell,
	title = {Flexible automation for bare metal},
	url = {https://tinkerbell.org/},
	abstract = {Designed for scalable provisioning of physical hardware, Tinkerbell is both open-source and cloud native. Contributed to the CNCF by Equinix Metal.},
	language = {en},
	urldate = {2023-12-16},
	journal = {Tinkerbell.org},
	author = {Community, Tinkerbell},
	file = {Snapshot:files/182/tinkerbell.org.html:text/html},
        year = 2021
}

@misc{siderometal,
	title = {Sidero {Metal}},
	url = {https://www.sidero.dev/},
	language = {en},
	urldate = {2023-12-16},
	file = {Snapshot:files/184/www.sidero.dev.html:text/html},
	author = {{Sidero Labs}},
	year = 2023
}

@misc{taloslinux,
	title = {Talos {Linux}},
	url = {https://www.talos.dev/},
	language = {en},
	urldate = {2023-12-16},
	file = {Snapshot:files/186/www.talos.dev.html:text/html},
	author = {{Sidero Labs}},
	year = 2023
}


@misc{sealedsecrets,
	title = {{GitHub}: bitnami-labs/sealed-secrets},
	copyright = {Apache-2.0},
	url = {https://github.com/bitnami-labs/sealed-secrets},
	abstract = {A Kubernetes controller and tool for one-way encrypted Secrets},
	urldate = {2023-12-18},
	publisher = {Bitnami Labs},
	month = dec,
	keywords = {devops-workflow, encrypt-secrets, gitops, kubernetes, kubernetes-secrets},
        author = {{Bitnami Labs}},
        year = 2023
}

@misc{externalsecretsoperator,
	title = {Introduction - {External} {Secrets} {Operator}},
	url = {https://external-secrets.io/latest/},
	urldate = {2023-12-18},
	file = {Introduction - External Secrets Operator:files/190/latest.html:text/html},
        year = 2023
}

@misc{mozillasops,
	title = {{GitHub}: getsops/sops},
	copyright = {MPL-2.0},
	url = {https://github.com/getsops/sops},
	abstract = {Simple and flexible tool for managing secrets},
	urldate = {2023-12-18},
	publisher = {SOPS: Secrets OPerationS},
	month = dec,
	year = {2023},
	keywords = {aws, azure, devops, gcp, pgp, secret-distribution, secret-management, security, sops},
        author = {{Mozilla}}
}

@misc{secrets-csi-driver,
	title = {{GitHub}: kubernetes-sigs/secrets-store-csi-driver},
	copyright = {Apache-2.0},
	url = {https://github.com/kubernetes-sigs/secrets-store-csi-driver},
	abstract = {Secrets Store CSI driver for Kubernetes secrets - Integrates secrets stores with Kubernetes via a CSI volume.},
	urldate = {2023-12-18},
	publisher = {Kubernetes SIGs},
	month = dec,
	year = {2023},
	keywords = {aws-secrets-manager, azure-keyvault, csi, csi-secrets-store, gcp-secret-manager, hashicorp-vault, k8s-sig-auth, kubernetes, mount-multiple-secrets},
}


@misc{telekom_dasschiff,
	title = {{GitHub}: das-schiff/{README}.md at main · telekom/das-schiff},
	url = {https://github.com/telekom/das-schiff/blob/main/README.md},
	abstract = {This is home of Das Schiff - Deutsche Telekom Technik's engine for Kubernetes Cluster as a Service (CaaS) in on-premise environment on top of bare-metal servers and VMs.  - telekom/das-schiff},
	language = {en},
	urldate = {2023-12-18},
	journal = {GitHub},
	author = {{Telekom}},
	file = {Snapshot:files/193/README.html:text/html},
        year = 2022
}

@misc{victoriametrics,
	title = {Open {Source} {Time} {Series} {Monitoring} {Tools} \& {Solutions}},
	url = {https://victoriametrics.com/products/open-source/},
	abstract = {Fast \& easy open source time series database \& monitoring solution optimized for high cardinality. Highly scalable on cloud, kubernetes or on-premise setups},
	language = {en},
	urldate = {2023-12-18},
	file = {Snapshot:files/195/open-source.html:text/html},
	author = {{VictoriaMetrics}},
        year = 2023
}

@misc{hivemq_operator,
	title = {{HiveMQ} {Kubernetes} {Operator} :: {HiveMQ} {Documentation}},
	url = {https://docs.hivemq.com/hivemq-operator/index.html},
	urldate = {2023-12-18},
	file = {HiveMQ Kubernetes Operator \:\: HiveMQ Documentation:files/197/index.html:text/html},
	author = {{HiveMQ}},
        year = 2023
}


@misc{hivemq_edge_website,
	title = {{HiveMQ} {Edge}: {Open}-source {IIoT} gateway \& protocol converter to {MQTT}},
	shorttitle = {{HiveMQ} {Edge}},
	url = {https://www.hivemq.com/products/hivemq-edge/},
	abstract = {Convert OT protocols like Modbus \& OPC-UA into MQTT with open-source IIoT gateway for easy integration with enterprise \& cloud systems. Learn more.},
	language = {en},
	urldate = {2023-12-18},
	file = {Snapshot:files/199/hivemq-edge.html:text/html},
	author = {{HiveMQ}},
        year = 2023
}


@misc{fraunhofer_whitepaper,
	title = {Whitepaper: {Industrial} {Internet} of {Things}: {Referenzarchitektur} für die {Kommunikation}},
	shorttitle = {Whitepaper},
	url = {https://www.iks.fraunhofer.de/de/publikationen/whitepaper-studien/whitepaper-internet-of-things.html},
	abstract = {Whitepaper »Industrial Internet of Things: Referenzarchitektur für die Kommunikation«: Jetzt downloaden},
	language = {de},
	urldate = {2024-01-02},
	journal = {Fraunhofer-Institut für Kognitive Systeme IKS},
	file = {Snapshot:files/204/whitepaper-internet-of-things.html:text/html},
        author = {{Fraunhofer} {IKS}},
        year = 2016
}