IBM Cloud Kubernetes Service is a
managed Kubernetes offering, delivering user tools and built-in security for rapid delivery of applications
that users can bind to cloud services related to IBM Watson®, IoT, DevOps
and data analytics. As a certified K8s provider, IBM Cloud Kubernetes
Service provides intelligent scheduling, self-healing, horizontal
scaling, service discovery and load balancing, automated rollouts and
rollbacks, and secret and configuration management. The Kubernetes…
N/A
Perforce Puppet
Score 8.9 out of 10
N/A
Puppet Enteprise is an IT automation and configuration management solution that enables users to manage and automate infrastructure and complex workflows. The vendor states Puppet Enterprise combines both model‑based and task-based capabilities in a way that enables organizations to scale their multi-cloud infrastructure as their automation footprint grows, with more flexibility from both agent-based and agentless capabilities.
N/A
Pricing
IBM Cloud Kubernetes Service
Perforce Puppet
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
IBM Cloud Kubernetes Service
Perforce Puppet
Free Trial
No
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
IBM Cloud Kubernetes Service
Perforce Puppet
Features
IBM Cloud Kubernetes Service
Perforce Puppet
Container Management
Comparison of Container Management features of Product A and Product B
IBM Cloud Kubernetes Service is ideal for deploying modern applications on a microservices architecture -- where easy scaling and ability to update are important. IBM Cloud Kubernetes Service also handles automated deployments and load balancing very well, particularly if you're already working in the IBM Cloud ecosystem. There are applications less suited to IBM Cloud Kubernetes Service -- such as very small applications, where managing an IBM Cloud Kubernetes Service cluster would be overkill. Also, users not familiar with container organization might find IBM Cloud Kubernetes Service to be a challenge to manage effectively.
Most of the major issues that people had with the language have been addressed in Puppet 4 which primarily pertain to the limitations of the language and its ability to scale. It would be nice to allow for full ruby support as an unsupported option though so developers are able to reference their own data sources dynamically.
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.
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
The complexity can get a little overwhelming in a more collaborative deployment methodology across multiple platforms and data centers.
Some external changes to Puppet like the new Puppet 4 architecture can cause considerable time consuming migration efforts especially if you have a lot of legacy classes and configuration that do not conform readily to the new design.
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.
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.
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)
Puppet has top class support. You can simply mail them with their query and they will respond to your query in a timely manner. We do have enterprise license for puppet. Also there is a vibrant community for puppet out there. So even if you dont purchase a premium support option you can simply google your queries and get answers
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.
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.
I have earlier used various services, such as Kubernetes and Google Cloud Run. Still, IBM Cloud Kubernetes Service offers more convenience and a larger set of functions and features are available in Kubernetes. Google Cloud Run is much closer to a server less approach to deployment, although it gives slightly less flexibility in terms of configuration than IBM Cloud Kubernetes Service.
Puppet was selected before I joined the team, had it been my choice I would have much rather went with Chef as it has the ability to do things that Puppet has not yet added to their system such a the ability to quickly query what host currently are allowing puppet to maintain their files or the ability to run remote commands without having to include it in a manifest like Chef does with the knife command. Salt allows you to do similar things to the knife command that is included with Chef, and also allows you to transfer files quickly to multiple host at once with a short simple command.
IBM's CKS does not offers automatic autoscaling nor vertical scaling (automatic). Other services like Google Kubernetes Engine scales up and down very well
IKS can provide around 30% savings when it comes to operational costs since Kubernetes is designed to run applications in most machines in the most efficient manner possible.
Managed Kubernetes can save a company time by 45% since Managed Kubernetes usually is seamlessly updated, without any interruptions with the workload. IKS fall into this benefit.
We heard people had saved in maintenance downtimes when it comes to Kubernetes by a factor of 10 so IKS can contribute to more flexible and distributed services with virtually no downtime.
With all the DevOps and automation that we have going on, we save a ton of time on the configuration of the server. It's safe to say that configuring servers via console or via UI is a thing of the past.
We try to get all the things done by using a centralized repo (GitHub). Puppet is one tool that actually gets the actual work done.
The small amount that we spent on purchasing premium Puppet is completely justified because of the time and effort that this tool actually helps us save.
