{
	"connector": {
		"class": "org.apache.camel.kafkaconnector.kuberneteshpa.CamelKuberneteshpaSinkConnector",
		"artifactId": "camel-kubernetes-hpa-kafka-connector",
		"groupId": "org.apache.camel.kafkaconnector",
		"id": "camel-kubernetes-hpa-sink",
		"type": "sink",
		"version": "0.12.0-SNAPSHOT",
		"description": "Perform operations on Kubernetes Horizontal Pod Autoscalers (HPA) and get notified on HPA changes."
	},
	"properties": {
		"camel.sink.path.masterUrl": {
			"name": "camel.sink.path.masterUrl",
			"description": "Kubernetes Master url",
			"priority": "HIGH",
			"required": "true"
		},
		"camel.sink.endpoint.apiVersion": {
			"name": "camel.sink.endpoint.apiVersion",
			"description": "The Kubernetes API Version to use",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.dnsDomain": {
			"name": "camel.sink.endpoint.dnsDomain",
			"description": "The dns domain, used for ServiceCall EIP",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.kubernetesClient": {
			"name": "camel.sink.endpoint.kubernetesClient",
			"description": "Default KubernetesClient to use if provided",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.portName": {
			"name": "camel.sink.endpoint.portName",
			"description": "The port name, used for ServiceCall EIP",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.portProtocol": {
			"name": "camel.sink.endpoint.portProtocol",
			"description": "The port protocol, used for ServiceCall EIP",
			"defaultValue": "\"tcp\"",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.lazyStartProducer": {
			"name": "camel.sink.endpoint.lazyStartProducer",
			"description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing.",
			"defaultValue": "false",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.operation": {
			"name": "camel.sink.endpoint.operation",
			"description": "Producer operation to do on Kubernetes",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.connectionTimeout": {
			"name": "camel.sink.endpoint.connectionTimeout",
			"description": "Connection timeout in milliseconds to use when making requests to the Kubernetes API server.",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.caCertData": {
			"name": "camel.sink.endpoint.caCertData",
			"description": "The CA Cert Data",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.caCertFile": {
			"name": "camel.sink.endpoint.caCertFile",
			"description": "The CA Cert File",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.clientCertData": {
			"name": "camel.sink.endpoint.clientCertData",
			"description": "The Client Cert Data",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.clientCertFile": {
			"name": "camel.sink.endpoint.clientCertFile",
			"description": "The Client Cert File",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.clientKeyAlgo": {
			"name": "camel.sink.endpoint.clientKeyAlgo",
			"description": "The Key Algorithm used by the client",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.clientKeyData": {
			"name": "camel.sink.endpoint.clientKeyData",
			"description": "The Client Key data",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.clientKeyFile": {
			"name": "camel.sink.endpoint.clientKeyFile",
			"description": "The Client Key file",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.clientKeyPassphrase": {
			"name": "camel.sink.endpoint.clientKeyPassphrase",
			"description": "The Client Key Passphrase",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.oauthToken": {
			"name": "camel.sink.endpoint.oauthToken",
			"description": "The Auth Token",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.password": {
			"name": "camel.sink.endpoint.password",
			"description": "Password to connect to Kubernetes",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.trustCerts": {
			"name": "camel.sink.endpoint.trustCerts",
			"description": "Define if the certs we used are trusted anyway or not",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.username": {
			"name": "camel.sink.endpoint.username",
			"description": "Username to connect to Kubernetes",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.component.kubernetes-hpa.lazyStartProducer": {
			"name": "camel.component.kubernetes-hpa.lazyStartProducer",
			"description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing.",
			"defaultValue": "false",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.component.kubernetes-hpa.autowiredEnabled": {
			"name": "camel.component.kubernetes-hpa.autowiredEnabled",
			"description": "Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.",
			"defaultValue": "true",
			"priority": "MEDIUM",
			"required": "false"
		}
	}
}