Google Container Registry vs. IBM Cloud Kubernetes Service

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

IBM Cloud Kubernetes Service also stands out in environments where the workloads vary continuously and require befitting scale. The product excels particularly in microservices structures, wherein the companies would harness the capacity for container orchestration and automated scaling. Still, it may face the challenges due to monolith applications that have not been originally developed for using container technology.

• 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

• IBM has a strong focus on serverless and Kubernetes. This shows in the platform. Deploying containers to Kubernetes was very easy.
• Deploying a Kubernetes cluster through the GUI is very easy and quick. On top of that, IBM Cloud offers a single node cluster for Free.
• Container Registry is a very good product for managing container images. Integration with Kubernetes was seemless.
• Portability. To transition from Google Cloud Kubernetes to IBM Cloud Kubernetes took almost no effort. We mostly use the CLI and the standard tools such as kubectl were present.

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

• I constantly get this error even when everything is well configured prefect.exceptions.AuthorizationError: [{'path': ['auth_info'], 'message': 'AuthenticationError: Forbidden', 'extensions': {'code': 'UNAUTHENTICATED'}}]
• Then sometimes the error disapear without changine anything, happened twice to me. Should there be an issue with the authentication service? Please let's improve or let users know why this may be happening.
• Improve the UX in the browse console when removing many images at once
• UX on the process of installing KeyCloack operator

Incentivized

We have our application running on a CentOS compartment on IBM Cloud Kubernetes Service. We have been utilizing the help since IBM Cloud initially dispatched. We liked the adaptability and versatility that IBM Cloud Kubernetes Service give us. Since we are tiny, the Kubernetes administration is just utilized at present inside my venture bunch.

Incentivized

We actually haven't had any real problems in our clusters recently and the results we have gotten from adopting IBM Cloud Kubernetes Service have been beyond even our greatest expectations. The community has helped optimize the use of the system and make it relatively simpler to use.

Incentivized

IBM's cloud is almost infallible.

Incentivized

IBM's cloud has a site in my conuntry (MEXICO) so the network latency was almost 0

Incentivized

The self-guided support was solid, and there are plenty of online videos to guide first time users, but I think one area of improvement is a faster way to transfer a large quantity of files from our local machine to the cloud for storage (Aspera)

Incentivized

Online training is really an important resource for using these tools. IBM's help center is rich in useful information and tips. Also, external guides and tutorials are available (e.g. on youtube), but I followed only IBM ones and I had no difficulties.

Incentivized

Ease of use. Very intuitive. We have been looking for a product that allows us to orchestrate our docker containers in a way where it allows us to effectively scale our applications to production. It also provides us a way of monitoring all our infrastructure in a very clear concise way.

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 mainly selected [IBM Cloud Kubernetes Service] because IBM fabric blockchain service is mostly compatible with it. To have all the infrastructure in a single cloud to get the best output we selected the [IBM Cloud Kubernetes Service].

Incentivized

IBM's CKS does not offers automatic autoscaling nor vertical scaling (automatic). Other services like Google Kubernetes Engine scales up and down very well

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

• Increased development speed and agility allows to build features faster and more economically.
• Improved resource utilization helps keep applications running very efficiently, which saves on cloud service expenses.
• Scalability and resilience allows for scaling up or down based on demand, which keeps applications running efficiently and more economically.

Incentivized