The Chief I/O Posted July 28, 2020 Share Posted July 28, 2020 Kubernetes has made it more straightforward than ever to build and deploy application environments quickly via containerization. However, with that convenience comes an extra issue – how to secure all your new pods and containers. You cannot simply apply a blanket rule such as 'Deny access from external,' because sometimes, some of your applications/ pods may require this external access.It is also important to note that Kubernetes is inherently neither secure nor insecure. It is simply a platform, and that platform, just like Windows or Linux or a MySql database, is only as secure as you make it. There are, of course, flaws in every system, including Kubernetes and Docker, but in most cases, critical security issues are caused directly or indirectly by the users and their applications. View the full article Quote Link to comment Share on other sites More sharing options...
.png.6dd3056f38e93712a18d153891e8e0fc.png.1dbd1e5f05de09e66333e631e3342b83.png.933f4dc78ef5a5d2971934bd41ead8a1.png)
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.