このコンテンツは選択した言語では利用できません。
Chapter 4. Set up a DNS provider secret
Your DNS provider supplies credentials to access the DNS zones that Connectivity Link can use to set up your DNS configuration. You must ensure that these credentials have access to only the DNS zones that you want Connectivity Link to manage with your DNSPolicy.
You must apply the following Secret resource to each cluster. If you are adding an additional cluster, add it to the new cluster.
Prerequisites
Procedure
Create the namespace that the Gateway will be deployed in as follows:
kubectl create ns ${KUADRANT_GATEWAY_NS}kubectl create ns ${KUADRANT_GATEWAY_NS}Copy to Clipboard Copied! Toggle word wrap Toggle overflow Create the secret credentials in the same namespace as the Gateway as follows:
kubectl -n ${KUADRANT_GATEWAY_NS} create secret generic aws-credentials \ --type=kuadrant.io/aws \ --from-literal=AWS_ACCESS_KEY_ID=$KUADRANT_AWS_ACCESS_KEY_ID \ --from-literal=AWS_SECRET_ACCESS_KEY=$KUADRANT_AWS_SECRET_ACCESS_KEYkubectl -n ${KUADRANT_GATEWAY_NS} create secret generic aws-credentials \ --type=kuadrant.io/aws \ --from-literal=AWS_ACCESS_KEY_ID=$KUADRANT_AWS_ACCESS_KEY_ID \ --from-literal=AWS_SECRET_ACCESS_KEY=$KUADRANT_AWS_SECRET_ACCESS_KEYCopy to Clipboard Copied! Toggle word wrap Toggle overflow Before adding a TLS certificate issuer, create the secret credentials in the
cert-managernamespace as follows:kubectl -n cert-manager create secret generic aws-credentials \ --type=kuadrant.io/aws \ --from-literal=AWS_ACCESS_KEY_ID=$KUADRANT_AWS_ACCESS_KEY_ID \ --from-literal=AWS_SECRET_ACCESS_KEY=$KUADRANT_AWS_SECRET_ACCESS_KEY
kubectl -n cert-manager create secret generic aws-credentials \ --type=kuadrant.io/aws \ --from-literal=AWS_ACCESS_KEY_ID=$KUADRANT_AWS_ACCESS_KEY_ID \ --from-literal=AWS_SECRET_ACCESS_KEY=$KUADRANT_AWS_SECRET_ACCESS_KEYCopy to Clipboard Copied! Toggle word wrap Toggle overflow