mirror of https://github.com/k3s-io/k3s
![]() Automatic merge from submit-queue (batch tested with PRs 38739, 40480, 40495, 40172, 40393) Use existing ABAC policy file when upgrading GCE cluster When upgrading, continue loading an existing ABAC policy file so that existing system components continue working as-is ``` When upgrading an existing 1.5 GCE cluster using `cluster/gce/upgrade.sh`, an existing ABAC policy file located at /etc/srv/kubernetes/abac-authz-policy.jsonl (the default location in 1.5) will enable the ABAC authorizer in addition to the RBAC authorizer. To switch an upgraded 1.5 cluster completely to RBAC, ensure the control plane components and your superuser have been granted sufficient RBAC permissions, move the legacy ABAC policy file to a backup location, and restart the apiserver. ``` |
||
---|---|---|
.. | ||
mounter | ||
README.md | ||
configure-helper.sh | ||
configure.sh | ||
health-monitor.sh | ||
helper.sh | ||
master-helper.sh | ||
master.yaml | ||
node-helper.sh | ||
node.yaml |
README.md
Container-VM Image
Container-VM Image is a container-optimized OS image for the Google Cloud Platform (GCP). It is primarily for running Google services on GCP. Unlike the open preview version of container-vm, the new Container-VM Image is based on the open source ChromiumOS project, allowing us greater control over the build management, security compliance, and customizations for GCP.