cbi
cbi copied to clipboard
Container Builder Interface for Kubernetes with support for several backends (Docker, BuildKit, Buildah, kaniko, img, Google Cloud Container Builder, Azure Container Registry Build, OpenShift Source-t...
After installing cbi in my cluster, I configured the following buildjob. ``` apiVersion: cbi.containerbuilding.github.io/v1alpha1 kind: BuildJob metadata: name: django-s2i spec: registry: target: registry.example.com/django/django-s2i:1.0 push: true language: kind: S2I s2i: baseImage:...
This is awesome. Can you explain how build and image pull caching can work with cbi? How can I configure one or more of the build tools, e.g. docker, to...
Deployed the following on AKS, 1.11.5 with RBAC: kubectl apply -f https://raw.githubusercontent.com/containerbuilding/cbi/master/cbi-latest.yaml Response: namespace/cbi-system created error: error validating "https://raw.githubusercontent.com/containerbuilding/cbi/master/cbi-latest.yaml": error validating data: [ValidationError(CustomResourceDefinition.status): missing required field "conditions" in io.k8s.apiextensions-apiserver.pkg.apis.apiextensions.v1beta1.CustomResourceDefinitionStatus, ValidationError(CustomResourceDefinition.status):...
It would be usefull to be able to specify multiple context sources. With that we could setup a build which pulls its dockerfile and main application from git but additionally...
When the registry secret does not exist, job pods stucks at `PodInitializing` without human-readable error. It would be better to validate the secret name on CBI controller.
https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/#handling-pod-and-container-failures
maybe like ```yaml apiVersion: cbi.containerbuilding.github.io/v1alpha1 kind: FlexContextProvider metadata: name: foo labels: mediaType: application/tar+gzip spec: template: spec: containers: - name: foo commands: ["cat", "a.tgz"] --- apiVersion: cbi.containerbuilding.github.io/v1alpha1 kind: BuildJob spec: context:...
Challenge: how to set (kind of) `batch/v1.Job` annotations from the job itself?
* Kubernetes labels? * Bidirectional gRPC?