-
Notifications
You must be signed in to change notification settings - Fork 133
[maintenance/master] 'elasticsearch' updated '5.6.14' -> '6.6.0' #361
[maintenance/master] 'elasticsearch' updated '5.6.14' -> '6.6.0' #361
Conversation
…0-r0' Signed-off-by: Bitnami Containers <containers@bitnami.com>
…0-r1' Signed-off-by: Bitnami Containers <containers@bitnami.com>
…0-r2' Signed-off-by: Bitnami Containers <containers@bitnami.com>
…0-r3' Signed-off-by: Bitnami Containers <containers@bitnami.com>
…0-r4' Signed-off-by: Bitnami Containers <containers@bitnami.com>
…0-r5' Signed-off-by: Bitnami Containers <containers@bitnami.com>
…0-r6' Signed-off-by: Bitnami Containers <containers@bitnami.com>
…0-r7' Signed-off-by: Bitnami Containers <containers@bitnami.com>
…0-r8' Signed-off-by: Bitnami Containers <containers@bitnami.com>
…0-r9' Signed-off-by: Bitnami Containers <containers@bitnami.com>
…0-r10' Signed-off-by: Bitnami Containers <containers@bitnami.com>
…0-r11' Signed-off-by: Bitnami Containers <containers@bitnami.com>
…0-r12' Signed-off-by: Bitnami Containers <containers@bitnami.com>
11b666c
to
7d23d80
Compare
@anguslees @falfaro upgrading to Kibana 6.0 requires the Kibana index to be migrated to the new format. I've added a BKPR v1.2 upgrade guide with the steps to perform the migration. Note: #374 should be merged after this PR as the elasticsearch and kibana versions should be in sync |
Minor comment on doc, rest lgtm. |
7d23d80
to
376a9b8
Compare
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.
It looks good, but I think we need to explain better the generated files, where to find them, etc.
|
||
Follow the [installation guide](install.md) to update the BKPR installer binary to the latest release of BKPR v1.2. | ||
|
||
### Step 2: Edit `kubeprod-manifest.jsonnet` |
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.
Where does this mean? Where is this supposed to be?
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.
If this was generated in the previous install, we should specify that, and explain where people would expect it.
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.
linked back to the workflow document for the upgrade instructions. The workflow document has other related information.
|
||
### Step 3: Perform the upgrade | ||
|
||
Re-run the `kubeprod install` command in the directory containing the existing `kubeprod-autogen.json` and updated `kubeprod-manifest.jsonnet` files. |
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.
Same as above
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.
linked back to the workflow document and added some more details about the kubeprod-manifest.jsonnet
file.
376a9b8
to
a9bc998
Compare
Kibana index needs to be reindexed in order to migrate to Kibana 6 Signed-off-by: Sameer Naik <sameer@bitnami.com>
a9bc998
to
b18d133
Compare
Thanks! |
399: [maintenance/master] 'elasticsearch' updated '5.6.14' -> '6.6.1' r=sameersbn a=bitnami-bot Merged updates from #361 Fixes #376 400: [maintenance/master] 'kibana' updated '5.6.14' -> '6.6.1' r=sameersbn a=bitnami-bot Co-authored-by: Bitnami Containers <containers@bitnami.com> Co-authored-by: Sameer Naik <sameer@bitnami.com>
Fixes #376