public_git/bitnami-containers
1
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-10-18 01:42:21 +02:00
Code Issues Projects Releases Wiki Activity

[bitnami/cluster-autoscaler] Release 1.26.1-debian-11-r18 (#24874)

Browse Source 
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
2023-02-22 14:51:47 +01:00
committed by GitHub
parent b047c89ada
commit ff710523d7
3 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bitnami/cluster-autoscaler/1/debian-11/Dockerfile
+3 -3
View File
@@ -3,10 +3,10 @@ FROM docker.io/bitnami/minideb:bullseye
ARG TARGETARCH
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
org.opencontainers.image.created="2023-02-20T14:26:22Z" \
org.opencontainers.image.created="2023-02-22T13:35:11Z" \
org.opencontainers.image.description="Application packaged by VMware, Inc" \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="1.26.1-debian-11-r17" \
org.opencontainers.image.ref.name="1.26.1-debian-11-r18" \
org.opencontainers.image.title="cluster-autoscaler" \
org.opencontainers.image.vendor="VMware, Inc." \
org.opencontainers.image.version="1.26.1"
@@ -22,7 +22,7 @@ SHELL ["/bin/bash", "-o", "pipefail", "-c"]
RUN install_packages ca-certificates curl procps
RUN mkdir -p /tmp/bitnami/pkg/cache/ && cd /tmp/bitnami/pkg/cache/ && \
COMPONENTS=( \
"cluster-autoscaler-1.26.1-2-linux-${OS_ARCH}-debian-11" \
"cluster-autoscaler-1.26.1-3-linux-${OS_ARCH}-debian-11" \
) && \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
bitnami/cluster-autoscaler/1/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json
+1 -1
View File
@@ -4,6 +4,6 @@
"digest": "dc39d192fd5c4f37b4a111596c660d072cb4ff8c03453f2d1c238ccc9b1bc78f",
"distro": "debian-11",
"type": "NAMI",
"version": "1.26.1-2"
"version": "1.26.1-3"
}
}
bitnami/cluster-autoscaler/README.md
+2 -2
View File
@@ -31,7 +31,7 @@ Cluster Autoscaler runs on the Kubernetes master node on most K8s cloud offering
Currently, it is possible to run Cluster Autoscaler on:
* **AliCloud**: Consult [Cluster Autoscaler on AliCloud docs](https://github.com/kubernetes/autoscaler/cloudprovider/alicloud/README.md).
* **AliCloud**: Consult [Cluster Autoscaler on AliCloud docs](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/alicloud/README.md).
* **AWS**: Consult [Cluster Autoscaler on AWS docs](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/aws/README.md).
* **Azure**: Consult [Cluster Autoscaler on Azure docs](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/azure/README.md).
* **GCE**: Consult [Cluster Autoscaler on GCE docs](https://kubernetes.io/docs/concepts/cluster-administration/cluster-management#upgrading-google-compute-engine-clusters).
@@ -39,7 +39,7 @@ Currently, it is possible to run Cluster Autoscaler on:
Please note that Cluster Autoscaler a series of permissions/privileges to adjusts the size of the K8s cluster. For instance, to run it on AWS, you need to:
* Provide the K8s worker node which runs the cluster autoscaler with a minimum IAM policy (check [permissions docs](https://github.com/kubernetes/autoscaler/cloudprovider/aws#permissions) for more information).
* Provide the K8s worker node which runs the cluster autoscaler with a minimum IAM policy (check [permissions docs](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler/cloudprovider/aws#user-content-permissions) for more information).
* Create a service account for Cluster Autoscaler's deployment and bind to it some roles and cluster roles that provide the corresponding RBAC privileges.
> NOTE: Find resources to deploy Cluster Autoscaler on AWS in the [aws-examples](./aws-examples) directory.