Terrakube
Initial Install on Azure #298
-
|
There seem to be a handful of steps that are not called out in the documentation. For people who work with these things every day it may be obvious, but it is unclear for those who do not. Take for example the initial helm charts. There are a lot of values like this: https://terrakube-ui.domain.com It would be advisable to walk through changing the service ingress to "LoadBalancer" along with populating the generated public IP's to support external connectivity. Just deploying the helm chart as-is will leave the service inaccessible. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 21 replies
-
|
Hello @erick-prosimo, I understand your point there are like different parameters that you need to change in order to make the installation work. For the domain that you need to update I was thinking maybe just leaving one parameter asking the domain that you will use and create some output in the helm chart with the URLs for the api, registry, dex component, etc instead of filling all the URL in the helm chart values. Example domain: myterrakube.comAnd in the helm chart output could be something like this. Your terrakube installation is complete the URLs will be the following:
Api: terrakube-api.myterrakube.com
Registry: terrakube-reg.myterrakube.com
Dex: terrakube-api.myterrakube.com/dex
But there are other parameters I am not really sure what could be the best practice becuase there are like several configuration options depending of where you are installing terrakube this is the reason we left like several examples in the helm chart repository. All suggestions, ideas are welcome even if you want to contribute feel free to send the pull request to improve the documentation. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, I am a little smaller than that. I did find the auth issue as well, typo in the helm chart. I think I finally got it working! |
Beta Was this translation helpful? Give feedback.
-
|
That sounds great @erick-prosimo |
Beta Was this translation helpful? Give feedback.
-
|
I'm still a little confused on the values for these 2 items: patSecret: "XXXXXXX" Are these just 32 character secrets that you made up yourself for terrakube to use? |
Beta Was this translation helpful? Give feedback.
-
|
Hello @jderieg you can find the information here https://docs.terrakube.org/getting-started/deployment/token-security The patSecret should be 32 character long and it should be base64 compatible string, internally Terrakube will use the patSecret to "signed" the personal access token that you can generate from the UI. You can check here https://docs.terrakube.org/user-guide/organizations/api-tokens The internalSecret is the secret used to "signed" the token for internal between Terrakube components. You should change that when you are deploying Terrakube. I hope this can answer your questions |
Beta Was this translation helpful? Give feedback.
-
|
That's helpful! Thanks for the quick reply. |
Beta Was this translation helpful? Give feedback.
Hello @erick-prosimo, I understand your point there are like different parameters that you need to change in order to make the installation work.
For the domain that you need to update I was thinking maybe just leaving one parameter asking the domain that you will use and create some output in the helm chart with the URLs for the api, registry, dex component, etc instead of filling all the URL in the helm chart values.
Example
And in the helm chart output could be something like this.
Your terrakube installation is complete the URLs will be the following: Api: terrakube-api.myterrakube.com Registry: terrakube-reg.myterrakube.com Dex: terrakube-api.myterrakube.com/…