# Configuring CF routing for Kubo

CF routing requires that a Cloud Foundry installation with TCP routing enabled is accessible,
and the credentials for various services can be obtained.

Verify that the pre-deployment and post-deployment steps have been followed correctly to [enable TCP Routing](http://docs.cloudfoundry.org/adminguide/enabling-tcp-routing.html), 
including the creation of a shared domain with the TCP domain and the setup of the quota for TCP Routes.

In order to configure kubo to use Cloud Foundry routing, the following CF settings should be available:
  
  - Cloud Foundry TCP Router hostname
  - Cloud Foundry apps domain
  - Cloud Foundry API URL
  - Cloud Foundry UAA URL and credentials for a client with [appropriate authorities](https://github.com/cloudfoundry-incubator/routing-api#configure-oauth-clients-manually-using-uaac-cli-for-uaa)
    - Make sure to include the following authorities: `"routing.router_groups.read,routing.routes.write,cloud_controller.admin"`
  - Cloud Foundry NATS bus information - ip addresses, username, port and access credentials

Follow the steps below in order to configure Kubo to use CF routing:

1. Uncomment and fill in the values for `routing-cf-client-secret` and `routing-cf-nats-password` in 
  `<KUBO_ENV>/director-secrets.yml`

1. Configure the CF routing settings in `<KUBO_ENV>/director.yml`:

  - Comment out all the lines grouped underneath the **IaaS routing mode settings** comment
  
  - Uncomment all the lines grouped underneath the **CF routing mode settings** comment 
    and fill in all the values.
  

# Configuring CF routing for Kubo

**This topic has been relocated to the new Kubo documentation.**

**See the [Configuring Cloud Foundry Routing](https://docs-kubo.cfapps.io/installing/cf-routing/) topic.**

Add deprecation notice to Configuring CF Routing
Add deprecation notice to Configuring CF Routing