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.

Sign up for GitHub

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

ENDOC-797 fix format #821

Merged
merged 1 commit into from
Mar 7, 2024
Merged

ENDOC-797 fix format #821

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 15 additions & 16 deletions vuepress/docs/next/tutorials/curate/bundle-private-images.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ For microservices in a private image registry, follow the [install guide here](m
## Tutorial
### Step 1: Create the Registry Credentials
1. Create the registry JSON configuration using your registry and credentials on the port of your choice:
```
``` json
{
"auths": {
"YOUR-REGISTRY.com": {
Expand All @@ -25,7 +25,6 @@ For microservices in a private image registry, follow the [install guide here](m
}
}
}

```
2. [Convert the JSON configuration into a base64 string](https://www.base64encode.org/)

Expand Down Expand Up @@ -106,20 +105,20 @@ kubectl get ConfigMap -n entandokubectl edit ConfigMap/entando-operator-config -
```
Add the `YOUR-CA-CERT-SECRET` under the data property to refer to your secret, as shown here:

``` yaml
apiVersion: v1
data:
entando.ca.secret.name: YOUR-CA-CERT-SECRET
entando.ingress.class: nginx
entando.k8s.operator.image.pull.secrets: container-registry-secret
entando.k8s.operator.impose.limits: "true"
entando.requires.filesystem.group.override: "true"
entando.tls.secret.name: test-fire-tls-secret
kind: ConfigMap
metadata:
name: entando-operator-config
namespace: entando
```
``` yaml
apiVersion: v1
data:
entando.ca.secret.name: YOUR-CA-CERT-SECRET
entando.ingress.class: nginx
entando.k8s.operator.image.pull.secrets: container-registry-secret
entando.k8s.operator.impose.limits: "true"
entando.requires.filesystem.group.override: "true"
entando.tls.secret.name: test-fire-tls-secret
kind: ConfigMap
metadata:
name: entando-operator-config
namespace: entando
```

**Next Steps**
* [Install Microservices from a Private Image Registry](ms-private-images.md).
Expand Down
31 changes: 15 additions & 16 deletions vuepress/docs/v7.3/tutorials/curate/bundle-private-images.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ For microservices in a private image registry, follow the [install guide here](m
## Tutorial
### Step 1: Create the Registry Credentials
1. Create the registry JSON configuration using your registry and credentials on the port of your choice:
```
``` json
{
"auths": {
"YOUR-REGISTRY.com": {
Expand All @@ -25,7 +25,6 @@ For microservices in a private image registry, follow the [install guide here](m
}
}
}

```
2. [Convert the JSON configuration into a base64 string](https://www.base64encode.org/)

Expand Down Expand Up @@ -106,20 +105,20 @@ kubectl get ConfigMap -n entandokubectl edit ConfigMap/entando-operator-config -
```
Add the `YOUR-CA-CERT-SECRET` under the data property to refer to your secret, as shown here:

``` yaml
apiVersion: v1
data:
entando.ca.secret.name: YOUR-CA-CERT-SECRET
entando.ingress.class: nginx
entando.k8s.operator.image.pull.secrets: container-registry-secret
entando.k8s.operator.impose.limits: "true"
entando.requires.filesystem.group.override: "true"
entando.tls.secret.name: test-fire-tls-secret
kind: ConfigMap
metadata:
name: entando-operator-config
namespace: entando
```
``` yaml
apiVersion: v1
data:
entando.ca.secret.name: YOUR-CA-CERT-SECRET
entando.ingress.class: nginx
entando.k8s.operator.image.pull.secrets: container-registry-secret
entando.k8s.operator.impose.limits: "true"
entando.requires.filesystem.group.override: "true"
entando.tls.secret.name: test-fire-tls-secret
kind: ConfigMap
metadata:
name: entando-operator-config
namespace: entando
```

**Next Steps**
* [Install Microservices from a Private Image Registry](ms-private-images.md).
Expand Down
Loading