Published by kvalliyurnatt 5 months ago
Published by thbkrkr 7 months ago
Published by thbkrkr 7 months ago
type
keys in eck-beats chart #7523 (issue: #7487)Published by naemono 9 months ago
resourceStatuses
back into the status subresource section of the Stack Configuration Policy for backwards compatability #7500Published by naemono 9 months ago
docker.io/bash
for sleep container of max-map-count-setter Daemonset #7332Published by naemono 12 months ago
Published by pebrc about 1 year ago
Published by barkbay over 1 year ago
Warning
This release includes a hardened default security context for Elasticsearch containers. It is highly recommended to test against a staging environment before deploying to production.
elasticsearch-data
volumeMount configuration #6725 (issue: #6186)Published by thbkrkr over 1 year ago
Published by thbkrkr almost 2 years ago
Published by naemono almost 2 years ago
Published by pebrc almost 2 years ago
Published by david-kow about 2 years ago
Configure Elastic Agent host path volume to point to correct path #5890 (issue: #4428)
Fleet-managed Elastic Agents now default to use a hostPath
volume for storing their state. This will prevent more than one Pod from the same Elastic Agent Deployment to be deployed on the same Kubernetes node. For cases where this is desired, the volume type can be changed to an emptyDir
volume. Check the docs to learn more.
OOMKilled
" docs section #5836Published by barkbay over 2 years ago
status.ObservedGeneration
from metadata.Generation
:
Published by thbkrkr over 2 years ago
Published by naemono over 2 years ago
Published by pebrc over 2 years ago
IMPORTANT
Operator Lifecycle Manager (OLM) and OpenShift OperatorHub users that run with automatic upgrades enabled, are advised to set the set-default-security-context
operator flag explicitly before upgrading to ECK 2.0. If not set ECK can fail to auto-detect the correct security context configuration and Elasticsearch Pods may not be allowed to run.
Published by david-kow almost 3 years ago
This change will mitigate the Log4Shell vulnerability (CVE-2021-44228) in susceptible Elasticsearch clusters (below version 7.2
). ECK will prepend the -Dlog4j2.formatMsgNoLookups=true
JVM parameter to the environment variable ES_JAVA_OPTS
if it is not yet defined by the user. This triggers a rolling restart of all Pods of the affected Elasticsearch clusters to apply these changes.
Published by david-kow almost 3 years ago
IMPORTANT
For Operator Lifecycle Manager (OLM) and OpenShift OperatorHub users that run with automatic upgrades enabled, it is advised to set set-default-security-context
operator flag explicitly before next ECK release. Next version of ECK will introduce a change that could result in setting an invalid Pod Security Context to Elasticsearch Pods.
All init containers will inherit resource requirements from the main containers by default.
ECK operator will configure Elastic Agent in Fleet mode using environment variables instead of a configuration file. This method allows you to easily override the default settings. If the override is configured with any other method, an additional step is required before the operator upgrade.
...
spec:
deployment:
podTemplate:
spec:
containers:
- name: agent
env:
- name: KIBANA_FLEET_HOST
value: "https://kibana.example.com:443"
...
1.9.x
.fleet-setup.yml
. As ECK 1.9.x
uses environment variables to set the default config, the environment variables you've set in step 1. override the default values.