mirrors/node-feature-discovery
1
0
Fork 0
mirror of https://github.com/kubernetes-sigs/node-feature-discovery.git synced 2024-12-14 11:57:51 +00:00
Code Activity
node-feature-discovery/Dockerfile

25 lines
700 B
Text
Raw Normal View History

Utilize multi-stage build to reduce docker image size This reduces the size of the Docker image from ca. 1.2GB down to about 750MB. Also, move unit tests from .travis.yml to Dockerfile. Final production image is not able to run unit tests anymore, as sources are missing from there.
2018-05-28 10:47:56 +00:00
# Build node feature discovery
Migrate from glide to dep Glide is not actively developed anymore, and, its documentation recommends migrating to dep. Also, dep is widely used in other k8s projects. Migrating to dep dramatically reduces the size of the populated vendor/ directory from 75MB down to about 20MB.
2018-11-07 10:39:09 +00:00
FROM golang:1.10 as builder
Fixed vulnerabilities in Docker image. - Updated to debian testing (stretch). - Updated to go v1.7. - Added .dockerignore file.
2016-09-20 17:42:00 +00:00
Import from sigs.k8s.io/node-feature-discovery
2018-11-28 12:30:03 +00:00
ADD . /go/src/sigs.k8s.io/node-feature-discovery
1. Enabled RDT discovery. 2. Updated the ds to a job for node labelling. 3. Added script to run a job in each node. 4. Updated Readme.
2016-07-12 00:30:49 +00:00
Import from sigs.k8s.io/node-feature-discovery
2018-11-28 12:30:03 +00:00
WORKDIR /go/src/sigs.k8s.io/node-feature-discovery
1. Enabled RDT discovery. 2. Updated the ds to a job for node labelling. 3. Added script to run a job in each node. 4. Updated Readme.
2016-07-12 00:30:49 +00:00
Fix to report the correct version inside container. - Used build args to pass the correct version.
2016-12-09 19:32:39 +00:00
ARG NFD_VERSION
enable nfd framework on Arm64 platform currently, nfd framework can't be work on Arm64 platform. Fix points: 1, removed rdt on Arm64 platform 2, optimized the code related to multi-arch Change-Id: If605041f6d2243ae2afb3248edbf102083c6dcb4 Signed-off-by: Bin Lu <bin.lu@arm.com> Jira: ENTOS-432
2017-12-20 06:51:56 +00:00
Migrate from glide to dep Glide is not actively developed anymore, and, its documentation recommends migrating to dep. Also, dep is widely used in other k8s projects. Migrating to dep dramatically reduces the size of the populated vendor/ directory from 75MB down to about 20MB.
2018-11-07 10:39:09 +00:00
RUN go get github.com/golang/dep/cmd/dep
RUN dep ensure
Automatically determine git version for labels. - Added git version to published labels. - Minor formatting fix in job template. - Added .travis.yml and added build status image link to README. - Added .gitignore.
2016-07-14 21:17:27 +00:00
RUN go install \
Move version information into a separate module
2019-01-10 16:02:53 +00:00
-ldflags "-s -w -X sigs.k8s.io/node-feature-discovery/pkg/version.version=$NFD_VERSION" \
Split NFD into client and server Refactor NFD into a simple server-client system. Labeling is now done by a separate 'nfd-master' server. It is a simple service with small codebase, designed for easy isolation. The feature discovery part is implemented in a 'nfd-worker' client which sends labeling requests to nfd-server, thus, requiring no access/permissions to the Kubernetes API itself. Client-server communication is implemented by using gRPC. The protocol currently consists of only one request, i.e. the labeling request. The spec templates are converted to the new scheme. The nfd-master server can be deployed using the nfd-master.yaml.template which now also contains the necessary RBAC configuration. NFD workers can be deployed by using the nfd-worker-daemonset.yaml.template or nfd-worker-job.yaml.template (most easily used with the label-nodes.sh script). Only nfd-worker currently support config file or options. The (default) NFD config file is renamed to nfd-worker.conf.
2019-01-11 13:55:28 +00:00
./cmd/*
RUN install -D -m644 nfd-worker.conf.example /etc/kubernetes/node-feature-discovery/nfd-worker.conf
1. Enabled RDT discovery. 2. Updated the ds to a job for node labelling. 3. Added script to run a job in each node. 4. Updated Readme.
2016-07-12 00:30:49 +00:00
Fix unit tests after master-worker split Refactor old tests and add tests for new functions. Add 'test' target in Makefile.
2019-01-23 08:15:47 +00:00
RUN make test
Utilize multi-stage build to reduce docker image size This reduces the size of the Docker image from ca. 1.2GB down to about 750MB. Also, move unit tests from .travis.yml to Dockerfile. Final production image is not able to run unit tests anymore, as sources are missing from there.
2018-05-28 10:47:56 +00:00
# Create production image for running node feature discovery
Use Debian strecth-slim as a base for the producion Docker image To cut the image size further, down to about 75MB. We use Debian strecth-slim as the base for the production image as golang docker images use stretch as their base.
2018-05-28 12:41:32 +00:00
FROM debian:stretch-slim
Utilize multi-stage build to reduce docker image size This reduces the size of the Docker image from ca. 1.2GB down to about 750MB. Also, move unit tests from .travis.yml to Dockerfile. Final production image is not able to run unit tests anymore, as sources are missing from there.
2018-05-28 10:47:56 +00:00
Add config file support Support yaml/json based config file for nfd. This commit does not add any actual consumers for the config file, yet. By default, nfd tries to read /etc/kubernetes/node-feature-discovery/node-feature-discovery.conf. This can be changed by specifying the --config command line flag.
2018-07-06 11:11:07 +00:00
COPY --from=builder /etc/kubernetes/node-feature-discovery /etc/kubernetes/node-feature-discovery
Split NFD into client and server Refactor NFD into a simple server-client system. Labeling is now done by a separate 'nfd-master' server. It is a simple service with small codebase, designed for easy isolation. The feature discovery part is implemented in a 'nfd-worker' client which sends labeling requests to nfd-server, thus, requiring no access/permissions to the Kubernetes API itself. Client-server communication is implemented by using gRPC. The protocol currently consists of only one request, i.e. the labeling request. The spec templates are converted to the new scheme. The nfd-master server can be deployed using the nfd-master.yaml.template which now also contains the necessary RBAC configuration. NFD workers can be deployed by using the nfd-worker-daemonset.yaml.template or nfd-worker-job.yaml.template (most easily used with the label-nodes.sh script). Only nfd-worker currently support config file or options. The (default) NFD config file is renamed to nfd-worker.conf.
2019-01-11 13:55:28 +00:00
COPY --from=builder /go/bin/nfd-* /usr/bin/
Copy permalink