History

Walter Fender 99156b5bdc Turn on CCM in kube-up when cloudprovider=external Currently if we disable cloud provider by the following CLOUD_PROVIDER_FLAG=external KUBE_FEATURE_GATES=DisableCloudProviders=true,DisableKubeletCloudCredentialProviders=true we can no longer schedule workloads due to taints and a lack of node configuration. This pulls a CCM image from K/cloud-provider-gcp to run tests. This is a pre-step for taking the above feature gates to beta. It does not address the last known good dependency issue. Specifically the CCM image is built on top of client-go and staging. However this image will be an "old" verison of those libraries. So it does not test if those libraries work in the CCM. Fix shellcheck errors. Add CCM_FEATURE_GATES for testing. Switching to extended regex from perl regex. Adding instrumentation to cluster configuration. Improved regex to not greedily get key-value pairs. Fixed issue with error on regex no line match. Switch credentialprovider version to v1alpha1		2022-11-03 10:38:23 -07:00
..
addon-manager	Move from k8s.gcr.io to registry.k8s.io	2022-05-31 10:16:53 -04:00
calico-policy-controller	cleanup psp related rbac in cluster addons	2022-10-31 11:29:20 +08:00
cloud-controller-manager	Turn on CCM in kube-up when cloudprovider=external	2022-11-03 10:38:23 -07:00
cluster-loadbalancing	Move from k8s.gcr.io to registry.k8s.io	2022-05-31 10:16:53 -04:00
device-plugins/nvidia-gpu	Move from k8s.gcr.io to registry.k8s.io	2022-05-31 10:16:53 -04:00
dns	Update to latest kubedns and nodelocaldns images.	2022-10-13 14:48:37 +02:00
dns-horizontal-autoscaler	Move from k8s.gcr.io to registry.k8s.io	2022-05-31 10:16:53 -04:00
fluentd-gcp	Move from k8s.gcr.io to registry.k8s.io	2022-05-31 10:16:53 -04:00
ip-masq-agent	cleanup psp related rbac in cluster addons	2022-10-31 11:29:20 +08:00
kube-proxy	Check in OWNERS modified by update-yamlfmt.sh	2021-12-09 21:31:26 -05:00
metadata-agent	cleanup psp related rbac in cluster addons	2022-10-31 11:29:20 +08:00
metadata-proxy	cleanup psp related rbac in cluster addons	2022-10-31 11:29:20 +08:00
metrics-server	Move from k8s.gcr.io to registry.k8s.io	2022-05-31 10:16:53 -04:00
node-problem-detector	cleanup psp related rbac in cluster addons	2022-10-31 11:29:20 +08:00
rbac	Add leases permissions to glbc rbac	2022-05-10 15:49:15 -07:00
storage-class	Remove references to openstack and cinder	2022-08-22 16:43:14 -04:00
volumesnapshots	Update sidecar controllers to latest versions in the e2e	2022-09-29 22:13:11 +05:30
OWNERS	Check in OWNERS modified by update-yamlfmt.sh	2021-12-09 21:31:26 -05:00
README.md	Removed broken link to Analytics	2020-08-13 16:03:37 -04:00

README.md

Legacy Cluster add-ons

For more information on add-ons see the documentation.

Overview

Cluster add-ons are resources like Services and Deployments (with pods) that are shipped with the Kubernetes binaries and are considered an inherent part of the Kubernetes clusters.

There are currently two classes of add-ons:

Add-ons that will be reconciled.
Add-ons that will be created if they don't exist.

More details could be found in addon-manager/README.md.

Cooperating Horizontal / Vertical Auto-Scaling with "reconcile class addons"

"Reconcile" class addons will be periodically reconciled to the original state given by the initial config. In order to make Horizontal / Vertical Auto-scaling functional, the related fields in config should be left unset. More specifically, leave replicas in ReplicationController / Deployment / ReplicaSet unset for Horizontal Scaling, leave resources for container unset for Vertical Scaling. The periodic reconcile won't clobbered these fields, hence they could be managed by Horizontal / Vertical Auto-scaler.

Add-on naming

The suggested naming for most of the resources is <basename> (with no version number). Though resources like Pod, ReplicationController and DaemonSet are exceptional. It would be hard to update Pod because many fields in Pod are immutable. For ReplicationController and DaemonSet, in-place update may not trigger the underlying pods to be re-created. You probably need to change their names during update to trigger a complete deletion and creation.