diff --git a/.github/workflows/bulwark-gitleaks-pr-validation.yaml b/.github/workflows/bulwark-gitleaks-pr-validation.yaml new file mode 100644 index 0000000000..bc8b8a00f5 --- /dev/null +++ b/.github/workflows/bulwark-gitleaks-pr-validation.yaml @@ -0,0 +1,36 @@ +name: BulwarkGitLeaks +on: [pull_request] + +concurrency: + group: gitleaks-${{ github.ref }} + cancel-in-progress: true + +jobs: + gitleaks-scan: + runs-on: ubuntu-latest + container: + image: gcr.io/spectro-dev-public/bulwark/gitleaks:latest + env: + REPO: ${{ github.event.repository.name }} + GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} + GITLEAKS_CONFIG: config.toml + steps: + + - name: run-bulwark-gitleaks-scan + shell: sh + env: + BRANCH: ${{ github.head_ref || github.ref_name }} + run: /workspace/bulwark -name CodeSASTGitLeaks -target $REPO -tags "branch:$BRANCH,options:--log-opts origin..HEAD" + + - name: check-result + shell: sh + run: | + resultPath=./$REPO/gitleaks.json + cat $resultPath | grep -v \"Match\"\: | grep -v \"Secret\"\: + total_failed_tests=`cat $resultPath | grep \"Fingerprint\"\: | wc -l` + if [ "$total_failed_tests" -gt 0 ]; then + echo "GitLeaks validation check failed with above findings..." + exit 1 + else + echo "GitLeaks validation check passed" + fi \ No newline at end of file diff --git a/LICENSE b/LICENSE deleted file mode 100644 index 8dada3edaf..0000000000 --- a/LICENSE +++ /dev/null @@ -1,201 +0,0 @@ - Apache License - Version 2.0, January 2004 - http://www.apache.org/licenses/ - - TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION - - 1. Definitions. - - "License" shall mean the terms and conditions for use, reproduction, - and distribution as defined by Sections 1 through 9 of this document. - - "Licensor" shall mean the copyright owner or entity authorized by - the copyright owner that is granting the License. - - "Legal Entity" shall mean the union of the acting entity and all - other entities that control, are controlled by, or are under common - control with that entity. For the purposes of this definition, - "control" means (i) the power, direct or indirect, to cause the - direction or management of such entity, whether by contract or - otherwise, or (ii) ownership of fifty percent (50%) or more of the - outstanding shares, or (iii) beneficial ownership of such entity. - - "You" (or "Your") shall mean an individual or Legal Entity - exercising permissions granted by this License. - - "Source" form shall mean the preferred form for making modifications, - including but not limited to software source code, documentation - source, and configuration files. - - "Object" form shall mean any form resulting from mechanical - transformation or translation of a Source form, including but - not limited to compiled object code, generated documentation, - and conversions to other media types. - - "Work" shall mean the work of authorship, whether in Source or - Object form, made available under the License, as indicated by a - copyright notice that is included in or attached to the work - (an example is provided in the Appendix below). - - "Derivative Works" shall mean any work, whether in Source or Object - form, that is based on (or derived from) the Work and for which the - editorial revisions, annotations, elaborations, or other modifications - represent, as a whole, an original work of authorship. For the purposes - of this License, Derivative Works shall not include works that remain - separable from, or merely link (or bind by name) to the interfaces of, - the Work and Derivative Works thereof. - - "Contribution" shall mean any work of authorship, including - the original version of the Work and any modifications or additions - to that Work or Derivative Works thereof, that is intentionally - submitted to Licensor for inclusion in the Work by the copyright owner - or by an individual or Legal Entity authorized to submit on behalf of - the copyright owner. For the purposes of this definition, "submitted" - means any form of electronic, verbal, or written communication sent - to the Licensor or its representatives, including but not limited to - communication on electronic mailing lists, source code control systems, - and issue tracking systems that are managed by, or on behalf of, the - Licensor for the purpose of discussing and improving the Work, but - excluding communication that is conspicuously marked or otherwise - designated in writing by the copyright owner as "Not a Contribution." - - "Contributor" shall mean Licensor and any individual or Legal Entity - on behalf of whom a Contribution has been received by Licensor and - subsequently incorporated within the Work. - - 2. Grant of Copyright License. Subject to the terms and conditions of - this License, each Contributor hereby grants to You a perpetual, - worldwide, non-exclusive, no-charge, royalty-free, irrevocable - copyright license to reproduce, prepare Derivative Works of, - publicly display, publicly perform, sublicense, and distribute the - Work and such Derivative Works in Source or Object form. - - 3. Grant of Patent License. Subject to the terms and conditions of - this License, each Contributor hereby grants to You a perpetual, - worldwide, non-exclusive, no-charge, royalty-free, irrevocable - (except as stated in this section) patent license to make, have made, - use, offer to sell, sell, import, and otherwise transfer the Work, - where such license applies only to those patent claims licensable - by such Contributor that are necessarily infringed by their - Contribution(s) alone or by combination of their Contribution(s) - with the Work to which such Contribution(s) was submitted. If You - institute patent litigation against any entity (including a - cross-claim or counterclaim in a lawsuit) alleging that the Work - or a Contribution incorporated within the Work constitutes direct - or contributory patent infringement, then any patent licenses - granted to You under this License for that Work shall terminate - as of the date such litigation is filed. - - 4. Redistribution. You may reproduce and distribute copies of the - Work or Derivative Works thereof in any medium, with or without - modifications, and in Source or Object form, provided that You - meet the following conditions: - - (a) You must give any other recipients of the Work or - Derivative Works a copy of this License; and - - (b) You must cause any modified files to carry prominent notices - stating that You changed the files; and - - (c) You must retain, in the Source form of any Derivative Works - that You distribute, all copyright, patent, trademark, and - attribution notices from the Source form of the Work, - excluding those notices that do not pertain to any part of - the Derivative Works; and - - (d) If the Work includes a "NOTICE" text file as part of its - distribution, then any Derivative Works that You distribute must - include a readable copy of the attribution notices contained - within such NOTICE file, excluding those notices that do not - pertain to any part of the Derivative Works, in at least one - of the following places: within a NOTICE text file distributed - as part of the Derivative Works; within the Source form or - documentation, if provided along with the Derivative Works; or, - within a display generated by the Derivative Works, if and - wherever such third-party notices normally appear. The contents - of the NOTICE file are for informational purposes only and - do not modify the License. You may add Your own attribution - notices within Derivative Works that You distribute, alongside - or as an addendum to the NOTICE text from the Work, provided - that such additional attribution notices cannot be construed - as modifying the License. - - You may add Your own copyright statement to Your modifications and - may provide additional or different license terms and conditions - for use, reproduction, or distribution of Your modifications, or - for any such Derivative Works as a whole, provided Your use, - reproduction, and distribution of the Work otherwise complies with - the conditions stated in this License. - - 5. Submission of Contributions. Unless You explicitly state otherwise, - any Contribution intentionally submitted for inclusion in the Work - by You to the Licensor shall be under the terms and conditions of - this License, without any additional terms or conditions. - Notwithstanding the above, nothing herein shall supersede or modify - the terms of any separate license agreement you may have executed - with Licensor regarding such Contributions. - - 6. Trademarks. This License does not grant permission to use the trade - names, trademarks, service marks, or product names of the Licensor, - except as required for reasonable and customary use in describing the - origin of the Work and reproducing the content of the NOTICE file. - - 7. Disclaimer of Warranty. Unless required by applicable law or - agreed to in writing, Licensor provides the Work (and each - Contributor provides its Contributions) on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or - implied, including, without limitation, any warranties or conditions - of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A - PARTICULAR PURPOSE. You are solely responsible for determining the - appropriateness of using or redistributing the Work and assume any - risks associated with Your exercise of permissions under this License. - - 8. Limitation of Liability. In no event and under no legal theory, - whether in tort (including negligence), contract, or otherwise, - unless required by applicable law (such as deliberate and grossly - negligent acts) or agreed to in writing, shall any Contributor be - liable to You for damages, including any direct, indirect, special, - incidental, or consequential damages of any character arising as a - result of this License or out of the use or inability to use the - Work (including but not limited to damages for loss of goodwill, - work stoppage, computer failure or malfunction, or any and all - other commercial damages or losses), even if such Contributor - has been advised of the possibility of such damages. - - 9. Accepting Warranty or Additional Liability. While redistributing - the Work or Derivative Works thereof, You may choose to offer, - and charge a fee for, acceptance of support, warranty, indemnity, - or other liability obligations and/or rights consistent with this - License. However, in accepting such obligations, You may act only - on Your own behalf and on Your sole responsibility, not on behalf - of any other Contributor, and only if You agree to indemnify, - defend, and hold each Contributor harmless for any liability - incurred by, or claims asserted against, such Contributor by reason - of your accepting any such warranty or additional liability. - - END OF TERMS AND CONDITIONS - - APPENDIX: How to apply the Apache License to your work. - - To apply the Apache License to your work, attach the following - boilerplate notice, with the fields enclosed by brackets "{}" - replaced with your own identifying information. (Don't include - the brackets!) The text should be enclosed in the appropriate - comment syntax for the file format. We also recommend that a - file or class name and description of purpose be included on the - same "printed page" as the copyright notice for easier - identification within third-party archives. - - Copyright {yyyy} {name of copyright owner} - - Licensed under the Apache License, Version 2.0 (the "License"); - you may not use this file 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. diff --git a/README-WG.md b/README-WG.md deleted file mode 100644 index 08de27545a..0000000000 --- a/README-WG.md +++ /dev/null @@ -1,66 +0,0 @@ -# Kubernetes Conformance - -The Kubernetes Software Conformance Working Group operates under the aegis of CNCF. -The charter of the working group is to define the process around certifying -Kubernetes conformance. We collaborate with the Kubernetes [SIG Architecture](https://github.com/kubernetes/community/tree/master/sig-architecture) who owns -the conformance definition, and [SIG Testing](https://github.com/kubernetes/community/tree/master/sig-testing) who work on -the mechanics of the conformance tests. - -The goal for the group is to create a software conformance program that any Kubernetes implementation can use to demonstrate that they are conformant and interoperable. Here is a [list](https://docs.google.com/spreadsheets/d/1LxSqBzjOxfGx3cmtZ4EbB_BGCxT_wlxW_xgHVVa23es/edit#gid=0) of all known current implementations of Kubernetes. - -# Submitting Conformance Results - -We have [instructions for submitters](instructions.md) and [for -reviewers](reviewing.md). - -# Mailing List - -https://lists.cncf.io/mailman/listinfo/cncf-k8s-conformance - -⚠️ To view all the docs below your Google account MUST also belong to [kubernetes-dev](https://goo.gl/C4CR8r) (though you don't need to actually receive mail from the group). - -# Slack - -[slack.k8s.io](slack.k8s.io) #k8s-conformance - -# Documentation - -* [Early design proposal](https://docs.google.com/document/d/1JsE9itAzL-ZSqKbd5rYnHKKSFW6xK4m50wBj1lTz6Do/edit#heading=h.ub3h0cdur849) -* [Certified Kubernetes Design Brief](https://docs.google.com/document/d/16ORnXNkR-hFQzNZ6aL3OroXM6_zLP4gKME9E3NyD1jw/edit#) - -# Upcoming Meetings - -## December 6, Austin (KubeCon) - -* [Agenda](https://docs.google.com/document/d/1kHgty5PqHRZWotmbb2aicgvKNhW4m4qWBXFSk-hkYBg/edit) - -# Past Meetings & Presentations - -NB. you need to join [kubernetes-dev](https://goo.gl/C4CR8r) to access all documents. - -## September 26, Video Meet -* [Notes](https://docs.google.com/document/d/1XkuZToB31AAjOCy4pMxzxS2HHcRj4O_Xu_F84l8ecAc/edit) - - -## September 12, Los Angeles -* [Notes](https://docs.google.com/document/d/1HcyeqfFCZ3pVvUg3HRqEPoAeiRKKH5oERm97kUy27RM/edit) -* [Slides](https://docs.google.com/presentation/d/198DZzAC22rLGNrLYpoEha-PuJE3QAkSaJdZ37lkJ8r4/edit#slide=id.g19497da556_0_12) - -## July 27, Seattle - -* [Notes](https://docs.google.com/document/d/1EO6S_o6hSRQFDQ_AkaizZd7Ia5N5fSFwAih-GfNGbRw/edit#heading=h.9mbss5g49xcf) -* [Sonobuoy Slides](https://docs.google.com/presentation/u/1/d/1jw5PJGKVMX_1Hv7pDsAqyq_xQThNEPEfaYaYxQqk6cU/edit?usp=sharing) - -## May 30, San Francisco - -* [Notes](https://docs.google.com/document/d/1nwGwnfvWoDkIdDW5dl2bbbA_nFULrq9xrt1vqpJOE3Y/edit#heading=h.ub3h0cdur849) - -## April, Austin - -* [Overview](https://docs.google.com/document/d/1Nbzi6vl6J2oBk3coGpW_oo1GPmOx7OGOYHDzlo2bxC0/edit) -* [Notes](https://docs.google.com/document/d/1OqJDVBaCtn4DfSEyCByAkXkyKtLM7a9sDs_IZmvCbr0/edit) -* [Slides](https://docs.google.com/presentation/d/1M1sesGhXyDDanF2WBr-l0jvyQQlKLH-YK7v2euqBeB4/edit#slide=id.g207a823394_2_299) - -## [BoF] March, Berlin - -* [Slides](https://docs.google.com/presentation/d/1DbwKE0TiG4hNkHnjerAhyUbvArkcCDw1JNqAWAO90Iw/edit#slide=id.g19497da556_0_12) diff --git a/README.md b/README.md deleted file mode 100644 index 342d84b969..0000000000 --- a/README.md +++ /dev/null @@ -1,35 +0,0 @@ -# Certified Kubernetes - -Over the last 3 years Kubernetes has seen wide-scale adoption by a vibrant and diverse community of platform providers. In fact, there are now more than [60](https://docs.google.com/spreadsheets/u/1/d/1LxSqBzjOxfGx3cmtZ4EbB_BGCxT_wlxW_xgHVVa23es/edit#gid=0) known Kubernetes platforms and distributions. - -One of the goals of the project has always been consistency and portability. Kubernetes sits on top of the infrastructure and enables you to describe your workload in a common format. Kubernetes makes it easy to move workloads from one place to another, or combine disjointed environments with a shared control plane. - -In order to better serve these goals, the Kubernetes community (under the aegis of the CNCF) is -running a Kubernetes Software Conformance Certification program, currently in a pre-launch status. -All vendors are invited to submit conformance testing results for review and certification by the CNCF. The CNCF will formally certify compliant platforms and officially launch the program later this year. - -This program gives end users the confidence that when they use a Certified Kubernetes product they can rely on a high level of common functionality. It gives Independent Software Vendors (ISVs) confidence that if their customer is using a Certified Kubernetes platform that their software will behave as expected. - -Just like Kubernetes itself, the conformance certification is a living thing. Certification is versioned, and with each new version of Kubernetes, as features are added and the architecture changes, the Certification requirements will change as appropriate. The Kubernetes community, through [SIG Architecture](https://github.com/kubernetes/community/tree/master/sig-architecture), is the change controller and oversees of what it means to be Certified Kubernetes. Work on the mechanics of the conformance tests occurs in [SIG Testing](https://github.com/kubernetes/community/tree/master/sig-testing) and the [Conformance WG](README-WG.md) develops the process and policy around the certification program. - -Once the program officially launches later this year, platforms that certify will be able to proudly display the new Certified Kubernetes logo mark on their marketing materials and may also take advantage of a new combination trademark rule the CNCF adopted for Certified Kubernetes providers that keep up to date with their certification. Certification is available for Kubernetes versions 1.7 and higher. - -To ensure the pace of innovation in Kubernetes continues and benefits all users, platforms must complete a recertification each year for the current or previous version of Kubernetes to remain certified. This ensures that when you see the Certified Kubernetes mark on a product, you’re not only getting something that’s proven conformant, but also contains the latest and greatest developments from the community. - -## Program Information - -[Certification Guide](instructions.md) - -[Certified Kubernetes Conformance Program – Terms and Conditions](https://github.com/cncf/k8s-conformance/tree/master/terms-conditions) - -[Certified Kubernetes Conformance Program – Participation Form](https://github.com/cncf/k8s-conformance/tree/master/participation-form) - -[Certified Kubernetes Conformance Program – Brand Guidelines](https://github.com/cncf/artwork/blob/master/kubernetes/certified_kubernetes/Certified_Kubernetes_BrandGuide_101617.pdf) - -[Certified Kubernetes Conformance Program – Marks](https://github.com/cncf/artwork/tree/master/kubernetes/certified_kubernetes) - -## Working Group Information - -To participate and contribute to the program itself (including discussion of -issues affecting conformance and certification), join the mailing list and -slack channel. Details: [Conformance WG](README-WG.md). diff --git a/instructions.md b/instructions.md deleted file mode 100644 index 12e236c793..0000000000 --- a/instructions.md +++ /dev/null @@ -1,82 +0,0 @@ -# How to submit conformance results - -## The tests - -The standard set of conformance tests is currently those defined by the -`[Conformance]` tag in the -[kubernetes e2e](https://github.com/kubernetes/kubernetes/tree/master/test/e2e) -suite. - -## Running - -The standard tool for running these tests is -[sonobuoy](https://github.com/heptio/sonobuoy), and the standard way to run -these in your cluster is with `curl -L https://raw.githubusercontent.com/cncf/k8s-conformance/master/sonobuoy-conformance-1.7.yaml | kubectl apply -f -`. - -Watch sonobuoy's logs with `kubectl logs -f -n sonobuoy sonobuoy` and wait for -the line `no-exit was specified, sonobuoy is now blocking`. At this point, use -`kubectl cp` to bring the results to your local machine, expand the tarball, and -retain `plugins/e2e/results/{e2e.log,junit.xml}`. - -## Uploading - -Prepare a PR to -[https://github.com/cncf/k8s-conformance](https://github.com/cncf/k8s-conformance). -In the descriptions below, `X.Y` refers to the kubernetes major and minor -version, and `$dir` is a short subdirectory name to hold the results for your -product. Examples would be `gke` or `openshift`. - -Description: `Conformance results for vX.Y/$dir` - -### Contents of the PR - -``` -vX.Y/$dir/README.md: A script or human-readable description of how to reproduce -your results. -vX.Y/$dir/version.txt: Test and cluster versions. -vX.Y/$dir/e2e.log: Test log output. -vX.Y/$dir/junit_01.xml: Machine-readable test log. -vX.Y/$dir/PRODUCT.yaml: See below. -``` - -#### PRODUCT.yaml - -This file describes your product. Please fill in these fields as appropriate. -Examples below are for a fictional Kubernetes implementation called _Turbo -Encabulator_ produced by a company named _Yoyodyne_. - -```yaml -vendor: Yoyodyne -name: Turbo Encabulator -version: v1.7.4 -website_url: https://yoyo.dyne/turbo-encabulator -documentation_url: https://yoyo.dyne/turbo-encabulator/docs -product_logo_url: https://yoyo.dyne/assets/turbo-encabulator.svg -``` - -Note: the `version` property is the version of your product, not the version of -Kubernetes being used. - -### Sample PR - -See https://github.com/mml/k8s-conformance/pull/1 for a sample. - -## Amendment for Private Review - -If you need a private review, please contact info@cncf.io. - -## Review - -A reviewer should be assigned to your PR shortly. If you seek faster service, -please contact info@cncf.io. - -## Issues - -If you have problems certifying that you feel are an issue with the conformance -program itself (and not just your own configuration), you can file an issue in -the [repository](https://github.com/cncf/k8s-conformance). Questions and -comments can also be sent to the working group's -[mailing list and slack channel](https://github.com/cncf/k8s-conformance/blob/master/README.md). -[SIG Architecture](https://github.com/kubernetes/community/tree/master/sig-architecture) -is the change controller of the conformance definition, we track a -[list of issue resolutions](issues.md) with SIG Architecture. diff --git a/issues.md b/issues.md deleted file mode 100644 index 9d62693d44..0000000000 --- a/issues.md +++ /dev/null @@ -1,14 +0,0 @@ -# Issue Tracking Doc - -This document tracks issues with the conformance e2e suite and their resolutions. - -## e2e: Internet connection test should not rely on ICMP achievement - -* https://github.com/kubernetes/kubernetes/issues/51145 -* https://github.com/kubernetes/kubernetes/pull/51287 -* https://github.com/kubernetes/kubernetes/pull/53381 - -## ThirdParty resource e2e test should not be marked as conformance - -* https://github.com/kubernetes/kubernetes/issues/52822 -* https://github.com/kubernetes/kubernetes/pull/52823 diff --git a/participation-form/Certified_Kubernetes_Form.md b/participation-form/Certified_Kubernetes_Form.md deleted file mode 100644 index 6f3890ae7b..0000000000 --- a/participation-form/Certified_Kubernetes_Form.md +++ /dev/null @@ -1,94 +0,0 @@ -### Certified Kubernetes Conformance Program -#### Participation Form - -Complete this form for each Participant (company or other entity) that desires to participate in the Certified Kubernetes Conformance Program and to use the Certified Kubernetes Marks or Participant Kubernetes Combinations. Kubernetes and the Certified Kubernetes Marks are trademarks of The Linux Foundation. Capitalized terms used herein and not otherwise defined shall have the same meanings set forth in the Program Terms. - -By signing below and submitting this form to The Linux Foundation (by email to [conformance@cncf.io](mailto:conformance@cncf.io), by [DocuSign](https://na3.docusign.net/Member/PowerFormSigning.aspx?PowerFormId=ba08f93a-65ca-4c5d-8210-d5c858bb9208) or other method made available by The Linux Foundation): - -1. The Participant agrees to the Terms and Conditions of the Certified Kubernetes Conformance Program (the "**Program Terms**"), available at . -2. The Participant confirms that the products and services identified below as Qualifying Offerings have passed all of the self-tests described in the Certification Guide, and are Qualifying Offerings under the Program Terms. -3. The Participant confirms that it has submitted to the Cloud Native Computing Foundation ("**CNCF**") the results of the self-tests prior to its first public use of the Certified Kubernetes Marks associated with the corresponding version of Kubernetes. -4. The Participant confirms that it will either (a) maintain conformance of the Qualifying Offerings with later versions of Kubernetes, or (b) cease use of the Certified Kubernetes Marks and Participant Kubernetes Combinations at the end of the applicable conformance time period described in the Program Terms. -5. The Participant confirms that it has listed below all Participant Kubernetes Combinations that it intends to use with the Qualifying Offerings. -6. The Participant confirms that it will promptly submit an updated Participant Form to The Linux Foundation prior to (a) using the Certified Kubernetes Marks with Qualifying Offerings not listed here, or (b) using Participant Kubernetes Combinations not listed here. -7. I confirm that I am authorized to make the above statements and to submit this form on behalf of the Participant. - - -#### Participant Information - - -Company / entity name: - -\___________________________________________________ - -Contact address: - -\___________________________________________________ - -\___________________________________________________ - -\___________________________________________________ - -\___________________________________________________ - -Contact telephone: - -\___________________________________________________ - -Contact email: - -\___________________________________________________ - - -Select one: - - - [ ] Participant is a member of CNCF. - - [ ] Participant is a non-profit organization. - - [ ] Neither of the above. **Please contact CNCF to discuss fees for participation in the Conformance Program.** - -#### Qualifying Offerings - -Name, brief description and URLs for more information: - -\___________________________________________________________________________ - -\___________________________________________________________________________ - -\___________________________________________________________________________ - -\___________________________________________________________________________ - - -#### Participant Kubernetes Combinations - -List all Participant Kubernetes Combinations to be used with the Qualifying Offerings, if any: - -(for example, "XYZ Kubernetes" or "XYZ Kubernetes Platform") - -\___________________________________________________________________________ - -\___________________________________________________________________________ - -\___________________________________________________________________________ - -\___________________________________________________________________________ - - -#### Conformance Details - -Initial Version of Kubernetes for Conformance (e.g., v1.8): _______ - -Conformance Date: __________________ - - -#### Signed on behalf of Participant by: - -``` -Signature: __________________________________ - -Name: __________________________________ - -Title: __________________________________ - -Date: __________________________________ -``` diff --git a/participation-form/Certified_Kubernetes_Form.pdf b/participation-form/Certified_Kubernetes_Form.pdf deleted file mode 100644 index a5a161a038..0000000000 Binary files a/participation-form/Certified_Kubernetes_Form.pdf and /dev/null differ diff --git a/reviewing.md b/reviewing.md deleted file mode 100644 index e5aca794c0..0000000000 --- a/reviewing.md +++ /dev/null @@ -1,5 +0,0 @@ -# How to review conformance results - - 1. Make sure the list of files matches [the one specified here](https://github.com/cncf/k8s-conformance/blob/master/instructions.md#contents-of-the-pr) - 2. Look at `version.txt`. Make sure the `client` and `server` versions match each other to the minor version level. Make sure this also matches the `vX.Y` subdirectory that the PR is in. - 3. Verify that the last line of `e2e.log` says "SUCCESS! -- `N` Passed | 0 Failed | 0 Pending | `M` Skipped PASS". The exact value of `N` and `M` don't matter as long as we see `0 Failed | 0 Pending`. diff --git a/sonobuoy-conformance-1.7.yaml b/sonobuoy-conformance-1.7.yaml deleted file mode 100644 index 56d8ca22e5..0000000000 --- a/sonobuoy-conformance-1.7.yaml +++ /dev/null @@ -1,194 +0,0 @@ ---- -apiVersion: v1 -kind: Namespace -metadata: - name: sonobuoy ---- -apiVersion: v1 -kind: ServiceAccount -metadata: - labels: - component: sonobuoy - name: sonobuoy-serviceaccount - namespace: sonobuoy ---- -apiVersion: rbac.authorization.k8s.io/v1beta1 -kind: ClusterRoleBinding -metadata: - labels: - component: sonobuoy - name: sonobuoy-serviceaccount -roleRef: - apiGroup: rbac.authorization.k8s.io - kind: ClusterRole - name: sonobuoy-serviceaccount -subjects: -- kind: ServiceAccount - name: sonobuoy-serviceaccount - namespace: sonobuoy ---- -apiVersion: rbac.authorization.k8s.io/v1beta1 -kind: ClusterRole -metadata: - labels: - component: sonobuoy - name: sonobuoy-serviceaccount - namespace: sonobuoy -rules: -- apiGroups: - - '*' - resources: - - '*' - verbs: - - '*' ---- -apiVersion: v1 -kind: ConfigMap -metadata: - labels: - component: sonobuoy - name: sonobuoy-config-cm - namespace: sonobuoy -data: - config.json: | - { - "Description": "EXAMPLE", - "Filters": { - "LabelSelector": "", - "Namespaces": ".*" - }, - "PluginNamespace": "sonobuoy", - "Plugins": [ - { - "name": "e2e" - } - ], - "Resources": [ - ], - "ResultsDir": "/tmp/sonobuoy", - "Server": { - "advertiseaddress": "sonobuoy-master:8080", - "bindaddress": "0.0.0.0", - "bindport": 8080, - "timeoutseconds": 3600 - }, - "Version": "v0.8.0" - } ---- -apiVersion: v1 -kind: ConfigMap -metadata: - labels: - component: sonobuoy - name: sonobuoy-plugins-cm - namespace: sonobuoy -data: - e2e.yaml: | - driver: Job - name: e2e - resultType: e2e - spec: - containers: - - env: - - name: E2E_FOCUS - value: '\[Conformance\]' - image: gcr.io/heptio-images/kube-conformance:v1.7.3 - imagePullPolicy: Always - name: e2e - volumeMounts: - - mountPath: /tmp/results - name: results - - command: - - sh - - -c - - /sonobuoy worker global -v 5 --logtostderr - env: - - name: NODE_NAME - valueFrom: - fieldRef: - apiVersion: v1 - fieldPath: spec.nodeName - - name: RESULTS_DIR - value: /tmp/results - image: gcr.io/heptio-images/sonobuoy:latest - imagePullPolicy: Always - name: sonobuoy-worker - volumeMounts: - - mountPath: /etc/sonobuoy - name: config - - mountPath: /tmp/results - name: results - restartPolicy: Never - serviceAccountName: sonobuoy-serviceaccount - tolerations: - - effect: NoSchedule - key: node-role.kubernetes.io/master - operator: Exists - - key: CriticalAddonsOnly - operator: Exists - volumes: - - emptyDir: {} - name: results - - configMap: - name: __SONOBUOY_CONFIGMAP__ - name: config ---- -apiVersion: v1 -kind: Pod -metadata: - labels: - component: sonobuoy - run: sonobuoy-master - tier: analysis - name: sonobuoy - namespace: sonobuoy -spec: - containers: - - command: - - /bin/bash - - -c - - /sonobuoy master --no-exit=true -v 3 --logtostderr - env: - - name: SONOBUOY_ADVERTISE_IP - valueFrom: - fieldRef: - fieldPath: status.podIP - image: gcr.io/heptio-images/sonobuoy:latest - imagePullPolicy: Always - name: kube-sonobuoy - volumeMounts: - - mountPath: /etc/sonobuoy - name: sonobuoy-config-volume - - mountPath: /etc/sonobuoy/plugins.d - name: sonobuoy-plugins-volume - - mountPath: /tmp/sonobuoy - name: output-volume - restartPolicy: Never - serviceAccountName: sonobuoy-serviceaccount - volumes: - - configMap: - name: sonobuoy-config-cm - name: sonobuoy-config-volume - - configMap: - name: sonobuoy-plugins-cm - name: sonobuoy-plugins-volume - - emptyDir: {} - name: output-volume ---- -apiVersion: v1 -kind: Service -metadata: - labels: - component: sonobuoy - run: sonobuoy-master - name: sonobuoy-master - namespace: sonobuoy -spec: - ports: - - port: 8080 - protocol: TCP - targetPort: 8080 - selector: - run: sonobuoy-master - type: ClusterIP - diff --git a/terms-conditions/Certified_Kubernetes_Terms.md b/terms-conditions/Certified_Kubernetes_Terms.md deleted file mode 100644 index 1a3ec4ce44..0000000000 --- a/terms-conditions/Certified_Kubernetes_Terms.md +++ /dev/null @@ -1,138 +0,0 @@ -### Certified Kubernetes Conformance Program – Terms and Conditions -#### Last updated: October 30, 2017 - -This document sets forth the terms and conditions that apply to the Conformance Program and use of the Certified Kubernetes Marks. - -In this document, these terms have the following meanings: -* "**Certified Kubernetes Marks**" means (1) the mark "Certified Kubernetes" and (2) all other logos and marks described in the Branding Guide, as defined herein; -* "**Kubernetes Word Mark**" means the trademark "Kubernetes"; -* "**Participant Kubernetes Combination**" means a combination that includes both the Participant’s mark(s) and the Kubernetes Word Mark as elements (for example, "XYZ Kubernetes" or "XYZ Kubernetes Platform"); -* "**Conformance Program**" means the program described in this document; -* "**Participant**" means a company or other entity that is permitted to use one or more of the Certified Kubernetes Marks in association with their goods and services, pursuant to the Conformance Program; and -* "**Qualifying Offering(s)**" means a Participant’s goods or services that have passed all of the self-tests described in the Certification Guide, where the self-test results have been submitted to and accepted by CNCF as described below. - -#### Related Documents - -Together with these terms and conditions, the following documents are part of the Conformance Program, each as updated from time to time: -* "**Certification Guide**": the conformance testing instructions and requirements for the Conformance Program, available at ; -* "**Branding Guide**": the Certified Kubernetes Brand Guidelines, available at ; -* "**LF Trademark Usage Guidelines**": The Linux Foundation Trademark Usage Guidelines, available at ; and -* "**Participation Form**": the Certified Kubernetes Participation Form, available at . - -#### Introduction - -The Certified Kubernetes Marks and the Kubernetes Word Mark are trademarks of The Linux Foundation. The Linux Foundation has established the Conformance Program to achieve two objectives: 1) The Linux Foundation needs to ensure that the Certified Kubernetes Marks and the Kubernetes Word Mark remain reliable indicators of the qualities that they have been created to preserve, and 2) The Linux Foundation needs to ensure that community members are able to accurately describe their Qualifying Offerings. - -To achieve these objectives, The Linux Foundation requires that third parties who use the Certified Kubernetes Marks or Participant Kubernetes Combinations in association with their goods and services may do so only as Participants pursuant to the Conformance Program described in this document. By participating in the Conformance Program and by using the Certified Kubernetes Marks or Participant Kubernetes Combinations, a Participant acknowledges that third parties will be relying on the accuracy of its self-testing results and on its compliance with the terms of the Conformance Program. - -#### Participant Requirements - -In order to be a Participant in the Conformance Program and to use the Certified Kubernetes Marks or Participant Kubernetes Combinations, a Participant must do the following: - -1. determine those of its goods and services with which it intends to use with the Certified Kubernetes Marks and Participant Kubernetes Combinations; -2. confirm through self-testing that those goods and services are Qualifying Offerings, as described herein; -3. submit to The Linux Foundation a signed Participation Form (by email to [conformance@cncf.io](mailto:conformance@cncf.io) or other method made available by The Linux Foundation), designating the applicable Qualifying Offerings and Participant Kubernetes Combinations and accepting the terms and conditions of the Conformance Program; -4. submit to the Cloud Native Computing Foundation ("CNCF") the successfully-passing self-testing results for the Qualifying Offerings, and have the results accepted by CNCF; -5. pay fees (if any) required for its participation in the Conformance Program; and -6. abide by the terms and conditions of the Conformance Program, including subsequent re-testing as described herein, throughout the period of the Participant’s use of the Certified Kubernetes Marks and Participant Kubernetes Combinations. - -Members of CNCF and non-profit organizations will not be charged fees to participate in the Conformance Program. Other potential Participants should contact CNCF for more information about participation fees. - -#### Qualifying Offerings and Self-Testing - -_Eligible Versions_. A Qualifying Offering may be initially self-certified for (1) the then-current minor (x.y) official release of Kubernetes, and (2) the immediately-preceding minor (x.y-1) official release of Kubernetes; provided, in each case, that CNCF has made available a testing evaluation program for that version of Kubernetes. - -Example: Following the release of Kubernetes v1.10, a new Qualifying Offering may be initially self-certified for Kubernetes v1.10 or v1.9, but not for v1.8. - -_Self-Testing Process_. The Certified Kubernetes Marks and Participant Kubernetes Combinations are intended to be used with Participants’ goods and services that are Qualifying Offerings. The Certification Guide contains details about the self-testing process and the specific tests that must be passed for a Participant’s offering to be a Qualifying Offering. A Participant confirms that its goods and services are Qualifying Offerings by demonstrating that its offerings have successfully passed all of the self-tests set forth in the Certification Guide. CNCF will make available a testing evaluation program that Participants will use to determine whether the self-tests are passed or failed. - -_Submission of Self-Testing Results_. After passing the designated self-tests, a Participant must submit to CNCF (in the manner described in the Certification Guide) a copy of the self-testing results generated by the testing evaluation program no more than 90 days prior to its first public use of the Certified Kubernetes Marks or Participant Kubernetes Combinations. These results will be made available to the public on a CNCF website or public repository if Participant makes public use of the Certified Kubernetes Marks or Participant Kubernetes Combinations. However, if the Participant decides not to proceed with any such public use following submission of self-testing results to CNCF, then upon Participant’s written request to CNCF the test results will not be publicly disclosed. - -_Acceptance of Self-Testing Results_. The Certified Kubernetes Marks and Participant Kubernetes Combinations may only be used with Qualifying Offerings whose self-tests have been both submitted to and accepted by CNCF (in the manner described in the Certification Guide). - -_Profiles_. The Certification Guide may also specify, for certain versions of Kubernetes, one or more "Profiles" consisting of groups of different or additional functionality. These Profiles will be associated with additional sets of self-tests. If a Participant’s Qualifying Offering also passes the set of self-tests associated with a Profile, then the Participant may additionally use with the Qualifying Offering any Certified Kubernetes Marks designated for that Profile. - -_End User Reproducibility_. One objective of the Conformance Program is that the self-tests set forth in the Certification Guide should be verifiable by end users of each Qualifying Offering. A Participant may not prohibit or prevent end users of its Qualifying Offerings from running the corresponding self-tests on a Qualifying Offering, in order to reproduce the submitted results and verify their accuracy. If The Linux Foundation determines or is informed that (1) end users of a Qualifying Offering are prevented from running the tests, or (2) that end users’ results from running the tests demonstrate that a Qualifying Offering does not successfully pass the tests, then upon written notice from The Linux Foundation the Participant must address any non-conformance concerns raised by The Linux Foundation; successfully pass the corresponding self-tests; and submit to CNCF a copy of the new self-testing results generated by the testing evaluation program within 30 days following such notice. Otherwise, the Participant will be subject to the requirements to remove the Certified Kubernetes Marks and Participant Kubernetes Combinations set forth herein. - -_Changes to Qualifying Offerings_. The self-testing process and permission to use the Certified Kubernetes Marks and Participant Kubernetes Combinations are intended for a specific version of a Qualifying Offering. If a Participant subsequently modifies a Qualifying Offering, and The Linux Foundation determines or is informed that the Qualifying Offering no longer conforms to the compatibility tests set forth in the Certification Guide or to users’ expectations for Qualifying Offerings, then upon written notice from The Linux Foundation the Participant must again successfully pass the corresponding self-tests and submit to CNCF a copy of the new self-testing results generated by the testing evaluation program within 30 days following such notice. Otherwise, the Participant’s permitted usage time period will be deemed expired and will be subject to the requirements to remove the Certified Kubernetes Marks and Participant Kubernetes Combinations set forth herein. - -_Conformance Time Period; Later Versions of Kubernetes_. A Participant’s permission to use the Certified Kubernetes Marks and Participant Kubernetes Combinations with its Qualifying Offerings is time-limited. The Certified Kubernetes Marks and Participant Kubernetes Combinations may be used with a Qualifying Offering for a particular version of Kubernetes (e.g., Kubernetes x.y) until the later of: - -* 12 months after the release date of Kubernetes x.y, or -* 9 months after the release date of the next minor release (e.g., Kubernetes x.y+1). - -However, notwithstanding the time limits above, the Participant may also continue to use the Certified Kubernetes Marks and Participant Kubernetes Combinations for any prior version of Kubernetes for which the offering was a Qualifying Offering, for so long as (1) the offering continues to be a Qualifying Offering for each subsequent version of Kubernetes; (2) the Qualifying Offering with the subsequent version of Kubernetes is made generally available to users of the prior version; and (3) the Participant otherwise continues to abide by the terms of the Conformance Program. - -Example: A Participant’s Qualifying Offering passed the self-tests for Kubernetes v1.9. Over the next two years, the Participant continued to ensure that passing self-tests for the Qualifying Offering were submitted to and accepted by CNCF for subsequent Kubernetes versions through the then-current version, Kubernetes v1.12. The Participant may continue to use the applicable Certified Kubernetes Marks with the Qualifying Offering for Kubernetes 1.9, even though the time limit described above for v1.9 has expired. - -_Removal of Certified Kubernetes Marks and Participant Kubernetes Combinations at End of Participation_. After the expiration of the permitted usage time period (if the Participant does not continue to ensure that it passes the self-tests for subsequent versions of Kubernetes) or other termination of participation in the Conformance Program, a Participant may no longer use the Certified Kubernetes Marks or Participant Kubernetes Combinations in new materials, and must remove the Certified Kubernetes Marks and Participant Kubernetes Combinations from existing marketing materials and websites within 30 days. - -#### Use of the Certified Kubernetes Marks and Participant Kubernetes Combinations - -Use of the Certified Kubernetes Marks and Participant Kubernetes Combinations is only permitted for Participants who have satisfied the requirements of the Conformance Program; is only permitted in connection with its Qualifying Offerings; and is only permitted for the usage time periods specified above. No other rights to use the Certified Kubernetes Marks or the Kubernetes Word Mark are permitted hereunder, except to the extent permitted under "fair use" or other applicable law. - -All use of the Certified Kubernetes Marks and Participant Kubernetes Combinations is subject to the LF Trademark Usage Guidelines, which are incorporated herein. - -Additionally, the following specific rules also apply to use of the Certified Kubernetes Marks and Participant Kubernetes Combinations: - -* **Do** follow the requirements set forth in the Branding Guide when using the Certified Kubernetes Marks. - -* **Do** specify the version of Kubernetes for which a Qualifying Offering has been self-tested, in a location near the Participant’s use of the Certified Kubernetes Marks. - -* **Do** include appropriate notices of The Linux Foundation’s ownership of the Certified Kubernetes Marks and the Kubernetes Word Mark. - -* **Do not** use the Certified Kubernetes Marks or Participant Kubernetes Combinations except as permitted pursuant to the Conformance Program’s terms. For example, do not use the Certified Kubernetes Marks or Participant Kubernetes Combinations with a service offering that is not itself a Qualifying Offering, or with a formerly Qualifying Offering whose period of use has expired. - -* **Do not** be misleading about the nature or scope of certification or conformance. **Do not** state or imply that the Participant’s participation in the Conformance Program constitutes The Linux Foundation’s or CNCF’s endorsement of a Participant or its goods or services. For example, do not say that a Participant or a Qualifying Offering has been "certified by CNCF" or "certified by The Linux Foundation," or that "The Linux Foundation has certified Product XYZ." - -* **Do not** state or imply that there are different degrees of certification or conformance. For example, do not say that a Qualifying Offering is "more certified" than another, or that it was "certified before" another Participant. However, this does not prohibit use of Certified Kubernetes Marks designated for Profiles that a Qualifying Offering has passed, as described above. - -#### Additional Terms for Use of Participant Kubernetes Combinations - -In addition to the rules set forth above and in the LF Trademark Usage Guidelines, the following specific rules also apply to use of Participant Kubernetes Combinations: - -* **Do** use the "circle R" symbol adjacent to the end of the Kubernetes Word Mark within the first prominent appearance of the Participant Kubernetes Combination, for example: XYZ Kubernetes® Engine. - -* **Do** include the following attribution statement in a conspicuous location near the first prominent appearance of the Participant Kubernetes Combination: Kubernetes® is a registered trademark of The Linux Foundation in the United States and other countries, and is used pursuant to a license from The Linux Foundation. - -* **Do** use the Participant Kubernetes Combination only in plain text form, in a similar font to the surrounding text (e.g., in the same font and style used for other header or body text on a web page). - -* **Do not** use the Participant Kubernetes Combination in a stylized form, or incorporate the Participant Kubernetes Combination or Kubernetes Word Mark into a custom logo. - -During and after the term of Participant’s participation in the Conformance Program, Participant will not, anywhere in the world, (1) register or attempt to register a mark that contains or consists of the Kubernetes Word Mark or Participant Kubernetes Combination; or (2) challenge, oppose, petition to cancel or otherwise attack or limit the Kubernetes Word Mark (whether its validity, enforceability, scope of coverage or otherwise) or The Linux Foundation’s exclusive ownership thereof. Performing either of the preceding actions shall constitute a material breach of the terms of the Conformance Program, resulting in termination of Participant’s participation in the Conformance Program without further notice and without opportunity to cure. - -Participant will promptly cooperate with The Linux Foundation, and comply with its requests and instructions, regarding use of the Participant Kubernetes Combination. The Linux Foundation shall have a reasonable right to request copies of and to inspect products and advertising distributed by Participant as an aid to enforcing the Kubernetes Word Mark and its rights hereunder, as a part of policing the Kubernetes Word Mark. Participant will promptly cease any use of the Participant Kubernetes Combination that The Linux Foundation determines may negatively impact the validity, enforceability or scope of coverage of the Kubernetes Word Mark. - -Participant will not otherwise combine the Kubernetes Word Mark with its own marks, other than Participant Kubernetes Combinations used in full compliance with the terms of the Conformance Program. - -#### Participant Marks - -Each Participant hereby grants to The Linux Foundation a royalty-free, worldwide license to use and display the names and logos of Participant and its Qualifying Offerings (the "Participant Marks") in connection with The Linux Foundation’s operation of the Conformance Program and its marketing and promotion of Participant’s participation in the Conformance Program. Each Participant represents and warrants that it possesses all rights necessary to make this license grant. The Linux Foundation will comply with any reasonable requirements regarding use of the Participant Marks about which the Participant notifies The Linux Foundation, and will correct any identified misuse within a reasonable time following Participant’s notification. Nothing in this section shall require The Linux Foundation to make any use of the Participant Marks. As between The Linux Foundation and Participant, any goodwill associated with the foregoing use of the Participant Marks shall inure to the benefit of the Participant. - -#### Term and Termination - -_Term_. The term of a Participant’s participation in the Conformance Program shall begin upon the Participant’s submission (by email to [conformance@cncf.io](mailto:conformance@cncf.io) or other method made available by The Linux Foundation), and The Linux Foundation’s receipt and acceptance, of a fully-completed Participation Form signed by the Participant. - -_Termination_. Either The Linux Foundation or the Participant may terminate Participant’s participation in the Conformance Program upon written notice to the other. Additionally, Participant’s participation in the Conformance Program shall automatically terminate (unless otherwise agreed by The Linux Foundation in writing) upon the occurrence of: (1) the Participant’s breach of the terms of the Conformance Program, if such breach is incurable or, if curable, is not cured within 15 days thereafter; or (2) the expiration of the usage time period for all of the Participant’s Qualifying Offerings, if the Participant does not confirm any new Qualifying Offering within 30 days thereafter. - -_Effect of Termination; Survival_. Upon the termination of Participant’s participation in the Conformance Program, the Participant may no longer use the Certified Kubernetes Marks or Participant Kubernetes Combinations and must remove them from existing marketing materials and websites. The sections of this agreement entitled "Participant Marks," "Disclaimer of Warranties," "Limitation of Liability," "Indemnification" and "Miscellaneous" shall survive any such termination. - -#### Disclaimer of Warranties - -THE LINUX FOUNDATION MAKES NO EXPRESS OR IMPLIED WARRANTIES WITH RESPECT TO THE CONFORMANCE PROGRAM, THE CERTIFIED KUBERNETES MARKS OR PARTICIPANT KUBERNETES COMBINATIONS, EITHER TO PARTICIPANT OR TO ANY THIRD PARTY, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, OR NON-INFRINGEMENT OF ANY THIRD PARTY INTELLECTUAL PROPERTY RIGHTS. THE DISCLAIMERS AND INDEMNITIES SET FORTH IN THE LF TRADEMARK USAGE GUIDELINES ARE ALSO DEEMED TO BE INCORPORATED HEREIN. A PARTICIPANT’S PARTICIPATION IN THE CONFORMANCE PROGRAM DOES NOT CONSTITUTE ANY FORM OF ENDORSEMENT BY THE LINUX FOUNDATION OF ANY PARTICIPANT OR ITS QUALIFYING OFFERINGS, AND THE LINUX FOUNDATION MAKES NO EXPRESS OR IMPLIED WARRANTIES WITH RESPECT THERETO. THE CONFORMANCE PROGRAM IS OFFERED "AS-IS", "AS-AVAILABLE" AND "WITH ALL FAULTS." - -#### Limitation of Liability - -TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE LINUX FOUNDATION SHALL NOT BE LIABLE FOR ANY DAMAGES, INCLUDING DIRECT, INDIRECT, SPECIAL, CONSEQUENTIAL, EXEMPLARY OR PUNITIVE DAMAGES, ARISING OUT OF OR RELATING TO THE CONFORMANCE PROGRAM OR ANY PARTICIPANT’S PARTICIPATION THEREIN. IF ANY DAMAGES ARE NOT EXCLUDED UNDER APPLICABLE LAW PURSUANT TO THE PRECEDING SENTENCE, THEN IN NO EVENT SHALL THE LINUX FOUNDATION’S LIABILITY FOR ANY SUCH DAMAGES EXCEED THE FEES PAID TO THE LINUX FOUNDATION BY THE PARTICIPANT SOLELY FOR PARTICIPATION IN THE CONFORMANCE PROGRAM. THE FOREGOING LIMITATIONS OF LIABILITY ARE AN ESSENTIAL BASIS OF THE LINUX FOUNDATION’S DECISION TO OFFER THE CONFORMANCE PROGRAM AND THE PARTICIPANT’S PARTICIPATION THEREIN, AND SHALL APPLY REGARDLESS OF THE LEGAL THEORY UPON WHICH DAMAGES MAY BE CLAIMED; REGARDLESS OF WHETHER A PARTY KNEW OR SHOULD HAVE KNOWN OF THE POSSIBILITY OF SUCH DAMAGES; AND REGARDLESS OF WHETHER THE FOREGOING LIMITATIONS OF LIABILITY CAUSE ANY REMEDY TO FAIL IN ITS ESSENTIAL PURPOSE. - -#### Indemnification - -By electing to participate in the Conformance Program or to make any use of the Certified Kubernetes Marks or Participant Kubernetes Combinations, each Participant agrees to indemnify, defend and hold harmless The Linux Foundation, together with its affiliates and its and their respective employees, officers and directors (collectively, the "Indemnified Parties") from and against any and all losses, liabilities, damages and penalties, and all related costs and expenses (including reasonable attorneys' fees) arising from (1) the Participant’s breach of the terms of the Conformance Program, (2) any third party claims that may arise in any manner by reason of Participant’s use of the Certified Kubernetes Marks or the Participant Kubernetes Combination with the Participant’s Qualifying Offerings or the Participant’s other goods and services, and (3) any third-party claim relating to the Participant’s Qualifying Offerings or the Participant’s other goods and services, including without limitation any product liability claim. - -#### Entire Agreement; Modifications - -These Terms and Conditions, together with the other documents referenced herein, constitute the entire agreement between any Participant and The Linux Foundation regarding Participant’s participation in the Conformance Program. These Terms and Conditions and the other documents referenced herein may be modified from time to time by The Linux Foundation, and updated versions will be placed on the CNCF website. Participant’s continued participation in the Conformance Program or continued use of the Certified Kubernetes Marks or Participant Kubernetes Combinations constitutes Participant’s acceptance of all such modifications. - -#### Miscellaneous - -All notices to be sent to The Linux Foundation hereunder should be sent to [info@cncf.io](mailto:info@cncf.io), unless otherwise specified herein. The Conformance Program Terms and Conditions are governed by the law of the State of California, without regards to its choice of law provisions, and any action arising hereunder shall be brought in the state or federal courts located in California. The Participant and The Linux Foundation agree that the Conformance Program does not create a partnership or joint venture between them or any other Participant. diff --git a/terms-conditions/Certified_Kubernetes_Terms.pdf b/terms-conditions/Certified_Kubernetes_Terms.pdf deleted file mode 100644 index bc78c525b9..0000000000 Binary files a/terms-conditions/Certified_Kubernetes_Terms.pdf and /dev/null differ