Description
Everyone is talking about the microservices and serverless architecture, and how to deploy them using cluster managers like Kubernetes. But, what about the secrets? The current trend increases the number of secrets required to run our services. This places a new level of maintenance on our security teams. How can we share and manage the secrets (certificates, passwords, SSH, API keys) for our services in this kind of dynamic scenario; where instances are started automatically, where there are multiple instances of the same services for scalability reasons? Are you keeping up?
Come to this session to see how you can manage your secrets with Vault in Kubernetes; why Kubernetes secrets might be not enough. Start making security a first-class citizen in the development process.
Provide a small paragraph that describes your proposal
Kubernetes secrets might be not enough, you need to encrypt secrets as well, in this direction Kubernetes implemented an Encrypting Secret Data at Rest feature that allows you to encrypt secrets on transit. Let's explore how to encrypt secrets, why using a key management system (KMS) is a must, and how Vault can help you in keeping your secrets secret.
Speaker Bio (optional)
Alex is a Director of Developer Experience at Red Hat. He is passionate about Java world, software automation and he believes in the open-source software model.
Alex is the creator of NoSQLUnit project, a member of JSR374 (Java API for JSON Processing) Expert Group, the co-author of Testing Java Microservices and Quarkus cookbook books and contributor of several open-source projects. A Java Champion since 2017, international speaker and teacher at Salle URL University, he has talked about new testing techniques for microservices and continuous delivery in the 21st century.
A short bio of the speaker
Alex is a Director of Developer Experience at Red Hat. He is passionate about Java world, software automation and he believes in the open-source software model.
Description Everyone is talking about the microservices and serverless architecture, and how to deploy them using cluster managers like Kubernetes. But, what about the secrets? The current trend increases the number of secrets required to run our services. This places a new level of maintenance on our security teams. How can we share and manage the secrets (certificates, passwords, SSH, API keys) for our services in this kind of dynamic scenario; where instances are started automatically, where there are multiple instances of the same services for scalability reasons? Are you keeping up?
Come to this session to see how you can manage your secrets with Vault in Kubernetes; why Kubernetes secrets might be not enough. Start making security a first-class citizen in the development process.
Provide a small paragraph that describes your proposal
Kubernetes secrets might be not enough, you need to encrypt secrets as well, in this direction Kubernetes implemented an Encrypting Secret Data at Rest feature that allows you to encrypt secrets on transit. Let's explore how to encrypt secrets, why using a key management system (KMS) is a must, and how Vault can help you in keeping your secrets secret.
Speaker Bio (optional)
Alex is a Director of Developer Experience at Red Hat. He is passionate about Java world, software automation and he believes in the open-source software model.
Alex is the creator of NoSQLUnit project, a member of JSR374 (Java API for JSON Processing) Expert Group, the co-author of Testing Java Microservices and Quarkus cookbook books and contributor of several open-source projects. A Java Champion since 2017, international speaker and teacher at Salle URL University, he has talked about new testing techniques for microservices and continuous delivery in the 21st century.
A short bio of the speaker
Alex is a Director of Developer Experience at Red Hat. He is passionate about Java world, software automation and he believes in the open-source software model.