debianmaster
Compare helm vs TPR vs Operators vs Service Catalog
@sabre1041 wrote.
helm is a package manage for kubernetes. it contains a packaging model and facilitate the deploying of kubernetes resources to the cluster through a set of charts
third party resources are user defined kubernetes API objects
TPR's are defined at a cluster level (until 1.7) and each object is scoped to a particular namespace
an operator is an intelligent process that can be used to manage complex state. IE i need to be able to manage an etcd cluster than has needs to contain a certain replaca count and manage the overall lifecycle of the cluster. operators typically make use of TPR's to define state that is managed by the operator
the service catalog is part of the open service broker API that was donated by cloudfoundry it allows for the creation of service brokers that can define which services are made available to the cluster. the broker manages the lifecycle of instances that are provided by the service. instances can be a postgresql database in a cluster. once an instance has been created, an application can bind to the instance which will create a set of resources for how applications can make use of the service. this is typically a secret. pod presets will be used to inject parameters into applications. Once complete with the service, a instance can be unbound and then deleted.
Hello @debianmaster. Could you explain advantages of Service Catalog over helm? I know that Service Catalog can provision services outside k8s cluster, but I am interested in scenario when Service Catalog provision for example DB inside k8s cluster.
My understanding of Service Catalog is very limited.
https://twitter.com/cheddarmint is leading this and is active on twitter, if you want to reach out