diff --git a/releases/v0.10.0.md b/releases/v0.10.0.md index 2dfd8e5..14e4fc5 100644 --- a/releases/v0.10.0.md +++ b/releases/v0.10.0.md @@ -74,7 +74,7 @@ The following are known limitations of this release: * Platform support is rapidly changing * SELinux is not supported on the host and must be set to permissive if in use. * Complete integration with Kubernetes is still in progress. - * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/community/issues/53) + * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/confidential-containers/issues/53) * Some commands accessing confidential data, such as `kubectl exec`, may either fail to work, or incorrectly expose information to the host * The CoCo community aspires to adopting open source security best practices, but not all practices are adopted yet. * We track our status with the OpenSSF Best Practices Badge, which remained at 75% at the time of this release. diff --git a/releases/v0.11.0.md b/releases/v0.11.0.md index 8152934..63acabe 100644 --- a/releases/v0.11.0.md +++ b/releases/v0.11.0.md @@ -71,7 +71,7 @@ The following are known limitations of this release: * Platform support is rapidly changing * SELinux is not supported on the host and must be set to permissive if in use. * Complete integration with Kubernetes is still in progress. - * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/community/issues/53) + * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/confidential-containers/issues/53) * Some commands accessing confidential data, such as `kubectl exec`, may either fail to work, or incorrectly expose information to the host * The CoCo community aspires to adopting open source security best practices, but not all practices are adopted yet. * Container metadata such as environment variables are not measured. diff --git a/releases/v0.12.0.md b/releases/v0.12.0.md index e44144f..bd0e8ff 100644 --- a/releases/v0.12.0.md +++ b/releases/v0.12.0.md @@ -80,7 +80,7 @@ The following are limitations and known issues with this release. * Platform support is rapidly changing * SELinux is not supported on the host and must be set to permissive if in use. * Complete integration with Kubernetes is still in progress. - * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/community/issues/53) + * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/confidential-containers/issues/53) * Some commands accessing confidential data, such as `kubectl exec`, may either fail to work, or incorrectly expose information to the host * The CoCo community aspires to adopting open source security best practices, but not all practices are adopted yet. * Container metadata such as environment variables are not measured. diff --git a/releases/v0.2.0.md b/releases/v0.2.0.md index 86b71c5..9ec1f08 100644 --- a/releases/v0.2.0.md +++ b/releases/v0.2.0.md @@ -60,11 +60,11 @@ The following are known limitations of this release: * `crio` is not supported - CoCo is not fully integrated with the orchestration ecosystem (Kubernetes, OpenShift) * OpenShift is a non-starter at the moment due to its dependency on [CRI-O](https://github.com/cri-o/cri-o) - * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/community/issues/53) + * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/confidential-containers/issues/53) * Some commands accessing confidential data, such as `kubectl exec`, may either fail to work, or incorrectly expose information to the host * Container image sharing is not possible in this release * Container images are downloaded by the guest (with encryption), not by the host - * As a result, the same image will be downloaded separately by every pod using it, not shared between pods on the same host. [More info](https://github.com/confidential-containers/community/issues/66) + * As a result, the same image will be downloaded separately by every pod using it, not shared between pods on the same host. [More info](https://github.com/confidential-containers/confidential-containers/issues/66) - The CoCo community aspires to adopting open source security best practices, but not all practices are adopted yet. * We track our status with the OpenSSF Best Practices Badge, which increased to 46% at the time of this release. * The main gaps are in test coverage, both general and security tests. diff --git a/releases/v0.3.0.md b/releases/v0.3.0.md index 50d8391..81b3dc4 100644 --- a/releases/v0.3.0.md +++ b/releases/v0.3.0.md @@ -60,11 +60,11 @@ The following are known limitations of this release: * `crio` is not supported - CoCo is not fully integrated with the orchestration ecosystem (Kubernetes, OpenShift) * OpenShift is a non-starter at the moment due to its dependency on [CRI-O](https://github.com/cri-o/cri-o) - * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/community/issues/53) + * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/confidential-containers/issues/53) * Some commands accessing confidential data, such as `kubectl exec`, may either fail to work, or incorrectly expose information to the host * Container image sharing is not possible in this release * Container images are downloaded by the guest (with encryption), not by the host - * As a result, the same image will be downloaded separately by every pod using it, not shared between pods on the same host. [More info](https://github.com/confidential-containers/community/issues/66) + * As a result, the same image will be downloaded separately by every pod using it, not shared between pods on the same host. [More info](https://github.com/confidential-containers/confidential-containers/issues/66) - The CoCo community aspires to adopting open source security best practices, but not all practices are adopted yet. * We track our status with the OpenSSF Best Practices Badge, which increased to 49% at the time of this release. * The main gaps are in test coverage, both general and security tests. diff --git a/releases/v0.4.0.md b/releases/v0.4.0.md index e5ce93f..a6cd783 100644 --- a/releases/v0.4.0.md +++ b/releases/v0.4.0.md @@ -58,11 +58,11 @@ The following are known limitations of this release: * `crio` is not supported - CoCo is not fully integrated with the orchestration ecosystem (Kubernetes, OpenShift) * OpenShift is a non-starter at the moment due to its dependency on [CRI-O](https://github.com/cri-o/cri-o) - * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/community/issues/53) + * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/confidential-containers/issues/53) * Some commands accessing confidential data, such as `kubectl exec`, may either fail to work, or incorrectly expose information to the host * Container image sharing is not possible in this release * Container images are downloaded by the guest (with encryption), not by the host - * As a result, the same image will be downloaded separately by every pod using it, not shared between pods on the same host. [More info](https://github.com/confidential-containers/community/issues/66) + * As a result, the same image will be downloaded separately by every pod using it, not shared between pods on the same host. [More info](https://github.com/confidential-containers/confidential-containers/issues/66) - The CoCo community aspires to adopting open source security best practices, but not all practices are adopted yet. * We track our status with the OpenSSF Best Practices Badge, which increased to 49% at the time of this release. * The main gaps are in test coverage, both general and security tests. diff --git a/releases/v0.5.0.md b/releases/v0.5.0.md index 15117b2..efb709f 100644 --- a/releases/v0.5.0.md +++ b/releases/v0.5.0.md @@ -65,11 +65,11 @@ The following are known limitations of this release: * `crio` is not supported - CoCo is not fully integrated with the orchestration ecosystem (Kubernetes, OpenShift) * OpenShift support is not yet complete. - * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/community/issues/53) + * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/confidential-containers/issues/53) * Some commands accessing confidential data, such as `kubectl exec`, may either fail to work, or incorrectly expose information to the host * Container image sharing is not possible in this release * Container images are downloaded by the guest (with encryption), not by the host - * As a result, the same image will be downloaded separately by every pod using it, not shared between pods on the same host. [More info](https://github.com/confidential-containers/community/issues/66) + * As a result, the same image will be downloaded separately by every pod using it, not shared between pods on the same host. [More info](https://github.com/confidential-containers/confidential-containers/issues/66) - The CoCo community aspires to adopting open source security best practices, but not all practices are adopted yet. * We track our status with the OpenSSF Best Practices Badge, which increased from 49% to 64% at the time of this release. * All CoCo repos now have automated tests, including linting, incorporated into CI. diff --git a/releases/v0.6.0.md b/releases/v0.6.0.md index ae60ff1..53995d4 100644 --- a/releases/v0.6.0.md +++ b/releases/v0.6.0.md @@ -46,9 +46,9 @@ The following are known limitations of this release: * `crio` is only supported with `cloud-api-adaptor`. - Complete integration with Kubernetes is still in progress. * OpenShift support is not yet complete. - * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/community/issues/53) + * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/confidential-containers/issues/53) * Some commands accessing confidential data, such as `kubectl exec`, may either fail to work, or incorrectly expose information to the host - * Container images must be downloaded separately (inside guest) for each pod. [More info](https://github.com/confidential-containers/community/issues/66) + * Container images must be downloaded separately (inside guest) for each pod. [More info](https://github.com/confidential-containers/confidential-containers/issues/66) - The CoCo community aspires to adopting open source security best practices, but not all practices are adopted yet. * We track our status with the OpenSSF Best Practices Badge, which remained at 64% at the time of this release. * Vulnerability reporting mechanisms still need to be created. Public github issues are still appropriate for this release until private reporting is established. diff --git a/releases/v0.7.0.md b/releases/v0.7.0.md index 711fa47..fa53af1 100644 --- a/releases/v0.7.0.md +++ b/releases/v0.7.0.md @@ -46,9 +46,9 @@ The following are known limitations of this release: * `crio` is only supported with `cloud-api-adaptor`. - Complete integration with Kubernetes is still in progress. * OpenShift support is not yet complete. - * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/community/issues/53) + * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/confidential-containers/issues/53) * Some commands accessing confidential data, such as `kubectl exec`, may either fail to work, or incorrectly expose information to the host - * Container images must be downloaded separately (inside guest) for each pod. [More info](https://github.com/confidential-containers/community/issues/66) + * Container images must be downloaded separately (inside guest) for each pod. [More info](https://github.com/confidential-containers/confidential-containers/issues/66) - The CoCo community aspires to adopting open source security best practices, but not all practices are adopted yet. * We track our status with the OpenSSF Best Practices Badge, which remained at 64% at the time of this release. * Vulnerability reporting mechanisms still need to be created. Public github issues are still appropriate for this release until private reporting is established. diff --git a/releases/v0.8.0.md b/releases/v0.8.0.md index e2ab019..29ea54b 100644 --- a/releases/v0.8.0.md +++ b/releases/v0.8.0.md @@ -77,7 +77,7 @@ The following are known limitations of this release: * Not all image repositories support encrypted container images. Complete integration with Kubernetes is still in progress. * OpenShift support is not yet complete. - * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/community/issues/53) + * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/confidential-containers/issues/53) * Some commands accessing confidential data, such as `kubectl exec`, may either fail to work, or incorrectly expose information to the host * The CoCo community aspires to adopting open source security best practices, but not all practices are adopted yet. * We track our status with the OpenSSF Best Practices Badge, which improved to 69% at the time of this release. diff --git a/releases/v0.9.0-alpha0.md b/releases/v0.9.0-alpha0.md index bf9cfdc..a2d6d60 100644 --- a/releases/v0.9.0-alpha0.md +++ b/releases/v0.9.0-alpha0.md @@ -65,7 +65,7 @@ The following are known limitations of this release: * Not all image repositories support encrypted container images. * Complete integration with Kubernetes is still in progress. * OpenShift support is not yet complete. - * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/community/issues/53) + * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/confidential-containers/issues/53) * Some commands accessing confidential data, such as `kubectl exec`, may either fail to work, or incorrectly expose information to the host * The CoCo community aspires to adopting open source security best practices, but not all practices are adopted yet. * We track our status with the OpenSSF Best Practices Badge, which improved to 75% at the time of this release. diff --git a/releases/v0.9.0-alpha1.md b/releases/v0.9.0-alpha1.md index 9afacdd..bf7b7e5 100644 --- a/releases/v0.9.0-alpha1.md +++ b/releases/v0.9.0-alpha1.md @@ -52,7 +52,7 @@ The following are known limitations of this release: * SELinux is not supported on the host and must be set to permissive if in use. * Complete integration with Kubernetes is still in progress. * OpenShift support is not yet complete. - * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/community/issues/53) + * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/confidential-containers/issues/53) * Some commands accessing confidential data, such as `kubectl exec`, may either fail to work, or incorrectly expose information to the host * The CoCo community aspires to adopting open source security best practices, but not all practices are adopted yet. * We track our status with the OpenSSF Best Practices Badge, which remained at 75% at the time of this release. diff --git a/releases/v0.9.0.md b/releases/v0.9.0.md index 63be2d4..37c1443 100644 --- a/releases/v0.9.0.md +++ b/releases/v0.9.0.md @@ -78,7 +78,7 @@ The following are known limitations of this release: * Platform support is rapidly changing * SELinux is not supported on the host and must be set to permissive if in use. * Complete integration with Kubernetes is still in progress. - * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/community/issues/53) + * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/confidential-containers/issues/53) * Some commands accessing confidential data, such as `kubectl exec`, may either fail to work, or incorrectly expose information to the host * The CoCo community aspires to adopting open source security best practices, but not all practices are adopted yet. * We track our status with the OpenSSF Best Practices Badge, which remained at 75% at the time of this release.