Google Container Registry vs. Kubernetes

As a Cloud Engineer while working on a migration project we used GCR and my experience of using it is actually good the reason behind this is: 1: GCR uses industry-standard encryption to protect your data.2: GCR offers data loss prevention features to help you prevent sensitive data from being leaked or exposed and last but not the least is GCR provides audit logging so you can track who has accessed your data and when, because of these reasons its my go to tool.

Incentivized

Along with all the best features and support by k8s, the automatic container scheduling to worker nodes and also self-healing containers which is what I like the most. On the other side, when I was installing the k8s cluster on CentOS 8, it was quite difficult for me, but never mind it is working as we expected and it is a one-time effort. Especially, in my case, there are more than 7 application containers required to run and communicate with each other, so for us, Kubernetes is an optimal solution.

Incentivized

• Object Immutability feature allows us to protect our code and backups from accidental or malicious changes.
• Data loss prevention feature helps us to prevent sensitive data from being leaked or exposed.
• GCR has support for machine learning which is in my opinion is best .

Incentivized

• Complex cluster management can be done with simple commands with strong authentication and authorization schemes
• Exhaustive documentation and open community smoothens the learning process
• As a user a few concepts like pod, deployment and service are sufficient to go a long way

Incentivized

• The one area which i think GCR lacks is that it currently supports a limited number of file types
• The major flaw a felt while working on it is it does not have feature of object versioning and object locking

Incentivized

• Local development, Kubernetes does tend to be a bit complicated and unnecessary in environments where all development is done locally.
• The need for add-ons, Helm is almost required when running Kubernetes. This brings a whole new tool to manage and learn before a developer can really start to use Kubernetes effectively.
• Finicy configmap schemes. Kubernetes configmaps often have environment breaking hangups. The fail safes surrounding configmaps are sadly lacking.

Incentivized

The Kubernetes is going to be highly likely renewed as the technologies that will be placed on top of it are long term as of planning. There shouldn't be any last minute changes in the adoption and I do not anticipate sudden change of the core underlying technology. It is just that the slow process of technology adoption that makes it hard to switch to something else.

It is an eminently usable platform. However, its popularity is overshadowed by its complexity. To properly leverage the capabilities and possibilities of Kubernetes as a platform, you need to have excellent understanding of your use case, even better understanding of whether you even need Kubernetes, and if yes - be ready to invest in good engineering support for the platform itself

Incentivized

It is very easy to integrate GCR with other services and I integrated GCR with GKE and Cloud Build. 1: While working on one project I created one pipeline pulls the app's Docker image from GCR and builds the app's Docker image. Deployed that apps image in GKE. 2: Ive stored the data in GCR and that data was being used by cloud Run applications

Incentivized

As I said earlier also - - K8s manage the workloads better as compared to OpenStack in terms of reliability, observability & reachability. - K8s is not limited to only a single networking or storage solution as compared to OpenStack. - Networking (which is a key concept) is much simpler in K8s as compared to OpenStack. - It is possible to upgrade your applications without downtime in K8s but in OpenStack, you either have to divert the traffic or face an outage because you have to delete the whole stack & then recreate it.

Incentivized

• As a DevOps Engineer , GCR has made a important contribution to my organisation because GCR can be used to store code and assets, which can help to reduce the development time for new projects.
• Using GCR has bee­n a cost-effective solution for us since­ we only pay for the storage we­ actually utilise. This has resulted in significant savings on our cloud storage­ expenses.
• We trust GCR be­cause they prioritise the­ security of our data by utilising industry-standard encryption. This assurance brings us pe­ace of mind, as we know our information is protecte­d.

Incentivized

• Because of microservices, Kubernetes makes it easy to find the cost of each application easily.
• Like every new technology, initially, it took more resources to educate ourselves but over a period of time, I believe it's going to be worth it.

Incentivized