-
Notifications
You must be signed in to change notification settings - Fork 4
MLE-19770: README updates for GA release #60
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
MLE-19770: README updates for GA release #60
Conversation
|
Please add cleanup steps. (helm uninstall/make uninstall & kubectl delete) |
|
One more thing, if you check out the README for Helm Chart, you will find the section for creating secret to be used later and how to review credential from the secret. We might need that section for Operator as well. |
I didn't add that because we wanted to keep the readme short and have links to documentation for detailed procedure. |
…nup and prerequistes
Added clean up steps. |
config/samples/quick_start.yaml
Outdated
| app.kubernetes.io/managed-by: kustomize | ||
| app.kubernetes.io/created-by: marklogic-kubernetes-operator | ||
| name: single-node | ||
| namespace: default |
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.
Don't use the default namespace even for quick start.
README.md
Outdated
| ## Introduction | ||
|
|
||
| The MarkLogic Kubernetes Operator is a tool that allows you to deploy and manage MarkLogic clusters on Kubernetes. It provides a declarative way to define and manage MarkLogic resources such as clusters, databases, and forests. | ||
| The MarkLogic Operator for Kubernetes is an operator that allows you to deploy and manage MarkLogic clusters on Kubernetes. It provides a declarative way to define and manage MarkLogic resources. For detailed documentation, please refer [MarkLogic Operator for Kubernetes](https://). |
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 URL for the documentation when they are deployed will be https://docs.progress.com/bundle/marklogic-server-on-kubernetes
| GITHUB_TOKEN=<YOUR_GITHUB_TOKEN> | ||
| ``` | ||
| 2. Then add the private repo to Helm repository with the GITHUB_TOKEN: | ||
| [Helm](https://helm.sh/docs/intro/install/) v3.0.0 or later and [Kubectl](https://kubernetes.io/docs/tasks/tools/) v1.30 or same as your Kubernetes version must be installed locally in order to use MarkLogic operator helm chart. |
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.
@barkhachoithani are you trying to say the Kubectl version number can be v1.30 or the version number should match the Kubernetes version number? @rwinieski does this need to be specified here or elsewhere in the doc? https://progress-dev.zoominsoftware.io/bundle/marklogic-server-on-kubernetes-2-feature-peter-edits/page/topics/set-up-the-required-tools.html
| 2. Then add the private repo to Helm repository with the GITHUB_TOKEN: | ||
| [Helm](https://helm.sh/docs/intro/install/) v3.0.0 or later and [Kubectl](https://kubernetes.io/docs/tasks/tools/) v1.30 or same as your Kubernetes version must be installed locally in order to use MarkLogic operator helm chart. | ||
|
|
||
| ### Kubernetes Version |
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.
@rwinieski i assume this should also be specified in the operator docs ? https://progress-dev.zoominsoftware.io/bundle/marklogic-server-on-kubernetes-2-feature-MLE-16694_Operator-GA-Doc
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.
Yes @plangleyprogress it will be.
It is more a Kubernetes best practicies the kubernetes client version should be aligned with the kubernetes server version.
README.md
Outdated
| ``` | ||
| #### Access HA Proxy | ||
| The HAProxy can be accessed from a service with the name of marklogic-haproxy. | ||
| 1. Run the below command to fetch all of the secret names: |
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.
@barkhachoithani I would just say Run this command to fetch all of the secret names:
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.
udpated the step.
README.md
Outdated
| service: | ||
| type: LoadBalancer | ||
| ``` | ||
| 2. Using the secret name from step 1 to get MarkLogic admin credentials, retrieve the values using the following commands: |
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.
@barkhachoithani I think you are saying "To return the MarkLogic admin credentials, use this command:"
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 would prefer retrieve the MarkLogic admin credentials instead of return. Also these steps are same as what we already have in helm chart readme: https://github.com/marklogic/marklogic-kubernetes?tab=readme-ov-file#installing-marklogic-helm-chart
README.md
Outdated
| + Wildcard Certificate - A single wildcard certificate can be used for all hosts within a cluster. | ||
| kubectl get secret node-admin -o jsonpath='{.data.wallet-password}' | base64 --decode | ||
| ``` | ||
| Please refer [Official Documentation]() for more sample manifests with different configurations to deploy MarkLogic cluster inside a Kubernetes cluster. |
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.
@barkhachoithani This should say something like "For additional manifests for deploying a MarkLogic cluster inside a Kubernetes cluster, see MarkLogic Server on Kubernetes
. But, is there a specific page you want to point to? It doesnt make sense to just point to a generic page, in my opinion.
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.
yes definitely, pointing a specific page in docs would be great. So here we need to point to the page where sample manifests are defined.
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.
Added link to manifests in the docs.
| 2. Then add the private repo to Helm repository with the GITHUB_TOKEN: | ||
| [Helm](https://helm.sh/docs/intro/install/) v3.0.0 or later and [Kubectl](https://kubernetes.io/docs/tasks/tools/) v1.30 or same as your Kubernetes version must be installed locally in order to use MarkLogic operator helm chart. | ||
|
|
||
| ### Kubernetes Version |
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.
Yes @plangleyprogress it will be.
It is more a Kubernetes best practicies the kubernetes client version should be aligned with the kubernetes server version.
README.md
Outdated
| ```shell | ||
| kubectl get secrets | ||
| ``` | ||
| The MarkLogic admin secret name will be in the format `<marklogicGroup-name>-admin`. For example if markLogicGroup name is `node`, the secret name would be `node-admin`. |
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.
We've just change the implementation to use one secret. Please change this line accordingly.
plangleyprogress
left a comment
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.
comments addeed
README.md
Outdated
| ## Introduction | ||
|
|
||
| The MarkLogic Kubernetes Operator is a tool that allows you to deploy and manage MarkLogic clusters on Kubernetes. It provides a declarative way to define and manage MarkLogic resources such as clusters, databases, and forests. | ||
| The MarkLogic Operator for Kubernetes is an operator that allows you to deploy and manage MarkLogic clusters on Kubernetes. It provides a declarative way to define and manage MarkLogic resources. For detailed documentation, please refer [MarkLogic Operator for Kubernetes](https://docs.progress.com/bundle/marklogic-server-on-kubernetes). |
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.
Should be "please refer to"
| The MarkLogic Kubernetes Operator is a tool that allows you to deploy and manage MarkLogic clusters on Kubernetes. It provides a declarative way to define and manage MarkLogic resources such as clusters, databases, and forests. | ||
| The MarkLogic Operator for Kubernetes is an operator that allows you to deploy and manage MarkLogic clusters on Kubernetes. It provides a declarative way to define and manage MarkLogic resources. For detailed documentation, please refer [MarkLogic Operator for Kubernetes](https://docs.progress.com/bundle/marklogic-server-on-kubernetes). | ||
|
|
||
| ## Code Structure |
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 word "contains" should be lower case in all uses unless it is after a period.
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 would also make this a bulleted list
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 line is not part of new README.
README.md
Outdated
| ``` | ||
| 4. Check the Operator Pod and make sure it is in Running state: | ||
|
|
||
| 3. Make sure the marklogic operator pod is running: |
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.
Capitalize MarkLogic Operator Pod
| ``` | ||
|
|
||
| ### Run Operator locally | ||
| After checking out the source code, you can run the MarkLogic Operator locally by following these steps: |
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.
After checking out the source code, you can run the MarkLogic Operator locally: (Strike "following these steps)
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 line is not part of new README.
| ``` | ||
| Once the installation is complete and the pod is in a running state, the MarkLogic admin UI can be accessed using the port-forwarding command as below: | ||
|
|
||
| ### Deploy Operator locally |
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.
strike "by following these steps"
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 line is not part of new README.
README.md
Outdated
| ```shell | ||
| kubectl get secrets | ||
| ``` | ||
| The MarkLogic admin secret name will be in the format `<marklogicGroup-name>-admin`. For example if markLogicGroup name is `node`, the secret name would be `node-admin`. |
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 MarkLogic admin secret name will be in the format `<marklogicGroup-name>-admin`. For example if markLogicGroup name is `node`, the secret name would be `node-admin`. | |
| The MarkLogic admin secret name will be in the format `<marklogicGroup-name>-admin`. For example, if the markLogicGroup name is `node`, the secret name is `node-admin`. |
README.md
Outdated
|
|
||
| ### Configure HAProxy Load Balancer | ||
| HAProxy is provided as a load balancer configured to support cookie-based session affinity and multi-statement transactions. These configurations are needed by some MarkLogic client applications, like mlcp. HAProxy is recommended for production workloads. | ||
| 2. Using the secret name from step 1 to get MarkLogic admin credentials, retrieve the values using the following commands: |
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.
| 2. Using the secret name from step 1 to get MarkLogic admin credentials, retrieve the values using the following commands: | |
| 2. Using the secret name from step 1, retrieve the MarkLogic admin credentials using these commands: |
README.md
Outdated
| tls: | ||
| enableOnDefaultAppServers: true | ||
| #### Cleaning up MarkLogic Cluster | ||
| Use following steps to delete MarkLogic cluster and other resources created from the manifests used in the above [step](#install-marklogic-cluster). |
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.
| Use following steps to delete MarkLogic cluster and other resources created from the manifests used in the above [step](#install-marklogic-cluster). | |
| Use these steps to delete MarkLogic clusters and other resources created from the manifests used in the [step](#install-marklogic-cluster). |
README.md
Outdated
| - "marklogic-1-cert" | ||
| caSecretName: "ca-cert" | ||
| #### Deleting Helm chart | ||
| Use following steps to delete MarkLogic Operator Helm chart. |
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.
| Use following steps to delete MarkLogic Operator Helm chart. | |
| Use these steps to delete MarkLogic Operator Helm chart. |
README.md
Outdated
|
|
||
| ## Known Issues and Limitations | ||
|
|
||
| 1. The latest released version of fluent/fluent-bit:3.2.5 has known high and critical security vulnerabilities. If you decide to enable the log collection feature, choose and deploy the fluent-bit or an alternate image with no vulnerabilities as per your requirements. |
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.
| 1. The latest released version of fluent/fluent-bit:3.2.5 has known high and critical security vulnerabilities. If you decide to enable the log collection feature, choose and deploy the fluent-bit or an alternate image with no vulnerabilities as per your requirements. | |
| 1. The latest released version of fluent/fluent-bit:3.2.5 has high and critical security vulnerabilities. If you decide to enable the log collection feature, choose and deploy the fluent-bit or an alternate image with no vulnerabilities as per your requirements. |
plangleyprogress
left a comment
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.
looks good
Please note there will be further changes in the README related to name, repo name, links to helm repo url and official documentation.