-
Notifications
You must be signed in to change notification settings - Fork 23
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.
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 446-Updates to CR page and remove Helm #487
Conversation
links failed because of new docs (Operator and env variable) not in this branch but already merged in main |
|
||
* Build and deploy the updated bundle. | ||
|
||
<!-- Supply the following parameters: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I put comment tags around sections and lines that should be removed but wasn't completely sure about. Hope that isn't too confusing.
@@ -61,7 +95,7 @@ operator.imagePullSecrets: [your-secret-name] | |||
<snip> | |||
``` | |||
|
|||
You can now generate the deployment yaml and deploy it to Kubernetes as usual. | |||
You can now generate the deployment yaml and deploy it to Kubernetes as usual. --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
another commented section to be removed
# Entando Custom Resources for Kubernetes | ||
|
||
## Objective | ||
|
||
This is an overview of Entando Kubernetes Custom Resources and their semantics. | ||
|
||
This is an overview of Entando Kubernetes Custom Resources and their semantics on the Entando Platform. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
semantics seems like a very odd and cryptic word choice
@@ -53,8 +59,10 @@ result in the Deployment of one or more Docker images, along with one or more Se | |||
|
|||
The Entando Operator itself is also implemented as a Docker Image. You can have a closer look at how it works in the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
image
@@ -149,7 +160,8 @@ spec: | |||
[globally configured TLS Secret](https://github.com/entando-k8s/entando-k8s-controller-coordinator/blob/master/charts/entando-k8s-controller-coordinator/README.md#tls) | |||
for the Operator is absent or has not been created with a wildcard hostname that supports this Keycloak instance's hostname. | |||
* `spec.replicas` - the number of replicas to be made available on the Deployment of this Keycloak Server. | |||
* `spec.resourceRequirements` - the minimum and maximum [resource allocations](#the-resourcerequirements-specification) for the Keycloak Server container. | |||
|
|||
* `spec.resourceRequirements` - the minimum and maximum [resource allocations](#the-resourcerequirements-specification) for the Keycloak Server container. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is the Keycloak Server a thing? server isn't capitalized i don't think
@@ -12,7 +12,7 @@ Microservices clustering that adds functionality to an Entando Application is di | |||
|
|||
To scale an Entando Application across multiple nodes, a storage class that supports a `ReadWriteMany` access policy must be created. There are a number of ways to accomplish this, inclusive of dedicated storage providers such as GlusterFS. Cloud Kubernetes providers also offer clustered storage options specific to their implementation, such as Google Cloud File in GKE or Azure Files in AKS. | |||
|
|||
Two different storage classes can be used for clustered vs non-clustered storage if the default class doesn't support `ReadWriteMany`. To achieve this, add the following properties to the operator config map in the Helm templates: | |||
Two different storage classes can be used for clustered vs non-clustered storage if the default class doesn't support `ReadWriteMany`. To achieve this, add the following properties to the operator Config Map: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
vs.
ConfigMap
|
||
You can achieve this by specifying some properties for the EntandoApp component present in the helm generated file. Look at [this](https://github.com/entando-k8s/entando-helm-quickstart) for more info. | ||
You can achieve this by specifying some properties for the EntandoApp component present in the entandoapp.yaml file. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
YAML files are backticked, right?
``` | ||
helm template quickstart ./ > my-clustered-app.yaml | ||
``` | ||
|
||
11. Add environment variables for your deployed Redis instance to `EntandoApp` in `my-clustered-app.yaml`. The variables to create are: | ||
11. Add environment variables to the `EntandoApp` in the outcome of the Helm template command generated above (`my-clustered-app.yaml`) for the Redis address and Redis password for your deployed Redis instance. The variables to create are: --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
super confusing run-on sentence. is the original not correct? like "Add address and password environment variables for your deployed Redis instance to EntandoApp
in my-clustered-app.yaml
, which is the outcome of the Helm template generation."
the command wasn't generated, right? the YAML file was generated ??
the EntandoApp
is misleading, like only one exists
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this section is commented out, to be deleted
@@ -191,7 +203,7 @@ spec: | |||
ingressPath: /entando-de-app | |||
environmentVariables: | |||
- name: REDIS_ADDRESS | |||
value: [your redis URI. For example redis://localhost:6379] | |||
value: YOUR redis URI. For example redis://localhost:6379 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Redis
what is a URI?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
||
## Prerequisites | ||
|
||
- An environment to install your Entando applicaiton | ||
- An environment to install your Entando application |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Application
5. Under `environmentVariables` you will need to provide database connection information for two Entando Server databases and one connection for the Entando Component Repository. Example connection information for each of those databases is provided below: | ||
2. Edit the EntandoApp and EntandoKeycloakServer custom resources. | ||
3. Set the value for `dbms` to `none` in both resources. | ||
4. Under `environmentVariables`, you will need to provide database connection information for two Entando Server databases and one connection for the Entando Component Repository. Example connection information for each of those databases is provided below: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Entando Server -> Entando server
and create the `keycloak-admin-secret` in the operator's namespace as specified in the | ||
[external Keycloak instance](../../tutorials/devops/external-id-management.md) tutorial. | ||
[external database tutorial](../../tutorials/devops/external-id-management.md). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was actually related to an external Keycloak.
@Lyd1aCla1r3 and @jyunmitch I applied most of the PR feedback but again we're getting into several untouched docs so let's just do the basic for review. |
``` | ||
|
||
#### Oracle | ||
``` | ||
XXX_URL: jdbc:oracle:{driver_type}:@//{DBMS_ADDRESS}:{DBMS_PORT}/{DBMS_SERVICE_NAME} | ||
XXX_CONNECTON_CHECKER: org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker | ||
XXX_EXCEPTION_SORTER: org.jboss.jca.adapters.jdbc.extensions.oracle.OracleExceptionSorter | ||
SPRING_JPA_DATABASE_PLATFORM: org.hibernate.dialect.Oracle | ||
SPRING_JPA_DATABASE_PLATFORM: org.hibernate.dialect.MySQLDialect |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix
@@ -191,7 +203,7 @@ spec: | |||
ingressPath: /entando-de-app | |||
environmentVariables: | |||
- name: REDIS_ADDRESS | |||
value: [your redis URI. For example redis://localhost:6379] | |||
value: YOUR redis URI. For example redis://localhost:6379 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
``` | ||
|
||
**The following example pertains to the EntandoApp only, not a complete deployment.** Utilize this as a reference to create your configuration in a complete deployment. | ||
11. Add environment variables to the `EntandoApp` defition to match your Redis instance. The variables to create are REDIS_ACTIVE, REDIS_ADDRESS (e.g. _redis://localhost:6379_), and REDIS_PASSWORD. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
was just about to approve, but was reading through and found typo: definition. Otherwise approved
@@ -51,10 +57,12 @@ Entando Custom Resource is created, updated or deleted, the Entando Operator wil | |||
that will translate that state change into a state change in the actual Kubernetes Cluster. Often, this will | |||
result in the Deployment of one or more Docker images, along with one or more Services, and sometimes an Ingress. We refer to the Docker Images that implement these run-to-completion Pods as Entando Kubernetes Controllers. | |||
|
|||
The Entando Operator itself is also implemented as a Docker Image. You can have a closer look at how it works in the | |||
The Entando Operator itself is also implemented as a Docker image. You can have a closer look at how it works in the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"have a closer look" sounds awkward. minor. sorry.
@@ -256,6 +260,8 @@ spec: | |||
* `spec.replicas` - the number of replicas to be made available on the Deployment of this Entando App. | |||
* `spec.resourceRequirements` - the minimum and maximum [resource allocation](#the-resourcerequirements-specification) for the Entando App Engine container. | |||
* `spec.ecrGitSshSecretName` - a secret containing a private key file named `rsa_id` that matches a public key configured in the Git server. | |||
* `spec.storageClass` - the name of the StorageClass to use for PersistentVolumeClaims created for this EntandoApp. For more information go to [Kubernetes explanation on Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
information -> information,
@@ -11,7 +11,8 @@ The tutorial below covers the basic steps to setup and validate a clustered inst | |||
In order to scale an Entando Application across multiple nodes, you must provide a storage class that supports | |||
a `ReadWriteMany` access policy. There are many ways to accomplish this, including using dedicated storage providers like GlusterFS. Cloud Kubernetes providers also offer clustered storage options specific to their implementation, such as Google Cloud File in GKE or Azure Files in AKS. | |||
|
|||
If your default class doesn't support `ReadWriteMany`, add the following operator properties to the ConfigMap of your Helm template to use two different storage classes for clustered vs non-clustered storage: | |||
|
|||
You can use two different storage classes for your clustered vs. non-clustered storage if your default class doesn't support `ReadWriteMany`. Add the following properties to your ConfigMap for the operator: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just fyi ConfigMap
and ConfigMap are both being used...
Updates to Custom Resources page and remove Helm mentions