diff --git a/ADOPTERS.md b/ADOPTERS.md index 291d3fa..b731c00 100644 --- a/ADOPTERS.md +++ b/ADOPTERS.md @@ -81,7 +81,7 @@ Users * N: Giant Swarm L: https://www.giantswarm.io/blog/time-to-catch-a-new-train-flatcar-linux - D: Giant Swarm uses Flatcar within their Kubernetes Distribution. Flatcar is used on all providers (Azure, AWS, Google, OpenStack and Vmware). Giant Swarm manages 100s of clusters with 1000s of nodes running on Flatcar across the planet. + D: Giant Swarm uses Flatcar within their Kubernetes Distribution. Flatcar is used on all providers (Azure, AWS, Google, OpenStack and VMware). Giant Swarm manages 100s of clusters with 1000s of nodes running on Flatcar across the planet. * N: Hedgehog D: Flatcar is the OS for the control node in our product. We like the air-gap deployment model and how easy it is to stand up a Kubernetes cluster diff --git a/CIS/level1-remediation_notes-2020-12-08.md b/CIS/level1-remediation_notes-2020-12-08.md index 9b2f304..187d09d 100644 --- a/CIS/level1-remediation_notes-2020-12-08.md +++ b/CIS/level1-remediation_notes-2020-12-08.md @@ -287,7 +287,7 @@ ENTRYPOINT [ "rsyslogd", "-n" ] # rsyslog.conf # # if you experience problems, check: -# http://www.rsyslog.com/troubleshoot +# https://www.rsyslog.com/doc/ $FileCreateMode 0640 diff --git a/attic/community-meetings/2021-05-11.md b/attic/community-meetings/2021-05-11.md index d0732d7..805ada9 100644 --- a/attic/community-meetings/2021-05-11.md +++ b/attic/community-meetings/2021-05-11.md @@ -33,7 +33,7 @@ The meeting largely followed the [slide deck](2021-05-11-slides.pdf). After the - “[...] we want to assure the Flatcar community that Microsoft and the Kinvolk team will continue to collaborate with the larger Flatcar community on the evolution of Flatcar Container Linux.” - Brendan Burns, Microsoft - “This will not be a replay of the movie you’ve seen before. In fact, we and Microsoft are committed to doubling down on the Flatcar community: we want to expand the universe of partners, contributors, and users, to ensure a vibrant, successful and sustainable long-term future for Flatcar as a truly open, community-driven project.” - Chris Kühl, Kinvolk 3. Thilo introduces monthly community calls and the new community focus of the Flatcar project, overcoming and leaving behind its single vendor past. -4. Marga introduces the [interop matrix](../interop-matrix.md) as a means to track Flatcar's support of runtime environments (clouds, on premise, etc.). +4. Marga introduces the [interop matrix](../../interop-matrix.md) as a means to track Flatcar's support of runtime environments (clouds, on premise, etc.). - Some environments, while supported, do not currently have an owner. - The project aims to have community owners who operate workloads / clusters in the respective environments, in the long term. 5. Andy elaborates on Flatcar's core philosophy and shares details on stabilisation process and on release cadence. @@ -47,12 +47,12 @@ The meeting largely followed the [slide deck](2021-05-11-slides.pdf). After the - Alpha release removes `rkt` and `kubelet-wrapper`. The changes will transition to Beta in June, and to Stable in July. - Upcoming May 19th releases will ship a new major Alpha (2879.0.0) and patch level updates to Beta, Stable, and LTS. 7. Dongsu provide an overview of ClusterAPI, and elaborates on our work to add Flatcar support to CAPI. - - CAPI utilises a management cluster to deploy workload clusters on a variety of inrastructure providers. + - CAPI utilises a management cluster to deploy workload clusters on a variety of infrastructure providers. - Adding OS support for providers requires a separate implementation for each; there is no unified standard for OS config. - OS images are provided via the ClusterAPI Image Builder project. - Workload clusters are provisioned via the ClusterAPI Bootstrap provider. - Current Flatcar status: - - QEmu and AWS OS images supported for Flatcar in Image builder. + - QEMU and AWS OS images supported for Flatcar in Image builder. - Bootstrap (kubeadm) Ignition support added to enable Flatcar OS config. - AWS provider Ignition support added to enable Flatcar OS config. - Future plans: diff --git a/attic/community-meetings/2021-09-14.md b/attic/community-meetings/2021-09-14.md index 627c2ff..3084e5c 100644 --- a/attic/community-meetings/2021-09-14.md +++ b/attic/community-meetings/2021-09-14.md @@ -7,14 +7,14 @@ - Brief intro / check-in of all participants in the Zoom call. Please introduce yourself and share what brings you here today. ## News -- We will discuss news and happenings in the Flatcar world, including our move out of the Kinvolk github org / website back into our own, features coming to the Flatcar community release images, and the results of our recent user survey. +- We will discuss news and happenings in the Flatcar world, including our move out of the Kinvolk GitHub org / website back into our own, features coming to the Flatcar community release images, and the results of our recent user survey. ## Spotlight: Equinix Metal's use of Flatcar Container Linux - Andy Holtzmann [@andy-v-h](https://github.com/andy-v-h) gives an introduction on EM's use of Flatcar. ## Status update: ARM64 - Progress made, remaining items, and next steps. -- Ed Vielmetti [@vielmetti](https://github.com/vielmetti) shares information on the "Works on ARM" project at Equinix Metal, inclunding hardware available today and in the near future. +- Ed Vielmetti [@vielmetti](https://github.com/vielmetti) shares information on the "Works on ARM" project at Equinix Metal, including hardware available today and in the near future. ## Releases review & planning (updated section!) - We'll wrap up changes for the upcoming release (week of September 20) and will plan items we aim to integrate for the release after that (week of October 4th). diff --git a/attic/community-meetings/README.md b/attic/community-meetings/README.md index 320d1fb..23b1cce 100644 --- a/attic/community-meetings/README.md +++ b/attic/community-meetings/README.md @@ -1,7 +1,7 @@ # Old-style community meeting agendas and presentation slides -Community meeting planning / agendas has moved to [Github discussions](../../../../discussions/categories/community-meeting-agenda) +Community meeting planning / agendas have moved to [GitHub discussions](../../../../discussions/categories/community-meeting-agenda) -This section in the attic contains agenda markdown files of "old style" Flatcar community calls where the agenda was agreed on in a PR instead of a github discussion. +This section in the attic contains agenda markdown files of "old style" Flatcar community calls where the agenda was agreed on in a PR instead of a GitHub discussion. Also archived here are slide decks used in these meetings. diff --git a/governance.md b/governance.md index 6718750..ede828b 100644 --- a/governance.md +++ b/governance.md @@ -166,8 +166,8 @@ with the CNCF Code of Conduct Committee in resolving it. ## Security Response Team The Maintainers will appoint a Security Response Team to handle security reports. -This committee is a sub-set of the Maintainer Council with full access to undisclosed security issues tracked by the project. -Members of the Security Response team as well as respective access permissions to sensitive data are administrated via membership in the [Flatcar Github organisation's Security team](https://github.com/orgs/flatcar/teams/flatcar-security-team). +This committee is a subset of the Maintainer Council with full access to undisclosed security issues tracked by the project. +Members of the Security Response Team as well as respective access permissions to sensitive data are administered via membership in the [Flatcar GitHub organisation's Security team](https://github.com/orgs/flatcar/teams/flatcar-security-team). The Maintainers will review who is assigned to this at least once a year. The Security Response Team is responsible for handling all reports of security diff --git a/interop-matrix.md b/interop-matrix.md index 556b728..550aa61 100644 --- a/interop-matrix.md +++ b/interop-matrix.md @@ -12,15 +12,15 @@ Please propose ownership by filing a PR for this document. | EC2 | Partial | X | X | @flatcar/flatcar-maintainers | | IAM 2.0 support missing | | Azure | X | X | X | @flatcar/flatcar-maintainers | | | | GCE | X | X | X | @flatcar/flatcar-maintainers | | | -| Digital Ocean (VMs) | X | X | X | @flatcar/flatcar-maintainers | | | +| DigitalOcean (VMs) | X | X | X | @flatcar/flatcar-maintainers | | | | Equinix Metal | X | X | X | @flatcar/flatcar-maintainers | | | -| ESXi / vSphere | X | X | X | @flatcar/flatcar-maintainers | | | +| VMware ESXi / VMware vSphere | X | X | X | @flatcar/flatcar-maintainers | | | | Hetzner Cloud | | X | | [no owner] | | | | Vultr VPS | | X | | [no owner] | | | -| Cloudscale | | X | | [no owner] | | | +| cloudscale.ch | | X | | [no owner] | | | | Oracle Cloud | | X | | [no owner] | | Bring-your-own-image on OCI VMs; install via Ubuntu on OCI bare metal | | Tencent | | | | [no owner] | | | -| AliCloud | | | | [no owner] | | | +| Alibaba Cloud | | | | [no owner] | | | | Yandex | | | | [no owner] | | | | Brightbox | X | X | X | @flatcar/flatcar-maintainers | | | @@ -31,10 +31,10 @@ Please propose ownership by filing a PR for this document. | Azure Stack | | w/ caveat | | [no owner] | | controller node not supported on Flatcar (cloud-init feature missing) | | Tinkerbell | | X | | [no owner] | | | | Rancher (VMs) | | X | | [no owner] | | | -| QEmu / KVM backed | X | X | X | @flatcar/flatcar-maintainers | | | +| QEMU / KVM backed | X | X | X | @flatcar/flatcar-maintainers | | | | OpenStack | X | X | X | @flatcar/flatcar-maintainers | | | | VirtualBox | | X | | [no owner] | | | -| Vagrant | | X | | [no owner] | | Isn't this plain qemu/kvm? | +| Vagrant | | X | | [no owner] | | Isn't this plain QEMU/KVM? | ## Managed Kubernetes @@ -61,12 +61,12 @@ Please propose ownership by filing a PR for this document. | Environment | Full-Feature (release blocker) | Works | Tested (CI) | Owner | Reference (e.g. GH issue) | Notes | |-------------|--------------------------------|-------|-------------|-------|---------------------------|-------| | AKS Engine | | X | | [no owner] | | https://kinvolk.io/blog/2020/12/aks-engine-on-flatcar | -| Rancher (rke) | | X | | [no owner] | | | -| Rancher (rke2) | | | | [no owner] | | | -| Tanzu KG | | X | | [no owner] | | | +| Rancher (RKE) | | X | | [no owner] | | | +| Rancher (RKE2) | | | | [no owner] | | | +| Tanzu Kubernetes Grid (TKG) | | X | | [no owner] | | | | K3s | | X | | [no owner] | | | -| EKS-Distro | | X | | [no owner] | | | -| KOPS | | X | | upstream | | | +| Amazon EKS Distro | | X | | [no owner] | | | +| kOps | | X | | Upstream | | | | Kubermatic | | X | | [no owner] | | | | Gardener | | X | | [no owner] | | |