Senior Principal Consultant at Red Hat who guides organizations on delivering container, integration and automation solutions along with microservices architectures across various deployment targets. Authored several reference architectures including Application Release Strategies With OpenShift and emphasizes the importance of CI/CD methodologies focusing on security to develop and deploy software faster. Passion for enablement and building collaboration. Serves as a manager of the Container Community of Practice within Red Hat, which fosters awareness around the container ecosystem.
Aside from naming and versioning, managing sensitive assets, like credentials, is one of the more challenging aspects in technology. So, why is it so difficult? Well, to start off. What may be considered a sensitive asset to one individual or organization may not be the same as another. Also, given that there are so many different ways that sensitive assets can be managed, there is no universally accepted method available.
The challenges that encompass how sensitive assets are handled also apply to image mode, a new method that enables building and deploying Operating Systems using similar tools and approaches as any other traditional container. In this article, we will discuss the types of sensitive assets that apply to image mode for RHEL specifically and how to design appropriate workflows to incorporate secure practices within all phases, from build and deployment to runtime.
Image mode for RHEL extends many of the benefits of running containers and applies them to building, deploying and managing traditional Operating System environments.
While the VMDK format is open source, they are traditionally used within the VMware family of solutions, such as VMware Workstation and VMware vSphere. In this post, we will describe how the previously created VMDK disk can be used as the basis for a virtual machine hosted in a VMware vSphere environment.
Article
