gc.ca

// cat : https://www.iana.org/domains/root/db/cat.html
cat

// cc : https://www.iana.org/domains/root/db/cc.html
cc

// cd : https://www.iana.org/domains/root/db/cd.html
// see also: https://www.nic.cd/domain/insertDomain_2.jsp?act=1
cd
gov.cd

// cf : https://www.iana.org/domains/root/db/cf.html
cf

// cg : https://www.iana.org/domains/root/db/cg.html
cg

## **Notable Features**

          with no declared namespace, it's not XHTML, it's just
          bad HTML, unfortunately.
     -->
    <root-XML localName="html"/>
    <root-XML localName="HTML"/>
    <root-XML localName="link"/>
    <root-XML localName="LINK"/>
    <root-XML localName="body"/>
    <root-XML localName="BODY"/>
    <root-XML localName="p"/>
    <root-XML localName="P"/>
    <root-XML localName="script"/>

* Changed ext3/ext4 volume creation to not reserve any portion of the volume for the root user. When creating ext3/ext4 volume, mkfs defaults to reserving 5% of the volume for the super-user (root). This patch changes the mkfs to pass -m0 to disable this setting.

## Known Issues

    * - All containers are now being executed under more restrictive privileges.
    * - Most of the containers now run as non-root user and has the root filesystem set as read-only.
    * - The remaining container running as root only has the minimum Linux capabilities it requires to run.
    * - Privilege escalation has been disabled for all containers.

* Fixes issue where subpath volume content was deleted during orphaned pod cleanup for Local volumes that are directories (and not mount points) on the root filesystem. ([#72291](https://github.com/kubernetes/kubernetes/pull/72291), [@msau42](https://github.com/msau42))

* fix: make azure disk URI as case insensitive...

  - [Known Issues](#known-issues)
    - [CPU and Memory manager are not working correctly for Guaranteed Pods with multiple containers](#cpu-and-memory-manager-are-not-working-correctly-for-guaranteed-pods-with-multiple-containers)
    - [<code>CSIMigrationvSphere</code> feature gate has not migrated to new CRD APIs](#csimigrationvsphere-feature-gate-has-not-migrated-to-new-crd-apis)

* Object quotas are not consistently charged or updated. Specifically, the object count quota does not reliably account for uninitialized objects. Some quotas are charged only when an object is initialized. Others are charged when an object is created, whether it is initialized or not. We plan to fix this issue in a future release.