The Makefile is even more generic now, clean, and easy to interact with
and extend.
The main targets are: build, build-containers, push-containers
Signed-off-by: Roy Golan <rgolan@redhat.com>
Motivation:
I want a CI pipeline to get the list of built containers, pull them by
version and run system tests on it.
Modification
First improved the Makefile to use pattern rules so its easy to get
evertyhing under one push target, and in there write every container
pushed into a containers-artifacts.list file.
Finally copying this file the EXPORTED_ARTIFACTS dir
Signed-off-by: Roy Golan <rgolan@redhat.com>
This patch moves the mono-repo under rgolangh to here as
ovirt-cloudprovider.
- Makefile
- add build
- add container
- add rpm
- Compile against k8s 1.11 api (should be compatible with 1.10)
Signed-off-by: Roy Golan <rgolan@redhat.com>
Since the provisioner runs in a container we can use a config map to
hold ovirt details. This would be translated into a file in the
container using the pod spec definition.
First create the config map file:
```
cat ovirt-configmap
url=https://hostname:8443/ovirt-engine/api
username=admin@internal
password=pass
insecure=false
cafile=
```
On k8s master, create the config map, name it 'ovirt' and map it to
'connection' key:
```
kubectl create configmap ovirt
--from-file=connection=ovirt-configmap
```
In the provisioner pod spec, map the config map to a file using a
volume:
```
cat pod-provisioner
apiVersion: v1
metadata:
name: ovirt-provisioner
spec:
containers:
- name: ovirt-provisioner
image: rgolangh/ovirt-provisioner:v0.1
securityContext:
imagePullPolicy: "IfNotPresent"
volumeMounts:
- name: config-volume
mountPath: /etc
volumes:
- name: config-volume
configMap:
name: ovirt
items:
- key: connection
path: ovirt-api.conf
```
Signed-off-by: Roy Golan <rgolan@redhat.com>
