0.3.0-ol-7-r0 release

This commit is contained in:
Bitnami Bot
2019-10-18 03:48:29 +00:00
parent 7d180158a6
commit a9f4b32b17
4 changed files with 178 additions and 0 deletions

View File

@@ -0,0 +1,20 @@
FROM bitnami/oraclelinux-extras:7-r500
LABEL maintainer "Bitnami <containers@bitnami.com>"
# Install required system packages and dependencies
RUN install_packages ca-certificates wget
RUN wget -nc -P /tmp/bitnami/pkg/cache/ https://downloads.bitnami.com/files/stacksmith/configmap-reload-0.3.0-0-linux-x86_64-ol-7.tar.gz && \
echo "717785c3f49a33aa4f5d6f318aae5d3e5b1ec5527b2f598b79a91a0e2304c1de /tmp/bitnami/pkg/cache/configmap-reload-0.3.0-0-linux-x86_64-ol-7.tar.gz" | sha256sum -c - && \
tar -zxf /tmp/bitnami/pkg/cache/configmap-reload-0.3.0-0-linux-x86_64-ol-7.tar.gz -P --transform 's|^[^/]*/files|/opt/bitnami|' --wildcards '*/files' && \
rm -rf /tmp/bitnami/pkg/cache/configmap-reload-0.3.0-0-linux-x86_64-ol-7.tar.gz
RUN ln -sf /opt/bitnami/configmap-reload/bin/configmap-reload /bin/configmap-reload
ENV BITNAMI_APP_NAME="configmap-reload" \
BITNAMI_IMAGE_VERSION="0.3.0-ol-7-r0" \
PATH="/opt/bitnami/configmap-reload/bin:$PATH"
EXPOSE 8080
WORKDIR /opt/bitnami/configmap-reload
USER 1001
ENTRYPOINT [ "configmap-reload" ]

View File

@@ -0,0 +1,6 @@
version: '2'
services:
configmap-reload:
image: bitnami/configmap-reload:0-ol-7
ports:
- 8080:8080

View File

@@ -0,0 +1,104 @@
# What is ConfigMap Reload?
configmap-reload is a cloud-native tool that watches Kubernetes ConfigMaps and triggers a reload when ConfigMaps are updated.
[https://github.com/jimmidyson/configmap-reload](https://github.com/jimmidyson/configmap-reload)
# TL;DR;
Deploy [ConfigMap Reload](https://github.com/jimmidyson/configmap-reload/blob/master/README.md) on your Kubernetes cluster.
# Why use Bitnami Images?
* Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
* With Bitnami images the latest bug fixes and features are available as soon as possible.
* Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
* All our images are based on [minideb](https://github.com/bitnami/minideb) a minimalist Debian based container image which gives you a small base container image and the familiarity of a leading linux distribution.
* All Bitnami images available in Docker Hub are signed with [Docker Content Trust (DTC)](https://docs.docker.com/engine/security/trust/content_trust/). You can use `DOCKER_CONTENT_TRUST=1` to verify the integrity of the images.
* Bitnami container images are released daily with the latest distribution packages available.
> This [CVE scan report](https://quay.io/repository/bitnami/configmap-reload?tab=tags) contains a security report with all open CVEs. To get the list of actionable security issues, find the "latest" tag, click the vulnerability report link under the corresponding "Security scan" field and then select the "Only show fixable" filter on the next page.
# Why use a non-root container?
Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers [in our docs](https://docs.bitnami.com/containers/how-to/work-with-non-root-containers/).
# How to deploy ConfigMap Reload in Kubernetes?
You can find an example for testing in the file `test.yaml`. To launch this sample file run:
```bash
$ kubectl apply -f test.yaml
```
> NOTE: If you are pulling from a private containers registry, replace the image name with the full URL to the docker image. E.g.
>
> - image: 'your-registry/image-name:your-version'
# Supported tags and respective `Dockerfile` links
> NOTE: Debian 8 images have been deprecated in favor of Debian 9 images. Bitnami will not longer publish new Docker images based on Debian 8.
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/).
* [`0-ol-7`, `0.3.0-ol-7-r0` (0/ol-7/Dockerfile)](https://github.com/bitnami/bitnami-docker-configmap-reload/blob/0.3.0-ol-7-r0/0/ol-7/Dockerfile)
* [`0-debian-9`, `0.3.0-debian-9-r0`, `0`, `0.3.0`, `0.3.0-r0`, `latest` (0/debian-9/Dockerfile)](https://github.com/bitnami/bitnami-docker-configmap-reload/blob/0.3.0-debian-9-r0/0/debian-9/Dockerfile)
* [`0-centos-7`, `0.3.0-centos-7-r0` (0/centos-7/Dockerfile)](https://github.com/bitnami/bitnami-docker-configmap-reload/blob/0.3.0-centos-7-r0/0/centos-7/Dockerfile)
Subscribe to project updates by watching the [bitnami/configmap-reload GitHub repo](https://github.com/bitnami/bitnami-docker-configmap-reload).
# Get this image
The recommended way to get the Bitnami ConfigMap Reload Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/configmap-reload).
```bash
$ docker pull bitnami/configmap-reload:latest
```
To use a specific version, you can pull a versioned tag. You can view the [list of available versions](https://hub.docker.com/r/bitnami/configmap-reload/tags/) in the Docker Hub Registry.
```bash
$ docker pull bitnami/configmap-reload:[TAG]
```
If you wish, you can also build the image yourself.
```bash
$ docker build -t bitnami/configmap-reload:latest 'https://github.com/bitnami/bitnami-docker-configmap-reload.git#master:0/debian-9'
```
# Configuration
Find how to configure ConfigMap Reload in its [official documentation](https://github.com/jimmidyson/configmap-reload/blob/master/README.md).
# Contributing
We'd love for you to contribute to this container. You can request new features by creating an [issue](https://github.com/bitnami/bitnami-docker-configmap-reload/issues), or submit a [pull request](https://github.com/bitnami/bitnami-docker-configmap-reload/pulls) with your contribution.
# Issues
If you encountered a problem running this container, you can file an [issue](https://github.com/bitnami/bitnami-docker-configmap-reload/issues). For us to provide better support, be sure to include the following information in your issue:
- Host OS and version
- Docker version (`docker version`)
- Output of `docker info`
- Version of this container
- The command you used to run the container, and any relevant output you saw (masking any sensitive information)
# License
Copyright (c) 2019 Bitnami
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

View File

@@ -0,0 +1,48 @@
## This is test deployment for Kubernetes platforms.
## This is _not_ intended to be used in production.
##
apiVersion: apps/v1
kind: Deployment
metadata:
labels:
app.kubernetes.io/name: test-configmap-reload
app.kubernetes.io/component: configmap-reload
spec:
replicas: 1
selector:
matchLabels:
app.kubernetes.io/name: test-configmap-reload
app.kubernetes.io/component: configmap-reload
template:
metadata:
labels:
app.kubernetes.io/name: test-configmap-reload
app.kubernetes.io/component: configmap-reload
spec:
containers:
- image: bitnami/configmap-reload
name: configmap-reload
#env:
#- name: BITNAMI_DEBUG
#- value: 0
ports:
- name: configmap-reload-port-8080
containerPort: 8080
protocol: TCP
---
apiVersion: v1
kind: Service
metadata:
name: test-configmap-reload
labels:
app.kubernetes.io/name: test-configmap-reload
app.kubernetes.io/component: configmap-reload
spec:
type: ClusterIP
ports:
- port: 8080
protocol: TCP
targetPort: configmap-reload-port-8080
selector:
app.kubernetes.io/name: test-configmap-reload
app.kubernetes.io/component: configmap-reload