Enterprise software systems rely on accurate configuration data to support their normal operation. Configurations take many forms and can be set up in a variety of ways, depending on the use case and context. These configurable properties could include details to support the application framework or the normal operation of the program.
While many of these properties are intended to be viewed by any party, there are certain attributes, such as passwords, that should only be seen or accessed by certain individuals or components. These sensitive forms of data are called Secrets, and protecting these Secrets is a top priority for Kubernetes administrators and developers. As one might expect with any complex system, Kubernetes configurations employ a myriad of properties to support normal operation, some which may contain sensitive information that, if exposed, would risk the integrity of the entire platform.