Tags: knechtionscoding/cloud-on-k8s
Tags
Updating versions to 2.3 (elastic#5742) * Updating versions to 2.3 * Update operatorhub config
Release notes and highlights for 2.1.0 (elastic#5427) (elastic#5444) * Adding release notes, and highlights for 2.1.0 release * Add missing float to enhancements section. * Adding missing 5331 enhancement. Renaming some pull request's titles Re-wording Elasticsearch Status subresource description. Moving predicate changes to bottom of highlights, and noting that it's dangerous. * avoid via in docs/release-notes/2.1.0.asciidoc Co-authored-by: Arianna Laudazzi <[email protected]> * capitalize HTTP in docs/release-notes/2.1.0.asciidoc Co-authored-by: Arianna Laudazzi <[email protected]> * Replace See with Check in docs/release-notes/highlights-2.1.0.asciidoc Co-authored-by: Arianna Laudazzi <[email protected]> * Stop using 2 spaces after period in docs/release-notes/highlights-2.1.0.asciidoc Co-authored-by: Arianna Laudazzi <[email protected]> * 1 Space after period docs/release-notes/highlights-2.1.0.asciidoc Co-authored-by: Arianna Laudazzi <[email protected]> * Suggestions in docs/release-notes/highlights-2.1.0.asciidoc Co-authored-by: Arianna Laudazzi <[email protected]> * Add 2 new breaking issues/PRs to 2.1.0 release notes. * Update risk language in docs/release-notes/highlights-2.1.0.asciidoc Co-authored-by: Peter Brachwitz <[email protected]> * Update webhook issue/bug fix description. Modify the sub-resource status description. * Add golang version update to release notes. * Remove mention of CVE * Update docs/release-notes/2.1.0.asciidoc Co-authored-by: Thibault Richard <[email protected]> Co-authored-by: Arianna Laudazzi <[email protected]> Co-authored-by: Peter Brachwitz <[email protected]> Co-authored-by: Thibault Richard <[email protected]> Co-authored-by: Arianna Laudazzi <[email protected]> Co-authored-by: Peter Brachwitz <[email protected]> Co-authored-by: Thibault Richard <[email protected]>
Fix Stack Monitoring with custom certificate without CA (elastic#5310) ( elastic#5319) Stack Monitoring incorrectly assumed that if the monitored Elastic resource has TLS enabled, there is a CA to configure in the input section of the Metricbeat config. This overlooked that you can have a certificate issued by a well-known CA, so you don't always provide a CA when TLS is enabled. This is fixed by differentiating between isSSL/isTLS and HasCA.
Add 1.9.1 release notes (elastic#5174) (elastic#5179) * Add 1.9.1 release notes * Also regenerate 1.9.0 release notes * Fix bad link * Add mitigation description * Update docs/release-notes/1.9.1.asciidoc Co-authored-by: Thibault Richard <[email protected]> Co-authored-by: Thibault Richard <[email protected]> Co-authored-by: Thibault Richard <[email protected]>
[1.9] Stop using deprecated xpack.monitoring.* settings (elastic#5136) ( elastic#5137) Completely remove the `xpack.monitoring.*` settings as they were never needed for stack monitoring.
Fix Agent volumes when an association has no CA (elastic#4833) (elast… …ic#4834) This commit fixes an issue that occurs if you associate an Agent with a Kibana without TLS. In this case, the association Agent<->Kibana does not have a CA and this breaks the volumeMounts of the Agent container because we returned instead of continuing to populate the slice of volumes.
Release notes and highlights for 1.7.1 (elastic#4782) (elastic#4783)
Add Stack Monitoring usage reporting (elastic#4708) (elastic#4711)
Report EnterpriseSearch memory usage (elastic#4499) (elastic#4503)
PreviousNext