![]() ![]() Is it simply a human issue? Or is there more to Security in Kubernetes? ![]() How did one of the biggest tech companies in Silicon Valley got hacked? It was a big headline and one that prompted the larger Kubernetes industry to focus more on security. "Within one Kubernetes pod, access credentials were exposed to Tesla's AWS environment, which contained an Amazon S3 (Amazon Simple Storage Service) bucket that had sensitive data such as telemetry." "The hackers had infiltrated Tesla's Kubernetes console, which was not password-protected," RedLock researchers wrote. They were hacked, and the end result was their system was used to run cryptocurrency mining malware. The Dashboard has cluster-admin privileges. In 2018, Tesla left their Kubernetes Dashboard open to the internet. She says that one of the reasons why you might want to do penetration testing is stories such as this. Liz Rice is on the stage discussing penetration testing in Kubernetes. It's a sunny May afternoon in a Barcelona KubeCon. You can subscribe to The Chief I/O newsletter to receive our best stories and the latest cloud native news and trends twice a week. This episode is sponsored by The Chief I/O, an online publication where you can read and share stories about cloud native, DevOps, Kubernetes, AIOps, and many other topics. We will also walk through the important patterns and security considerations in adopting GitOps. We will answer questions you may have asked about GitOps, like the advantages and disadvantages of adopting it. In this episode, we will dive deep into GitOps and its raison d'etre. If your auditors come to your office the next morning and ask if all your applications are running in your Kubernetes Cluster in a correct state now? How do you prove that? Ok, before we dig deep into any answers, let's start with another question: How do you know your systems are in a correct state now? But why? Why would you want this new way to operate? Why does this matter? GitOps gives you a mechanical, programmatic, automated way to operate. However, this was the case before GitOps. ![]() Git focuses on collaboration between developers and versioning, but it was never intended to help in operations. However, the one thing that Git did not give us is better operations. The rate of development improved with Git. It gave us the tooling for a distributed source control, continuous integration, container image distribution, and others. Git allowed us to do Cloud-native development. On a chilly November morning in 2020, it's GitOps Days, and we heard Alexis Richardson via Video Conferencing speak. #Podcast maker online sli freeVisit /faun and click on the “Create Free Account” button to get started. You can choose shared and dedicated compute instances or you can use your $100 in credit on S3-compatible object storage, Managed Kubernetes, and more. You also receive 24/7/365 human support with no tiers or hand-offs regardless of your plan size. Linode has data centers around the world with the same simple and consistent pricing regardless of location. Get started on Linode today with a $100 in free credit for listeners of the FaunCast. Whether you’re developing a personal project or managing larger workloads, you deserve simple, affordable, and accessible cloud computing solutions. Develop, deploy, and scale your modern applications faster and easier. Simplify your infrastructure and cut your cloud bills in half with Linode’s Linux virtual machines. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |