Modified: websites/production/camel/content/servicecall-eip.html ============================================================================== --- websites/production/camel/content/servicecall-eip.html (original) +++ websites/production/camel/content/servicecall-eip.html Thu Oct 6 14:18:41 2016 @@ -85,7 +85,7 @@ <tbody> <tr> <td valign="top" width="100%"> -<div class="wiki-content maincontent"><h2 id="ServiceCallEIP-ServiceCallEIP">ServiceCall EIP</h2><p><strong>Available as of Camel 2.18</strong></p><p>The serviceCall EIP allows to call remote services in a distributed system. The service to call is looked up in a service registry of some sorts such as Kubernetes, Consul, etcd, zookeeper.<br clear="none">The EIP separates the configuration of the service registry from the calling of the service. </p><p>Maven users will need to add the dependency for the service registry supported from the following:</p><ul><li>camel-consul</li><li>camel-etcd</li><li>camel-kubernetes</li><li>camel-ribbon</li></ul><p>Each implementation has their own set of configuration.</p><h3 id="ServiceCallEIP-Syntax">Syntax</h3><p>When calling a service you may just refer to the name of the service in the EIP as shown below:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> +<div class="wiki-content maincontent"><h2 id="ServiceCallEIP-ServiceCallEIP">ServiceCall EIP</h2><p><strong>Available as of Camel 2.18</strong></p><p>The <strong><code>serviceCall</code></strong> EIP allows to call remote services in a distributed system. The service to call is looked up in a service registry of some sorts such as Kubernetes, Consul, etcd, Zookeeper. The EIP separates the configuration of the service registry from the calling of the service. </p><p>Maven users will need to add the dependency for the service registry supported from the following:</p><ul><li><code>camel-consul</code></li><li><code>camel-etcd</code></li><li><code>camel-kubernetes</code></li><li><code>camel-ribbon</code></li></ul><p>Each implementation has their own set of configuration.</p><h3 id="ServiceCallEIP-Syntax">Syntax</h3><p>When calling a service you may just refer to the name of the service in the EIP as shown below:</p><div class="code panel pdl" style="border-width: 1px;"><div cl ass="codeContent panelContent pdl"> <script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[from("direct:start") .serviceCall("foo") .to("mock:result");]]></script> @@ -97,19 +97,19 @@ <to uri="mock:result"/> </route> </camelContext>]]></script> -</div></div><p>Camel will then lookup a service with the name "foo" from the chosen Camel component that integrates with the service registry. The lookup returns a set of IP:PORT paris that refer to which active servers that host the remote service. Camel will then pick a random server to use and then build a Camel uri with the chosen IP and PORT number. By default Camel uses the HTTP component, so the example above will resolve into a Camel uri that is called by a dynamic to endpoint as shown:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> +</div></div><p>Camel will then lookup a service with the name <strong><code>foo</code></strong> from the chosen Camel component that integrates with the service registry. The lookup returns a set of <strong><code>IP:PORT</code></strong> pairs that refer to a list of active servers that host the remote service. Camel will then select a server at random from the list to use and then build a Camel URI with the chosen IP and PORT number.</p><p>By default Camel uses the HTTP component, so the example above will resolve into a Camel URI that is called by a dynamic <strong><code>toD</code></strong> endpoint as shown:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> <script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[toD("http://IP:PORT") Â <toD uri="http:IP:port"/>]]></script> -</div></div><p>You can also call the service using URI parameters such as beer=yes</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> +</div></div><p>You can also call the service using URI parameters such as <strong><code>beer=yes</code></strong>:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> <script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[serviceCall("foo?beer=yes") Â -<serviceCall name="foo?beer=yes")]]></script> +<serviceCall name="foo?beer=yes"/>]]></script> </div></div><p>You can also provide a context-path such as shown:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> <script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[serviceCall("foo/beverage?beer=yes") Â -<serviceCall name="foo/beverage?beer=yes")]]></script> -</div></div><h3 id="ServiceCallEIP-ServiceNametoCamelURIExamples">Service Name to Camel URI Examples</h3><p>So as you can see above the service name is resolved as a Camel endpoint uri, and here is a few more examples (where -> shows what the Camel uri is resolved as)</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> +<serviceCall name="foo/beverage?beer=yes"/>]]></script> +</div></div><h3 id="ServiceCallEIP-ServiceNametoCamelURIExamples">Service Name to Camel URI Examples</h3><p>So as you can see above the service name is resolved as a Camel endpoint URI, and here is a few more examples (where <strong><code>-></code></strong> shows the resolution of the Camel URI):</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> <script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[serviceCall("myService") -> http://hostname:port serviceCall("myService/foo") -> http://hostname:port/foo serviceCall("http:myService/foo") -> http:hostname:port/foo @@ -117,13 +117,13 @@ serviceCall("http:myService/foo&quo <serviceCall name="myService"/> -> http://hostname:port <serviceCall name="myService/foo"/> -> http://hostname:port/foo <serviceCall name="http:myService/foo"/> -> http:hostname:port/foo]]></script> -</div></div><p>If you want full control of the resolved URI you can provide an additional uri parameter where you specify the Camel uri as you want. In the uri you can use the service name which are then resolved to IP:PORT as shown:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> +</div></div><p>If you want full control of the resolved URI you can provide an additional URI parameter where you specify the Camel URI as you want. In the URI you can use the service name which are then resolved to <strong><code>IP:PORT</code></strong> as shown:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> <script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[serviceCall("myService", "http:myService.host:myService.port/foo") -> http:hostname:port/foo serviceCall("myService", "netty4:tcp:myService?connectTimeout=1000") -> netty:tcp:hostname:port?connectTimeout=1000 Â <serviceCall name="myService" uri="http:myService.host:myService.port/foo"/> -> http:hostname:port/foo <serviceCall name="myService" uri="netty4:tcp:myService?connectTimeout=1000"/> -> netty:tcp:hostname:port?connectTimeout=1000]]></script> -</div></div><p>In the example above we want to call a service named "myService" and we can control the resolved URI as in the 2nd parameter. Notice how in the 1st we can use serviceName.host and serviceName.port to refer to either the IP or PORT. If you just use serviceName then its resolved as IP:PORT.</p><h3 id="ServiceCallEIP-ConfiguringServiceCall">Configuring Service Call</h3><p>By default Camel will call the service using the <a shape="rect" href="http.html">HTTP</a> component, but you can configure to use a different component such as <a shape="rect" href="http4.html">HTTP4</a>, <a shape="rect" href="netty4-http.html">Netty4 HTTP</a> as shown:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> +</div></div><p>In the example above we want to call a service named <strong><code>myService</code></strong> and we can control the resolved URI as in the second parameter. Notice how in the first example we can use <strong><code>serviceName.host</code></strong> and <strong><code>serviceName.port</code></strong> to refer to either the <code>IP</code> or <code>PORT</code>. If you just use <strong><code>serviceName</code></strong> then it's resolved as <code>IP:PORT</code>.</p><h3 id="ServiceCallEIP-ConfiguringServiceCall">Configuring Service Call</h3><p>By default Camel will call the service using the <a shape="rect" href="http.html">HTTP</a> component, but you can configure to use a different component such as <a shape="rect" href="http4.html">HTTP4</a>, <a shape="rect" href="netty4-http.html">Netty4 HTTP</a> as shown:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> <script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[KubernetesConfigurationDefinition config = new KubernetesConfigurationDefinition(); config.setComponent("netty4-http"); Â @@ -133,7 +133,7 @@ context.setServiceCallConfiguration(conf from("direct:start") .serviceCall("foo") .to("mock:result");]]></script> -</div></div><p>.. and in XML DSL:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> +</div></div><p>In XML DSL:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> <script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<camelContext xmlns="http://camel.apache.org/schema/spring"> <kubernetesConfiguration id="kubernetes" component="netty4-http"/> <route> @@ -142,9 +142,8 @@ from("direct:start") <to uri="mock:result"/> </route> </camelContext> - ]]></script> -</div></div><h3 id="ServiceCallEIP-CommonConfiguration">Common Configuration</h3><p>These are the common configuration that each implementation is sharing.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh">Name</th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default<br clear="none">Value</p></th><th colspan="1" rowspan="1" class="confluenceTh">Description</th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">component</td><td colspan="1" rowspan="1" class="confluenceTd">http</td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the default Camel component to use for calling the remote service.<br clear="none">By default the http component is used. You can configure this to use netty4-http, jetty, restlet or some other components of choice.<br clear="none">If the service is not HTTP protocol you can use other components such as mqtt, jms, amqp</tt> etc.<br clear="none">If the service call has been configured using an uri, then the component from the uri is used instead of this default component.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">loadBalancerRef</td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd">Sets a reference to a custom org.apache.camel.spi.ServiceCallLoadBalancer to use.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">serverListStrategyRef</td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd">Sets a reference to a custom org.apache.camel.spi.ServiceCallServerListStrategy to use.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">clientProperty</td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd">These properties are specific to what service call implementation are in use.<br clear="none">For example if using ribbon, then the cli ent properties are define in com.netflix.client.config.CommonClientConfigKey.</td></tr></tbody></table></div><p> </p><h3 id="ServiceCallEIP-KubernetesConfiguration">Kubernetes Configuration</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default Value</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">lookup</td><td colspan="1" rowspan="1" class="confluenceTd">environment</td><td colspan="1" rowspan="1" class="confluenceTd">What strategy to lookup the service. Possible values: environment, dns, client. By default enviornment is used to use environment variables. dns is for using DNS domain names. client is for use Java Client to call the kubernetes master API and query which servers are active hosting the service.</td></tr><tr><td colspan="1" rowspan="1" c lass="confluenceTd">dnsDomain</td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd">Sets the DNS domain to use for DNS lookup.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">namespace</td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd">The kubernetes namespace to use. Will by default use namespace from the ENV variable KUBERNETES_MASTER.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">apiVersion</td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd">Client lookup. Kubernetes API version.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">masterUrl</td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd">Client lookup. The url for the Kubernetes master. </td></tr><tr><td colspan="1" rowspan="1" class="confluen ceTd">username</td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd">Sets the username for authentication when using client lookup</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">password</td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd">Sets the password for authentication when using client lookup</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">oauthToken</td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd">Sets the OAUTH token for authentication (instead of username/password) when using client lookup</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">caCertData</td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd">Sets the Certificate Authority data when using client lookup</td></tr><tr><td colspan="1" row span="1" class="confluenceTd">caCertFile</td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd">Sets the Certificate Authority data that are loaded from the file when using client lookup</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">clientCertData</td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd">Sets the Client Certificate data when using client lookup</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">clientCertFile</td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd">Sets the Client Certificate data that are loaded from the file when using client lookup</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">clientKeyAlgo</td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd">Sets the Client Keystore algorithm, s uch as RSA when using client lookup</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">clientKeyData</td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd">Sets the Client Keystore data when using client lookup</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">clientKeyFile</td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd">Sets the Client Keystore data that are loaded from the file when using client lookup</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">clientKeyPassphrase</td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd">Sets the Client Keystore passphrase when using client lookup</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">trustCerts</td><td colspan="1" rowspan="1" class="confluenceTd">false</td><td colspan="1" rowspan="1" class="confluenceTd">Se ts whether to turn on trust certificate check when using client lookup</td></tr></tbody></table></div><h3 id="ServiceCallEIP-RibbonConfiguration">Ribbon Configuration</h3><p>Currently no ribbon specific options yet.</p><h3 id="ServiceCallEIP-"><br clear="none"><br clear="none"></h3></div> +</div></div><h3 id="ServiceCallEIP-CommonConfiguration">Common Configuration</h3><p>These are the common configuration that each implementation is sharing.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default<br clear="none">Value</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>clientProperty</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"><p>These properties are specific to what service call implementation are in use.</p><p>For example if using ribbon, then the client properties are define in <strong><code>com.netflix.client.config.CommonClientConfigKey</code></strong>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>component</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>http</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the default Camel component to use for calling the remote service. By default the <strong><code>http</code></strong> component is used.</p><p>You can configure this to use <strong><code>netty4-http</code></strong>, <strong><code>jetty</code>, <code>restlet</code></strong> or some other components of choice.<br clear="none">If the service does not use the HTTP protocol then other components such as <strong><code>mqtt</code>, <code>jms</code></strong>, <strong><code>amqp</code></strong> etc can be used.<br clear="none">If the service call has been configured using a URI the component specified in the URI is used instead of this default component.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>loadBalancerRef</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" cla ss="confluenceTd"><p>Sets a reference to a custom <strong><code>org.apache.camel.spi.ServiceCallLoadBalancer</code></strong> to use.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>serverListStrategyRef</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets a reference to a custom <strong><code>org.apache.camel.spi.ServiceCallServerListStrategy</code></strong> to use.</p></td></tr></tbody></table></div><p> </p><h3 id="ServiceCallEIP-KubernetesConfiguration">Kubernetes Configuration</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default Value</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>apiVersion</code></p></td><td colspan="1" r owspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"><p>Kubernetes API version when using <strong><code>client</code></strong> lookup.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>caCertData</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the Certificate Authority data when using <strong><code>client</code></strong> lookup.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>caCertFile</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the Certificate Authority data that are loaded from the file when using <strong><code>client</code></strong> lookup.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>clientCertData</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the Client Certificate data when using <strong><code>client</code></strong> lookup.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>clientCertFile</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the Client Certificate data that are loaded from the file when using <strong><code>client</code></strong> lookup.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>clientKeyAlgo</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the Client Keystore algorithm, such as RSA when using <strong><code>client</code></strong> lookup.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>clientKeyData</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan= "1" class="confluenceTd"><p>Sets the Client Keystore data when using <strong><code>client</code></strong> lookup.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>clientKeyFile</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the Client Keystore data that are loaded from the file when using <strong><code>client</code></strong> lookup.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>clientKeyPassphrase</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the Client Keystore passphrase when using <strong><code>client</code></strong> lookup.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>dnsDomain</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the D NS domain to use for <strong><code>dns</code></strong> lookup.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>lookup</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>environment</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The choice of strategy used to lookup the service.</p><p>The list of lookup strategies are:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Lookup Strategy</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><strong><code>environment</code></strong></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Use environment variables.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><strong><code>dns</code></strong></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Use DNS domain names.</p></td></t r><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><strong><code>client</code></strong></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Use Java Client to call the Kubernetes master API and query which servers are actively hosting the service.</p></td></tr></tbody></table></div></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>masterUrl</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"><p>The URL for the Kubernetes master when using <strong><code>client</code></strong> lookup.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>namespace</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"><p>The Kubernetes namespace to use. By default the namespace's name is taken from the environment variable <strong><code>KUBERNETES_MASTER</code></strong>.</p></td></tr><tr><td colspan=" 1" rowspan="1" class="confluenceTd"><p><code>oauthToken</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the <code>OAUTH</code> token for authentication (instead of username/password) when using <strong><code>client</code></strong> lookup.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>password</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the password for authentication when using <strong><code>client</code></strong> lookup.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>trustCerts</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets whether to turn on trust certificate check when using <strong><code>client</code></strong> lookup.</p></td></tr>< tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>username</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the username for authentication when using <strong><code>client</code></strong> lookup.</p></td></tr></tbody></table></div><h3 id="ServiceCallEIP-RibbonConfiguration">Ribbon Configuration</h3><p>Currently no ribbon specific options yet.</p></div> </td> <td valign="top"> <div class="navigation">