Skip to content
This repository has been archived by the owner on Sep 15, 2022. It is now read-only.

Provide start on containerizing these scripts #1

Open
adamhgriffith-uofu opened this issue Apr 27, 2022 · 1 comment
Open

Provide start on containerizing these scripts #1

adamhgriffith-uofu opened this issue Apr 27, 2022 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@adamhgriffith-uofu
Copy link

Create a starting position with a CheckMK agent base image.

@adamhgriffith-uofu adamhgriffith-uofu added the enhancement New feature or request label Apr 27, 2022
@adamhgriffith-uofu adamhgriffith-uofu self-assigned this Apr 27, 2022
@adamhgriffith-uofu
Copy link
Author

adamhgriffith-uofu commented Apr 27, 2022

@gcarcassi I grabbed what I did for https://github.com/slateci/slate-server-scripts and added a CheckMK agent.

The README.md on the associated feature branch (see on right) describes how I was originally setting up a local development environment.

The "release" flavor of the image would be created and pushed to OSG Harbor using a command like:

$ docker build --file ./resources/docker/Dockerfile --target release-stage --tag hub.opensciencegrid.org/slate/slate-checkmk-scripts:github-26 .
...
$ docker push hub.opensciencegrid.org/slate/slate-checkmk-scripts:github-26

And then like you said a Kubernetes a Deployment/Job/CronJob could load the container:

...
spec:
  containers:
    - name: worker
      image: "{{ $.Values.harbor.hostname }}/{{ $.Values.harbor.projectID }}/slate-checkmk-scripts:{{ $.Values.dockerImageTag }}"
     imagePullPolicy: IfNotPresent
     command:
       - /slate/scripts/{{ .filename }}
    env:
      - name: SLATE_API_CONF
      ...
...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant