docs: add tutorial for usage with Anexia Engine #5904
Conversation
|
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
cncf-cla: no
|
Welcome @davidkroell! |
k8s-ci-robot
added
the
needs-ok-to-test
|
Hi @davidkroell. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
k8s-ci-robot
added
the
size/L
|
Not sure is this repository is the right location. Most likely this tutorial is more relevant here https://engine.anexia-it.com/docs/en or here https://github.com/anexia/k8s-external-dns-webhook |
|
Hi @ivankatliarchuk that's only here because a lot of other providers also have tutorials in the documentation here. If it's no longer wanted this way it is no problem at all - just let me know. |
| ## Creating an Anexia API Token | ||
|
|
||
| To use ExternalDNS with CloudDNS, you need an API token to manage DNS zones and records. | ||
| For production usage it is advised to use a **service account** to manage DNS records. |
There was a problem hiding this comment.
| For production usage it is advised to use a **service account** to manage DNS records. | |
| For production usage, it is advised to use a **service account** to manage DNS records. |
| For production usage it is advised to use a **service account** to manage DNS records. | ||
| View the official [documentation how to create a service account and retrieve the respective API token](https://engine.anexia-it.com/docs/en/module/engine-core/getting-started/managing-users-and-teams/managing-users). | ||
|
|
||
| Once the user is created the retrieval of the API token itself is very similar to retrieving it from your personal user: |
There was a problem hiding this comment.
| Once the user is created the retrieval of the API token itself is very similar to retrieving it from your personal user: | |
| Once the user is created, the retrieval of the API token itself is very similar to retrieving it from your personal user: |
| kubectl apply -f web-demo-service.yaml | ||
| ``` | ||
|
|
||
| The service is going to expose the application on port 80. |
There was a problem hiding this comment.
| The service is going to expose the application on port 80. | |
| The service will expose the application on port 80. |
|
|
||
| ### Verifying everything worked | ||
|
|
||
| Verification if the DNS records were created can be done in multiple ways: |
There was a problem hiding this comment.
How does this sound?
| Verification if the DNS records were created can be done in multiple ways: | |
| Verification that the DNS records were created can be done in multiple ways: |
|
|
||
| ## Cleanup | ||
|
|
||
| > **Optional:** Only cleanup your changes if they are no longer needed. |
There was a problem hiding this comment.
English is dumb. This just got flagged by Grammarly, but I guess cleanup is a noun/adjective, but clean up is a verb
| > **Optional:** Only cleanup your changes if they are no longer needed. | |
| > **Optional:** Only clean up your changes if they are no longer needed. |
4 participants
What does it do ?
Adds documentation for usage with Anexia Engine.
Motivation
Tutorial was missing.
More