-
Notifications
You must be signed in to change notification settings - Fork 74
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'main' into sbp-rework-metadata-04042024
- Loading branch information
Showing
24 changed files
with
1,477 additions
and
365 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,56 @@ | ||
[#imagePullSecret] | ||
= Creating an imagePullSecret for the {rac} | ||
|
||
To make the resources available for deployment, you need to create an imagePullSecret. | ||
In this guide we use the name _application-collection_ for it. | ||
|
||
== Creating an imagePullSecret using kubectl | ||
|
||
Using `kubectl` to create the imagePullSecret is quite easy. | ||
Get your user name and your access token for the {rac}. | ||
Then run: | ||
|
||
---- | ||
$ kubectl -n <namespace> create secret docker-registry application-collection --docker-server=dp.apps.rancher.io --docker-username=<yourUser> --docker-password=<yourPassword> | ||
---- | ||
|
||
As secrets are namespace-sensitive, you need to create this for every namespace needed. | ||
|
||
ifdef::eic[] | ||
The related secret can then be used for the components: | ||
|
||
* xref:SAPDI3-Rancher.adoc#rancherIPS[Cert-Manager] | ||
* xref:SAP-EIC-Metallb.adoc#metalIPS[MetalLB] | ||
* xref:SAP-EIC-Redis.adoc#redisIPS[Redis] | ||
* xref:SAP-EIC-PostgreSQL.adoc#pgIPS[PostgreSQL] | ||
endif::[] | ||
|
||
++++ | ||
<?pdfpagebreak?> | ||
++++ | ||
|
||
== Creating an imagePullSecret using {rancher} | ||
|
||
You can also create an imagePullSecret using {rancher}. | ||
Therefore, open {rancher} and enter your cluster. | ||
|
||
Navigate to *Storage* -> *Secrets* as shown below: | ||
|
||
image::EIC-Secrets-Menu.png[title=Secrets Menu,scaledwidth=99%] | ||
|
||
++++ | ||
<?pdfpagebreak?> | ||
++++ | ||
|
||
Click the *Create* button in the top right corner. | ||
|
||
image::EIC-Secrets-Overview.png[title=Secrets Overview,scaledwidth=99%] | ||
|
||
A window will appear asking you to select the Secret type. Select *Registry* as shown here: | ||
|
||
image::EIC-Secrets-Types.png[title=Secrets Type Selection,scaledwidth=99%] | ||
|
||
Enter a name such as _application-collection_ for the Secret. In the text box *Registry Domain Name*, enter _dp.apps.rancher.io_. | ||
Enter your user name and password and click the *Create* button at the bottom right. | ||
|
||
image::EIC-Secret-Create.png[title=Secrets Creation Step,scaledwidth=99%] |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
[#LoginApplicationCollection] | ||
= Login into the Application Collection Registry | ||
|
||
To install the Helm Charts from the _application-collection_ you need to log in into the registry. This needs to be done with the Helm client. | ||
|
||
To log in to the {rac}, run: | ||
[source, bash] | ||
---- | ||
$ helm registry login dp.apps.rancher.io/charts -u <yourUser> -p <your-token> | ||
---- | ||
|
||
ifdef::eic[] | ||
The login process is needed for the following application installations: | ||
|
||
* xref:SAPDI3-Rancher.adoc#rancherLIR[Cert-Manager] | ||
* xref:SAP-EIC-Metallb.adoc#metalLIR[MetalLB] | ||
* xref:SAP-EIC-Redis.adoc#redisLIR[Redis] | ||
* xref:SAP-EIC-PostgreSQL.adoc#pgLIR[PostgreSQL] | ||
endif::[] |
Oops, something went wrong.