Skip to content

[8.x] includes liberation fonts in dockerfile (#204368)#204699

Merged
kibanamachine merged 1 commit intoelastic:8.xfrom
kibanamachine:backport/8.x/pr-204368
Dec 18, 2024
Merged

[8.x] includes liberation fonts in dockerfile (#204368)#204699
kibanamachine merged 1 commit intoelastic:8.xfrom
kibanamachine:backport/8.x/pr-204368

Conversation

@kibanamachine
Copy link
Copy Markdown
Contributor

Backport

This will backport the following commits from main to 8.x:

Questions ?

Please refer to the Backport tool documentation

\r\n\r\nCo-authored-by: Elastic Machine ","sha":"87440cf335e59032c05c883d467d01a367aaa0cf","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-major","ci:cloud-deploy","ci:build-serverless-image","ci:build-docker-fips","Feature:Reporting:Framework"],"title":"includes liberation fonts in dockerfile","number":204368,"url":"https://github.com//pull/204368","mergeCommit":{"message":"includes liberation fonts in dockerfile (#204368)\n\n## Summary\r\n\r\nThis PR includes liberations fonts in the docker file for Kibana. \r\n\r\ninformed by https://github.com/elastic/sdh-kibana/issues/5097, we\r\npreviously used to package liberation fonts within Dockerfile but this\r\nwas removed in https://github.com//pull/183334, it's\r\nhowever required for reporting on linux especially that these fonts\r\naren't provided by default, resulting in not so optimal rendering of\r\nusers reports.\r\n\r\n\r\n\r\nCo-authored-by: Elastic Machine ","sha":"87440cf335e59032c05c883d467d01a367aaa0cf"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com//pull/204368","number":204368,"mergeCommit":{"message":"includes liberation fonts in dockerfile (#204368)\n\n## Summary\r\n\r\nThis PR includes liberations fonts in the docker file for Kibana. \r\n\r\ninformed by https://github.com/elastic/sdh-kibana/issues/5097, we\r\npreviously used to package liberation fonts within Dockerfile but this\r\nwas removed in https://github.com//pull/183334, it's\r\nhowever required for reporting on linux especially that these fonts\r\naren't provided by default, resulting in not so optimal rendering of\r\nusers reports.\r\n\r\n\r\n\r\nCo-authored-by: Elastic Machine ","sha":"87440cf335e59032c05c883d467d01a367aaa0cf"}}]}] BACKPORT-->

## Summary

This PR includes liberations fonts in the docker file for Kibana.

informed by elastic/sdh-kibana#5097, we
previously used to package liberation fonts within Dockerfile but this
was removed in elastic#183334, it's
however required for reporting on linux especially that these fonts
aren't provided by default, resulting in not so optimal rendering of
users reports.

<!--
### Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

### Identify risks

Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.

- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...

-->

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
(cherry picked from commit 87440cf)
@kibanamachine kibanamachine added the backport This PR is a backport of another PR label Dec 18, 2024
@kibanamachine kibanamachine enabled auto-merge (squash) December 18, 2024 09:19
@kibanamachine kibanamachine merged commit 3ad3d92 into elastic:8.x Dec 18, 2024
@elasticmachine
Copy link
Copy Markdown
Contributor

💚 Build Succeeded

Metrics [docs]

✅ unchanged

cc @eokoneyo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants