Google Container Registry vs. Google Kubernetes Engine

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

Google Kubernetes Engine is well suited for dynamic and large workloads since it can scale up with usage. It is easily configurable, which allows for flexibility. User interface is simple to navigate, which reduces roadblocks for a team with people unfamiliar with Kubernetes. Great if you are already using other GCP services as it integrates well with that.

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

• Deployment of a new GKE cluster is really fast in comparison to other cloud providers.
• GCP is ahead other vendors and always provide the most up to date Kubernetes version.
• GKE automation for master upgrade and the worker nodes pool works really well.

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

• Not as intuitive as it could be
• Documentation could be better, especially for people using other Google Cloud tools
• Not the preferred Kubernetes Engine for many apps

Incentivized

It's a great product if you learn it. It has flexibility and is very strong. Autoscaling and Resource management make running huge applications a breeze. Using Helm with Kubernetes and Terraform for infrastructure creation can totally automate your CICD pipeline. You also get easy access to CUDA cores for machine learning.

Incentivized

Google support is excellent and helpful, but the first answer is always so bureaucratic no matter how many logs, evidence, and information you sent.

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

We had to move several products to Google Cloud, and the Google Kubernetes Engine was the option recommended to us, so we investigated it and ran with it. Back then (2019), we were not aware of Cloud Run-provisioned K8s clusters, so our other option was a completely self-managed K8s cluster on Compute Engine VMs, which we did not have the knowledge of and capacity to handle.

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

• Compared to other big K8s providers it has the best price/performance factors.
• Upgrade process from stable to regular versions
• Old stable releases: 1.15/1.16 should be in a stable branch.

Incentivized