Cloudflare

Cloudflare provider requires apitoken token and accountid id field in string format.

Cloudflare DNS Load Balancing

Claudie creates A DNS records with loadbalancing and healtcheck functionality. To enable this feature, you must have the Load Balancing add-on enabled in your Cloudflare plan. Without this add-on, Claudie will still create the DNS A records, but they won't be monitored for availability.

DNS example

apiVersion: v1
kind: Secret
metadata:
  name: cloudflare-secret
data:
  apitoken: a3NsSVNBODc4YTZldFlBZlhZY2c1aVl5ckZHTmxDeGM=
  accountid: ODU1NGEyM3J0NnU4NmRjNGFzZDE1ODc2NHcyNGIyNTQK
type: Opaque

Create Cloudflare credentials

You can create Cloudflare API token by following this guide. The required permissions for the zone you want to use are:

Zone:Read
DNS:Read
DNS:Edit

If Claudie will be creating load-balanced DNS records, the following additional permissions are required:

Load Balancing:Monitors And Pools:Edit
Billing:Read

The Billing: Read permission is necessary to verify that the Load Balancing feature is enabled and active in your Cloudflare account.

DNS setup

If you wish to use Cloudflare as your DNS provider where Claudie creates DNS records pointing to Claudie managed clusters, you will need to create a public DNS zone by following this guide.

Cloudflare is not my domain registrar

If you haven't acquired a domain via Cloudflare and wish to utilize Cloudflare for hosting your zone, you can refer to this guide on Cloudflare nameservers. However, if you prefer not to use the entire domain, an alternative option is to delegate a subdomain to Cloudflare.

Input manifest examples

Load balancing example

Showcase example

To make this example functional, you need to specify control plane and node pools. This current showcase will produce an error if used as is.

Create a secret for Cloudflare and AWS providers

The secret for an Cloudflare provider must include the following mandatory fields: apitoken and accountid

kubectl create secret generic cloudflare-secret-1 --namespace=mynamespace --from-literal=apitoken='kslISA878a6etYAfXYcg5iYyrFGNlCxc' --from-literal=accountid='8554a23rt6u86dc4asd158764w24b254'

The secret for an AWS provider must include the following mandatory fields: accesskey and secretkey.

kubectl create secret generic aws-secret-1 --namespace=mynamespace --from-literal=accesskey='SLDUTKSHFDMSJKDIALASSD' --from-literal=secretkey='iuhbOIJN+oin/olikDSadsnoiSVSDsacoinOUSHD'

apiVersion: claudie.io/v1beta1
kind: InputManifest
metadata:
  name: cloudflare-example-manifest
  labels:
    app.kubernetes.io/part-of: claudie
spec:
  providers:
    - name: cloudflare-1
      providerType: cloudflare
      secretRef:
        name: cloudflare-secret-1
        namespace: mynamespace

    - name: aws-1
      providerType: aws
      secretRef:
        name: aws-secret-1
        namespace: mynamespace

  nodePools: 
    dynamic:
      - name: loadbalancer
        providerSpec:
          name: aws-1
          region: eu-central-1
          zone: eu-central-1c
        count: 2
        serverType: t3.medium
        image: ami-0965bd5ba4d59211c

  kubernetes:
    clusters:
      - name: cluster
        version: v1.31.0
        network: 192.168.2.0/24
        pools:
          control: []
          compute: []

  loadBalancers:
    roles:
      - name: apiserver
        protocol: tcp
        port: 6443
        targetPort: 6443
        targetPools: []
    clusters:
      - name: apiserver-lb-prod
        roles:
          - apiserver
        dns:
          dnsZone: dns-zone
          provider: cloudflare-1
          hostname: my.fancy.url
        targetedK8s: prod-cluster
        pools:
          - loadbalancer