The fields after this are specific to the scaleService driver For the scaleService driver, the only two actions are up(increase the number of containers) and down(decrease the number of containers). (Only Scale a Service is available for 1.4)Īction: This field lets you specify the action specific to the driver.
#Webook blog drivers#
Kind: The Kind dropdown gives a list of all drivers available in webhook-service. Name: Every receiver hook should be given a unique name so it can be easily identifed. On this page, the fields to be entered are as follows You will see all these fields to be entered. This is where all the receiver hooks you create for the selected environment will be listed under Receiver HooksĬlick on Add Receiver. I will go through the steps of creating the receiver hooks. A classic use case for this is integration with a monitoring system that watches load balancer traffic and calls this receiver hook when response times or requests per second reach a certain threshold. The driver scaleService allows users to create a receiver hook that can scale a service up or down. I will explain the feature using our current driver, scaleService. We have implemented webhooks with our new microservice, called webhook-service. This action is selected while adding the receiver hook. A receiver hook in Rancher registers a webhook and provides a URL, which when hit can trigger an action within Rancher. A key concept for implementing webhooks is 'Receiver'. Rancher has added a new feature in 1.4 for webhooks.