ENDOC-501 In bundler k8ssvcApi renamed to componentManagerApi #511
+23
−24
Conversation
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
nshaw
approved these changes
May 16, 2022
There was a problem hiding this comment.
Looks good - but I'll feel better if you or @jyunmitch also test at least the bundler export step.
nshaw
approved these changes
May 17, 2022
nshaw
suggested changes
May 18, 2022
| @@ -29,7 +29,7 @@ Configure a Keycloak client to grant the bundler access to the required Entando | |||
|
|
|||
| 1. Log in to Keycloak using the admin credentials. The URL will be similar to `http://YOUR-HOST-NAME/auth/` and can be verified with the following command: | |||
| ``` sh | |||
| kubectl describe ingress/default-sso-in-namespace | |||
| ent kubectl describe ingress/default-sso-in-namespace-ingress | |||
There was a problem hiding this comment.
Let's leave this as kubectl and add the missing -n entando. Looking at the rest of the tutorial, I think that's clearest.
| ``` | ||
| kubectl get secrets -n YOUR-NAMESPACE | ||
| sudo kubectl get secrets -n YOUR-NAMESPACE |
There was a problem hiding this comment.
There are 2 kubectl commands on this page. Let's leave them both as kubectl (without ent) and make sure they have the -n setting so they match. The prod page right now doesn't match since one is ent kubectl -n entando and the other is kubectl -n YOUR-NAMESPACE, on the same page.
nshaw
suggested changes
May 19, 2022
| @@ -7,12 +7,12 @@ Entando Identity Management is based on open source Keycloak. Entando Applicatio | |||
| Keycloak is protected by a Secret deployed to your Entando Kubernetes instance. You can query Kubernetes for the Secret's default admin credentials via the following, modifying this command to use your environment's namespace and Secret name: | |||
|
|
|||
| ``` | |||
| ent kubectl get secret default-sso-in-namespace-admin-secret -n entando -o go-template="{{println}}Username: {{.data.username | base64decode}}{{println}}Password: {{.data.password | base64decode}}{{println}}{{println}}" | |||
| kubectl get secret default-sso-in-namespace-admin-secret -n entando -o go-template="{{println}}Username: {{.data.username | base64decode}}{{println}}Password: {{.data.password | base64decode}}{{println}}{{println}}" -n entando | |||
There was a problem hiding this comment.
This one is sneaky. There's already a -n entando in the middle before the -o.
| @@ -7,12 +7,12 @@ Entando Identity Management is based on open source Keycloak. Entando Applicatio | |||
| Keycloak is protected by a Secret deployed to your Entando Kubernetes instance. You can query Kubernetes for the Secret's default admin credentials via the following, modifying this command to use your environment's namespace and Secret name: | |||
|
|
|||
| ``` | |||
| ent kubectl get secret default-sso-in-namespace-admin-secret -n entando -o go-template="{{println}}Username: {{.data.username | base64decode}}{{println}}Password: {{.data.password | base64decode}}{{println}}{{println}}" | |||
| kubectl get secret default-sso-in-namespace-admin-secret -n entando -o go-template="{{println}}Username: {{.data.username | base64decode}}{{println}}Password: {{.data.password | base64decode}}{{println}}{{println}}" -n entando | |||
nshaw
approved these changes
May 19, 2022
nshaw
approved these changes
May 19, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.