Skip to content
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

Open
wants to merge 1 commit into
base: latest
Choose a base branch
from

Conversation

heruan
Copy link
Member

@heruan heruan commented Feb 10, 2025

@github-actions github-actions bot added the Language unchecked English language and AsciiDoc formatting checks haven't been done label Feb 10, 2025
@heruan heruan self-assigned this Feb 10, 2025
@heruan heruan requested a review from MatthewVaadin February 10, 2025 13:55
Comment on lines +13 to +18
== 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.
Copy link
Contributor

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.

Copy link
Member Author

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.

Comment on lines +40 to +41
export DO_API_TOKEN=dop_v1_your_generated_token
kubectl create secret generic digitalocean-api --from-literal=token=${DO_API_TOKEN}
Copy link
Contributor

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?

Copy link
Member Author

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?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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
----
--

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Language unchecked English language and AsciiDoc formatting checks haven't been done
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants