I am having an issue where I want to deploy the infrastructure on AWS. The following issues I have are -
As you are creating client_id and client_secret in https://github.com/jetstack/kube-oidc-proxy/blob/master/demo/infrastructure/modules/oauth2-secrets/secrets.tf for oauth2, so I have a doubt that you again say to create a Github OAuth Apps part in which it also creates client_id and client_secret in this part https://aws.amazon.com/blogs/opensource/consistent-oidc-authentication-across-multiple-eks-clusters-using-kube-oidc-proxy/, so my question is why to create client_id and client_secret again if you have already created using terraform in the first link?.
As you told in README file which is in demo directory, first deploy the google part then deploy the AWS part, but I want to deploy only AWS part i.e I want to create only 2 cluster of AWS not google, so is their any way to create only AWS part not Google part?.
I am having an issue where I want to deploy the infrastructure on AWS. The following issues I have are -
As you are creating client_id and client_secret in
https://github.com/jetstack/kube-oidc-proxy/blob/master/demo/infrastructure/modules/oauth2-secrets/secrets.tffor oauth2, so I have a doubt that you again say to create a Github OAuth Apps part in which it also creates client_id and client_secret in this parthttps://aws.amazon.com/blogs/opensource/consistent-oidc-authentication-across-multiple-eks-clusters-using-kube-oidc-proxy/, so my question is why to create client_id and client_secret again if you have already created using terraform in the first link?.As you told in README file which is in demo directory, first deploy the google part then deploy the AWS part, but I want to deploy only AWS part i.e I want to create only 2 cluster of AWS not google, so is their any way to create only AWS part not Google part?.