You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of #169408 we are adding the first very basic support to load Kibana static assets from a CDN. The translations files are still not implemented and are marked as future work.
On the Ops team side, once we have access into a CDN environment, we should analyse and implement a way for us to upload the assets into a CDN to be used on serverless environments.
For accomplish that task what John have done at #130916 should be a good place to start.
Wether we publish those assets at on-merge or in the promotion to QA quality gates we should make sure those published assets are either used in the QA serverless env FTR tests or that we do have a smoke test to validate we don't break this process at anytime.
The text was updated successfully, but these errors were encountered:
Closes#169427
Adds a new build step `createCdnAssets` that will create an archive
`kibana-<version>-cdn-assets.tar.gz` with static assets organized using
the request structure of the kibana client.
- By default CDN assets are created
- Adding the flag `node scripts/build --skip-cdn-assets` will skip
creation
- `ci:build-cdn-assets` can be used to create and upload the archive for
testing
Testing: see #169408. Builds are
available in the artifacts tab on the `Build Distribution` step.
1) Extract builds
2) ```
python3 -m http.server -b localhost -d kibana-8.12.0-SNAPSHOT-cdn-assets
8000
```
3) ```
echo 'server.cdn.url: http://localhost:8000' >>
kibana-8.12.0-SNAPSHOT/config/kibana.yml
```
4) ```
kibana-8.12.0-SNAPSHOT/bin/kibana
```
As part of #169408 we are adding the first very basic support to load Kibana static assets from a CDN. The translations files are still not implemented and are marked as future work.
On the Ops team side, once we have access into a CDN environment, we should analyse and implement a way for us to upload the assets into a CDN to be used on serverless environments.
For accomplish that task what John have done at #130916 should be a good place to start.
Wether we publish those assets at on-merge or in the promotion to QA quality gates we should make sure those published assets are either used in the QA serverless env FTR tests or that we do have a smoke test to validate we don't break this process at anytime.
The text was updated successfully, but these errors were encountered: