c31284e6db
Depends on #4033 ## Motivation If any job fails in the current GH Actions workflow, a re-run on the same commit SHA requires re-running *all* jobs--regardless if the job already passed in the previous run. This can be problematic when dealing with flakiness in the integration tests. If a test fails due to flakiness in `cloud_integration_tests`, all the unit tests, static checks, and `kind_integration_tests` are re-run which leads to lots of waiting and dealing with the possibility of flakiness in earlier jobs. With this change, individual workflows can now be re-run without triggering all other jobs to complete again first. ## Solution `workflow.yml` is now split into: - `static_checks.yml` - `unit_tests.yml` - `kind_integration.yml` - `cloud_integration.yml` ### Workflows `statc_checks.yml` performs checks related to dependencies, linting, and formatting. `unit_tests.yml` performs the Go and JS unit tests. `kind_integration.yml` builds the images (on Packet or the GH Action VM) and runs the integration tests on a KinD cluster. This workflow continues to run for **all** PRs and pushes to `master` and tags. `cloud_integration.yml` builds the images only on Packet. This is because forked repositories do not need to trigger this workflow. It then creates a unique GKE cluster and runs the integration tests on the cluster. ### The actual flow of work.. A forked repository or non-forked repository opening a PR triggers: - `static_checks` - `unit_tests` - `kind_integration_tests` These workflows all run in parallel and are invidivually re-runnable. A push to `master` or tags triggers: - `static_checks` - `unit_tests` - `kind_integration_tests` - `cloud_integration_tests` These workflows also all run in parallel, including the `docker_build` step of both integration test workflows. This has not conflicted in testing as it takes place on the same Packet host and just utilizes docker layer caching well. Signed-off-by: Kevin Leimkuhler <kevin@kleimkuhler.com> |
||
|---|---|---|
| .github | ||
| bin | ||
| charts | ||
| cli | ||
| cni-plugin | ||
| controller | ||
| grafana | ||
| pkg | ||
| proto | ||
| proxy-identity | ||
| test | ||
| testutil | ||
| web | ||
| .dockerignore | ||
| .editorconfig | ||
| .gcp.json.enc | ||
| .gitattributes | ||
| .gitignore | ||
| .golangci.yml | ||
| .proxy-version | ||
| ADOPTERS.md | ||
| BUILD.md | ||
| CHANGES.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| DCO | ||
| Dockerfile-base | ||
| Dockerfile-debug | ||
| Dockerfile-go-deps | ||
| Dockerfile-proxy | ||
| GOVERNANCE.md | ||
| LICENSE | ||
| MAINTAINERS.md | ||
| README.md | ||
| SECURITY_AUDIT.pdf | ||
| TEST.md | ||
| go.mod | ||
| go.sum | ||
| tools.go | ||
README.md
🎈 Welcome to Linkerd! 👋
Linkerd is a service mesh, designed to give platform-wide observability, reliability, and security without requiring configuration or code changes.
Linkerd is a Cloud Native Computing Foundation (CNCF) project.
Repo layout
This is the primary repo for the Linkerd 2.x line of development.
The complete list of Linkerd repos is:
- linkerd2: Main Linkerd 2.x repo, including control plane and CLI
- linkerd2-proxy: Linkerd 2.x data plane proxy
- linkerd2-proxy-api: Linkerd 2.x gRPC API bindings
- linkerd: Linkerd 1.x
- website: linkerd.io website (including docs for 1.x and 2.x)
Quickstart and documentation
You can run Linkerd on any Kubernetes 1.13+ cluster in a matter of seconds. See the Linkerd Getting Started Guide for how.
For more comprehensive documentation, start with the Linkerd docs. (The doc source code is available in the website repo.)
Working in this repo
BUILD.md includes general information on how to work in this repo.
We ❤️ pull requests! See CONTRIBUTING.md for info on
contributing changes.
Get involved
- Join Linkerd's user mailing list, developer mailing list, and announcements mailing list.
- Follow @linkerd on Twitter.
- Join the Linkerd Slack.
- Join us in the regular online community meetings!
Community meetings
We host regular online meetings for contributors, adopters, maintainers, and anyone else interested to connect in a synchronous fashion. These meetings take place the last Wednesday of the month at 9am Pacific / 4pm UTC.
We're a friendly group, so please feel free to join us!
Code of conduct
This project is for everyone. We ask that our users and contributors take a few minutes to review our code of conduct.
Security
Security Audit
A third party security audit was performed by Cure53. You can see the full report here.
License
Copyright 2019, Linkerd Authors. All rights reserved.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use these files except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.