Skip to main content

Cloud Foundry

Connect a Cloud Foundry foundation so its applications sit alongside your Kubernetes workloads in NudgeBee. Works with Pivotal Cloud Foundry (PCF) via UAA, and with Korifi or Kubernetes-backed foundations via a service account token.

Prerequisites​

  • The Cloud Foundry API endpoint, e.g. https://api.sys.example.com.
  • Credentials for one of the two supported authentication methods:
    • Bearer Token — a Korifi or Kubernetes service account token.
    • UAA OAuth2 — UAA client credentials, for PCF.

Step 1: Configure the Integration in NudgeBee​

Navigate to Admin > Integrations > Kubernetes & Cloud, select Cloud Foundry, then click Add Cloud Foundry Account. The form walks through five steps.

The Cloud Foundry tile in the Kubernetes & Cloud tab of the integrations catalog

  • Account Name * (Required)
    • A name for this foundation, e.g. pcf-prod.
  • CF API URL * (Required)
    • The Cloud Foundry API endpoint, e.g. https://api.sys.example.com.
  • Account Type
    • Production or Non-production. This drives how the foundation is treated in cost and optimization views.
  • Authentication Method
    • Bearer Token — for Korifi or a Kubernetes service account token.
    • UAA OAuth2 — for PCF with UAA client credentials.
  • Credentials
    • Bearer Token * when using bearer authentication, or the UAA client id and secret when using UAA OAuth2.
  • Skip SSL Verification
    • Enable only for foundations presenting self-signed certificates.

The Cloud Foundry configuration form, showing the five-step panel, the CF API URL and the bearer-token and UAA OAuth2 options

Step 2: Save​

Click Save.

caution

Skip SSL Verification disables certificate checking for this connection. Prefer installing a trusted certificate on the foundation; use this only where that is genuinely not possible, and never against an endpoint reachable from the public internet.

Verify the Integration​

  1. After saving, the account appears under Admin > Integrations > Kubernetes & Cloud as Enabled.
  2. Open Infra and confirm the foundation's applications appear.

Troubleshooting​

SymptomLikely CauseFix
Certificate errors on saveSelf-signed certificate on the API endpointInstall a trusted certificate, or enable Skip SSL Verification if the endpoint is on a private network.
401 Unauthorized with a bearer tokenThe token expired, or belongs to a service account without read accessIssue a fresh token for a service account that can list orgs, spaces and apps.
401 with UAA OAuth2Wrong client id or secret, or the client lacks the required scopesConfirm the UAA client credentials and that the client is authorized to read the foundation.
Connects but no applications appearThe identity can authenticate but cannot list spacesGrant the account read access across the orgs and spaces you want visible.
Wrong API endpointThe UI or login endpoint used instead of the APIUse the api. endpoint, not login. or the Apps Manager URL.