-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add guide for automatic DNS and certificate management in Control Center #4117
base: latest
Are you sure you want to change the base?
Conversation
== Prerequisites | ||
|
||
To utilize this feature, ensure the following requirements are met: | ||
|
||
1. **ExternalDNS Operator**: This operator manages DNS records in supported DNS providers. | ||
2. **Supported DNS Service**: Control Center supports services compatible with ExternalDNS, such as Google Cloud DNS, Azure DNS, or DigitalOcean. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This guide also assumes that you have set up a Kubernetes cluster, connected to it with kubectl and installed Control Center.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it assumes you already satisfy the requirements to install Control Center. It does not require Control Center to be installed, as it can be installed with the same values for the first time.
There's still an error here: while ExternalDNS is a requirement, it is also a dependency that can be installed along with Control Center so better clarify this.
export DO_API_TOKEN=dop_v1_your_generated_token | ||
kubectl create secret generic digitalocean-api --from-literal=token=${DO_API_TOKEN} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we include commands for Windows too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, can you suggest? Or maybe we can find a command that works for both?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
export DO_API_TOKEN=dop_v1_your_generated_token | |
kubectl create secret generic digitalocean-api --from-literal=token=${DO_API_TOKEN} | |
[.example] | |
-- | |
[source,bash] | |
---- | |
<source-info group="MacOS / Linux"></source-info> | |
export DO_API_TOKEN=dop_v1_your_generated_token | |
kubectl create secret generic digitalocean-api --from-literal=token=${DO_API_TOKEN} | |
---- | |
Add a new environment variable `DO_API_TOKEN` with your generated token value. Then execute the following command: | |
[source,bash] | |
---- | |
<source-info group="Windows"></source-info> | |
# Command Prompt | |
kubectl create secret generic digitalocean-api --from-literal=token=%DO_API_TOKEN% | |
# PowerShell | |
kubectl create secret generic digitalocean-api --from-literal=token=$env:DO_API_TOKEN | |
---- | |
-- |
Closes https://github.com/vaadin/control-center/issues/800 and closes https://github.com/vaadin/control-center/issues/801