HTTP
HTTP Connections are used to query data via any http/https compatible resource
Schema
| Field | Description | Scheme | Required | 
|---|---|---|---|
url | URL | string | true | 
username | Username | EnvVar | |
password | Password | EnvVar | |
oauth | OAuth | OAuth | |
bearer | Bearer | EnvVar | |
tls | TLS Config | TLS | |
connection | Connection Name | string | 
info
If connection is already created connection (Connection Name) can be used as a reference instead of redefining all fields. Read more on connection referencing
OAuth
| Field | Description | Scheme | Required | 
|---|---|---|---|
tokenURL | Token URL | string | true | 
clientID | Client ID | EnvVar | true | 
clientSecret | Client Secret | EnvVar | true | 
scopes | Scopes | []string | |
params | Params | map[string]string | 
TLS
| Field | Description | Scheme | Required | 
|---|---|---|---|
key | PEM encoded client private key | EnvVar | true | 
ca | PEM encoded certificate of the CA to verify the server certificate | EnvVar | true | 
cert | PEM encoded client certificate | EnvVar | true | 
insecureSkipVerify | controls whether a client verifies the server's certificate chain and host name | bool | |
handshakeTimeout | Handshake timeout (Default: 10 seconds) | time.Duration | 
Example
This example demonstrates how to configure an HTTP connection in Mission Control:
http-connection.yamlapiVersion: v1
kind: Connection
metadata:
  name: http-connection
spec:
  http:
    url: https://example.com
    username:
      value: user
    password:
      valueFrom:
        secretKeyRef:
          name: credentials
          key: password