-
Notifications
You must be signed in to change notification settings - Fork 204
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
add .Values.oap.initEs to work with ES initial #88
add .Values.oap.initEs to work with ES initial #88
Conversation
README.md
Outdated
@@ -19,6 +19,7 @@ There are required values that you must set explicitly when deploying SkyWalking | |||
| ---- | ----------- | ------- | | |||
| `oap.image.tag` | the OAP docker image tag | `9.1.0` | | |||
| `oap.storageType` | the storage type of the OAP | `elasticsearch`, `postgresql`, etc. | | |||
| `oap.initEs` | need to initial ES | `true`, `false` | |
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.
Please use ElasticSearch rather than a short term.
Besides docs update, you need to fix codes. |
My commit already included code change. I provied one argument to control whether the EleasticSearch storage need to be initialized. User can setup .Values.oap.initEs to false when they just want to change the image tag to another one like us. |
But your codes can't pass the CI which really run this helm on k8s. |
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.
LGTM
Try to solve this issue apache/skywalking#9290. It will provide the capability to helm upgrade the docker image tag or others after first helm install.