implement credential creation with the chart

[zackbradys]

For Cloud Credentials Auth/Creds:

# or create cloud credential secret:
  # createCloudCredentialAWS:
    # enabled: false
    # name: aws-creds
    # accessKey:
    # secretKey:
    # region:
  # createCloudCredentialAzure:
    # enabled: false
    # name: azure-creds
    # clientId:
    # clientSecret:
    # subscriptionId:
    # tenantId:
    # cloud:
  # createCloudCredentialDigitalOcean:
    # enabled: false
    # name: digitalocean-creds
    # token:
  # createCloudCredentialHarvester:
    # enabled: false
    # name: harvester-creds
    # token:
  # createCloudCredentialVsphere:
    # enabled: false
    # name: vsphere-creds
    # server:
    # username:
    # password:
    # port:

For Registry Auth/Creds:

      # createRegistryAuth:
        # enabled: false
        # name: registry-creds
        # username:
        # password:

[bcdurden]

I am pretty certain this is not possible with Harvester unless a kubeconfig is given as an input parameter. AWS/Azure should be easy

[zackbradys]

we will need to work on how this information is presented to users in the values.yaml, but true about harvester. it will be a bit complex to make it work seamlessly for each cloud provider