-
Notifications
You must be signed in to change notification settings - Fork 704
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge master into statefulset-refactoring #1358
Commits on Jul 19, 2019
-
Use the setvmmaxmapcount initcontainer by default in E2E tests (elast…
…ic#1300) Let's keep our default defaults :) The setting is disabled explicitly for E2E tests where we enable a restricted security context.
Configuration menu - View commit details
-
Copy full SHA for fff1526 - Browse repository at this point
Copy the full SHA fff1526View commit details -
Configuration menu - View commit details
-
Copy full SHA for e11e7b5 - Browse repository at this point
Copy the full SHA e11e7b5View commit details -
Allow license secret webhook to fail (elastic#1301)
Webhooks on core k8s objects are just too debilitating in case our webhook service fails. This sets the failure policy for the secret webhook to ignore to strike a balance between UX (immediate feedback) and keeping the users k8s cluster in a working state. Also we have an additional validation run on controller level so this does not allow circumventing our validation logic.
Configuration menu - View commit details
-
Copy full SHA for 156847e - Browse repository at this point
Copy the full SHA 156847eView commit details -
Revert "Use the setvmmaxmapcount initcontainer by default in E2E tests (
elastic#1300)" (elastic#1302) This reverts commit fff1526. This commit is breaking our E2E tests chain, which deploy a PodSecurityPolicy by default. Any privileged init container will not work. I'll open an issue for a longer-term fix to properly handle this.
Configuration menu - View commit details
-
Copy full SHA for 3098741 - Browse repository at this point
Copy the full SHA 3098741View commit details -
Update quickstart (elastic#1307)
* Update the name of the secret for the elastic user * Bump the Elastic Stack version from 7.1.0 to 7.2.0
Configuration menu - View commit details
-
Copy full SHA for 36f75f3 - Browse repository at this point
Copy the full SHA 36f75f3View commit details -
Change Kibana readiness endpoint to return a 200 OK (elastic#1309)
The previous endpoint returned an http code 302. While this is fine for Kubernetes, some derived systems like GCP LoadBalancers mimic the container readiness check for their own readiness check. Except GCP Loadbalancers only work with status 200. It's not up to us to adapt GCP LoadBalancers to K8s, but this is a fairly trivial fix.
Configuration menu - View commit details
-
Copy full SHA for f8448fc - Browse repository at this point
Copy the full SHA f8448fcView commit details
Commits on Jul 21, 2019
-
Fix pod_forwarder to support two part DNS names, adjust e2e http_clie…
…nt (elastic#1297) * Fix pod_forwarder to support two part DNS names, adjust e2e http_client url * Revert removing .svc in e2e http_client
Configuration menu - View commit details
-
Copy full SHA for 603b6d3 - Browse repository at this point
Copy the full SHA 603b6d3View commit details
Commits on Jul 22, 2019
-
[DOC] Resources management and volume claim template (elastic#1252)
* Add resources and persistent volume templates documentation
Configuration menu - View commit details
-
Copy full SHA for 8a19795 - Browse repository at this point
Copy the full SHA 8a19795View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9a2ac59 - Browse repository at this point
Copy the full SHA 9a2ac59View commit details -
Document PodDisruptionBudget section of the ES spec (elastic#1306)
* Document PodDisruptionBudget section of the ES spec I suspect this might slightly change in the feature depending on how we handle the readiness check, so I'm keeping this doc minimal for now: * what is a PDB, briefly (with a link) * default PDB we apply * how to set a different PDB * how to disable the default PDB
Configuration menu - View commit details
-
Copy full SHA for f47a425 - Browse repository at this point
Copy the full SHA f47a425View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1fdc257 - Browse repository at this point
Copy the full SHA 1fdc257View commit details -
Add release note generation tool (elastic#1314)
* no external dependencies * inspects PRs by version label * generates structured release notes in asciidoc grouped by type label
Configuration menu - View commit details
-
Copy full SHA for 133919a - Browse repository at this point
Copy the full SHA 133919aView commit details -
Configuration menu - View commit details
-
Copy full SHA for 571d678 - Browse repository at this point
Copy the full SHA 571d678View commit details -
Configuration menu - View commit details
-
Copy full SHA for e8e365f - Browse repository at this point
Copy the full SHA e8e365fView commit details -
* Update persistent storage section * Update kibana localhost url to use https * Update k8s resources names in accessing-services doc * Mention SSL browser warning * Fix bulleted list
Configuration menu - View commit details
-
Copy full SHA for 674c964 - Browse repository at this point
Copy the full SHA 674c964View commit details -
Add CI job for nightly builds (elastic#1248)
* Move version to a file * Add CI implementation * Update VERSION * Depend on another PR for moving out version from Makefile * Update Jenkinsfile
Configuration menu - View commit details
-
Copy full SHA for a1424a6 - Browse repository at this point
Copy the full SHA a1424a6View commit details -
Don't build and push operator image in bootstrap-gke (elastic#1332)
We don't need to do that anymore, since we don't use an init container based on the operator image.
Configuration menu - View commit details
-
Copy full SHA for ef7419c - Browse repository at this point
Copy the full SHA ef7419cView commit details
Commits on Jul 23, 2019
-
Configuration menu - View commit details
-
Copy full SHA for fbc38d3 - Browse repository at this point
Copy the full SHA fbc38d3View commit details -
Configuration menu - View commit details
-
Copy full SHA for b730e01 - Browse repository at this point
Copy the full SHA b730e01View commit details -
Configuration menu - View commit details
-
Copy full SHA for 8f0c556 - Browse repository at this point
Copy the full SHA 8f0c556View commit details -
Configuration menu - View commit details
-
Copy full SHA for 3855efa - Browse repository at this point
Copy the full SHA 3855efaView commit details -
Configuration menu - View commit details
-
Copy full SHA for 0319605 - Browse repository at this point
Copy the full SHA 0319605View commit details -
Fix docs build on PR job (elastic#1351)
* Fix docs build on PR job * Cleanup workspace before doing other steps
Configuration menu - View commit details
-
Copy full SHA for 878674f - Browse repository at this point
Copy the full SHA 878674fView commit details -
Configuration menu - View commit details
-
Copy full SHA for b00ac2e - Browse repository at this point
Copy the full SHA b00ac2eView commit details
Commits on Jul 24, 2019
-
Don't rely on buggy metaObject Kind (elastic#1324)
* Don't rely on buggy metaObject Kind A bug in our client implementation may clear the object's Kind on certain scenarios. See kubernetes-sigs/controller-runtime#406. Let's avoid that by fixing a constant Kind returned by a method call on the resource.
Configuration menu - View commit details
-
Copy full SHA for 51c4be8 - Browse repository at this point
Copy the full SHA 51c4be8View commit details -
Configuration menu - View commit details
-
Copy full SHA for 5275ada - Browse repository at this point
Copy the full SHA 5275adaView commit details