Merge master into statefulset-refactoring #1439
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ic#1300) Let's keep our default defaults :) The setting is disabled explicitly for E2E tests where we enable a restricted security context.
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.
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.
* Update the name of the secret for the elastic user * Bump the Elastic Stack version from 7.1.0 to 7.2.0
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.
…nt (elastic#1297) * Fix pod_forwarder to support two part DNS names, adjust e2e http_client url * Revert removing .svc in e2e http_client
* Add resources and persistent volume templates documentation
* 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
* no external dependencies * inspects PRs by version label * generates structured release notes in asciidoc grouped by type label
* 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
* Move version to a file * Add CI implementation * Update VERSION * Depend on another PR for moving out version from Makefile * Update Jenkinsfile
We don't need to do that anymore, since we don't use an init container based on the operator image.
* Fix docs build on PR job * Cleanup workspace before doing other steps
Co-Authored-By: Anya Sabo <1638148+anyasabo@users.noreply.github.com>
* 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.
* Add troubleshooting docs This docs should guide users into troubleshooting their failing deployment: * get resources details * get ES logs * get ECK logs * enable debug-level logs * pause controllers * get events * exec into containers * ask for help * Improvements from PR review * Wording improvements
* Pass proper flags during operator build * Fix CI * Update Jenkinsfile
Editing - Deploying ECK on OpenShift
Doc Reorg + titles alignment
Renaming title - Troubleshooting
Editing - Deploying ECK on Openshift
Editing - Accessing Elastic Stack services
Editing - Managing compute resources
Editing - Running ES on ECK
Editing - Running APM Server on ECK
Editing Snapshots + add back to index
…c#1414) The default storage class with GKE does not have WaitForFirstConsumer set by default. This means PVs get bound before a pod is scheduled in its zone, which could lead to all nodes of a cluster being scheduled on the same host. This happens when all the PVs have been randomly created with the same node affinity (same zone => same host). As a quick fix, we will use a custom default storage class with WaitForFirstConsumer for all the E2E tests.
* adds a test to exercise the custom config mechanism via volume/volume mount * uses custom synonyms as the example * adds a generic request method to the ES client
…astic#1429) The E2E tests are run in a k8s cluster configured with a Pod Security Policy. This forces to set up a Security Context in the Pod template of any Elastic custom resources in the E2E tests. Normally this Security Context is set through `WithESMasterDataNodes` but in this test, a custom Pod template defined just after overrides and cancels it. Thus `WithRestrictedSecurityContext` is called at the end to restore the cancelled definition of the Security Context.
* Update Openshift documentation with APM workaround
* Update statefulset ADR with recent decisions * Update associations ADR with recent outcomes * Update TLS certs ADR with recent outcomes * Update sidecar health ADR with recent outcomes * Update volume management ADR with recent outcomes
elastic#1364) Refactors the E2E tests and replaces the test setup scripts with a test runner written in Go. The new test runner allows isolating tests between each run by generating a unique name for the test run and creating all resources prefixed with that name.
|
jenkins please test this |
|
Jenkins test this please |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixing merge conflicts in the way.