Adding default config

[vvondruska]

This PR:

Adds a simplified way to configure auth apps in the bundle.

There is a new defaultConfig section available in the Helm values, which can be used to provide essential details about Dex connectors and RBAC rules. Some additional configuration options for Dex are also supported. Everything else that is required to deploy the Auth bundle is retrieved automatically from existing configs.

The defaultConfgi section has the following structure:

defaultConfig:
  deployDexK8SAuthenticator: false # optional, determines whether the K8s Authenticator is deployed together with Dex
  oidc: # in case the defaultConfig is defined, the oidc property is required
    expiry: # optional: defines expiration rules for tokens generated by Dex
      signingKeys: 6h
      idTokens: 30m
#   Specification of customer and/or GiantSwarm Dex connectors.
#   Either customer or giantswarm connectors or both are required.   
    customer: # specification of Dex connector details - most importantly credentials: 
      connectors:
      - id: CONNECTOR_ID # common name is "customer"
        connectorName: CONNECTOR_NAME
        connectorType: CONNECTOR_TYPE # e.g. "microsoft" or "github"
        connectorConfig: |- # specific configuration based on connector type. Structure comes from Dex.
          clientID: CLIENT_ID
          clientSecret: CLIENT_SECRET
          tenant: TENANT_ID
#   giantswarm:
#     connectors:
#     - ...
  rbac: # optional but recommended
  - role: ROLE_NAME #required
    namespaces: # optional - if omitted, cluster-wide bindings are created
    - NAMESPACE
    groups: # either groups or users or both are required
    - CUSTOMER_GROUP_NAME
    users:
    - USER_NAME

More detailed configuration can be provided in the "standard" apps section if needed. In that case the defaultConfig section can be omitted.

When both defaultConfig and apps sections are present, they are merged together and the apps section takes priority.

Testing

Description on how auth-bundle can be tested.

• fresh install works
  • AWS
  • Azure
  • KVM
• upgrade from previous version works
  • AWS
  • Azure
  • KVM

Checklist

• Update changelog in CHANGELOG.md.
• Make sure values.yaml and values.schema.json are valid.

[anvddriesch]

looks good to me! Just one question