Closed jromero closed 4 years ago
Is there any sort of versioning associated with the template? Maybe that's something we should do (if possible).
I was thinking about this... We could create a yaml file per platform API version (or keep older versions in a directory). Otherwise I can't think of a versioning mechanism since it's not our repository.
kubectl config current-context
should be docker-desktop
docker run --detach -p5000:5000 registry:2
"insecure-registries" : ["localhost:5000"]
> Apply & Restartkubectl apply --filename https://storage.googleapis.com/tekton-releases/pipeline/latest/release.yaml
kubectl apply -f ./buildpacks-v3.yaml
<your external ip>:5000/some-output-image
kubectl apply -f <path to task run yaml>
docker pull localhost:5000/some-output-image
To test persistent cache:
mkdir <some dir>
chmod 777 <some dir>
kubectl apply -f <path to volume yaml>
kubectl apply -f https://k8s.io/examples/pods/storage/pv-claim.yaml
kubectl apply -f <path to task run yaml>
cc @micahyoung
@natalieparellano Was this taken care of?
Yep!
Update tekton template to adhere to Platform API version 0.2.
Additional Considerations
Acceptance Criteria
AC1. Platform API verification
Notes
Relates to:
Blocked by: