Elastic Cloud on Kubernetes 1.9.0
Breaking changes
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.
- Inherit resource requirements in init containers #4963
All init containers will inherit resource requirements from the main containers by default.
- Move to env vars based Fleet mode configuration #4889
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.
- Update your Agent resources such that environment variables are set for settings you'd like to override, for example:
...
spec:
deployment:
podTemplate:
spec:
containers:
- name: agent
env:
- name: KIBANA_FLEET_HOST
value: "https://kibana.example.com:443"
...
- Upgrade ECK to version
1.9.x
. - Remove any modification and references to
fleet-setup.yml
. As ECK1.9.x
uses environment variables to set the default config, the environment variables you've set in step 1. override the default values.
New features
Enhancements
- Add logging for call to ES #4958 (issue: #4935)
- Shorten the reconciliation loop duration if Elasticsearch is down #4938 (issues: #2939, #3496)
- Ignore ClusterIPs, and IPFamilyPolicy in services, and timestamp in license during reconciliation #4929
- Add operator license key check #4925
- Skip remote clusters reconciliation earlier if remote clusters are not configured #4924
- Refactor Elasticsearch HTTP error handling #4922 (issue: #4918)
- Verify supported Elasticsearch distribution during license reconciliation #4920
- Remove permissions not used by the operator #4823
Bug fixes
- Avoid updating the association status when no association #4986 (issue: #4985)
- Forcibly recreate Beat keystore #4942 (issues: #4527, #4926)
- Init. fs container: make cp more resilient #4888 (issue: #4877)
- Allow the upgrade of a single node cluster with yellow status #4787 (issue: #4625)