github/kubernetes
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
e6b5b076b8
kubernetes/cluster/addons/addon-manager
History
Kubernetes Submit Queue 1d323adade Merge pull request #34361 from jessfraz/remove-docker-tag-f 
Automatic merge from submit-queue

remove all instances of docker tag -f

<!--  Thanks for sending a pull request!  Here are some tips for you:
1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md
2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md
3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes
-->

**What this PR does / why we need it**: There is no flag `-f` for newer versions of `docker tag`

**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #

**Special notes for your reviewer**:

**Release note**:
<!--  Steps to write your release note:
1. Use the release-note-* labels to set the release note state (if you have access) 
2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. 
-->
2016-10-17 19:16:56 -07:00
..
Dockerfile Remove "All rights reserved" from all the headers. 2016-06-29 17:47:36 -07:00
kube-addons.sh Upgrade addon-manager with kubectl apply 2016-10-11 16:22:02 -07:00
Makefile Merge pull request #34361 from jessfraz/remove-docker-tag-f 2016-10-17 19:16:56 -07:00
namespace.yaml run kube-addon-manager in a pod 2016-05-06 11:01:06 -07:00
README.md ConfigMap added to kube addon manager. 2016-07-11 13:54:18 +01:00

README.md

addon-manager

The addon-manager periodically checks for Kubernetes manifest changes in the /etc/kubernetes/addons directory, and when there's a new or changed addon, the addon-manager automatically kubectl creates it.

It supports ReplicationControllers, Deployments, DaemonSets, ConfigMaps, Services, PersistentVolumes and PersistentVolumeClaims.

The addon-manager is built for multiple architectures.

How to release

  1. Change something in the source
  2. Bump VERSION in the Makefile
  3. Bump KUBECTL_VERSION in the Makefile if required
  4. Build the amd64 image and test it on a cluster
  5. Push all images
# Build for linux/amd64 (default)
$ make push ARCH=amd64
# ---> gcr.io/google-containers/kube-addon-manager-amd64:VERSION
# ---> gcr.io/google-containers/kube-addon-manager:VERSION (image with backwards-compatible naming)

$ make push ARCH=arm
# ---> gcr.io/google-containers/kube-addon-manager-arm:VERSION

$ make push ARCH=arm64
# ---> gcr.io/google-containers/kube-addon-manager-arm64:VERSION

$ make push ARCH=ppc64le
# ---> gcr.io/google-containers/kube-addon-manager-ppc64le:VERSION

If you don't want to push the images, run make or make build instead

Analytics