Original Request from Charter: CaaS control plane shall provide curated platform(JVM, NodeJS, Python, Go) images
This test case demonstrates a user submitting an "Image" resource and allowing Tanzu Build Service build the image and push to a registry using curated buildpacks that are consistently patched for security and best-practice
- Completion of SC01-TC01, SC01-TC02, SC02-TC07
- vSphere Administrator console and user credentials
- Tanzu Build Service installed and running in Shared Services cluster
- Have kpack CLI installed
- Image Repo installed - Harbor installed with Project/Repo
- Git CLI
-
switch kubecontext to build service cluster
-
kubeapply image manifest - yaml file in directory (spring-petclinic)
-
check image build logs
-
check harbor for image
-
Change context to the kubernetes cluster where Tanzu Build Service is installed
-
Create a new repository called
microservices-demo
for the images to live in Harbor. For simplicity sake, we will make this a public repo -
Create the registry secret for the service account to publish images to your Harbor registry. (We will use the kpack helper)
kp secret create harbor-credentials --registry $HARBOR_HOSTNAME --registry-user $HARBOR_USER
-
Clone the microservices-demo repo
git clone -b tbs https://github.com/logankimmel/microservices-demo.git && cd microservices-demo
-
Replace the existing harbor registry with your Harbor registry
sed -i 's/harbor.vmw.binbytes.io/${HARBOR_HOSTNAME}/g' tbs-build.yaml
-
Submit build manifest to Tanzu Build Service
kubectl apply -f tbs-build.yaml
-
Check status of image builds
kp image list
-
Obvserve builds
kp build list
-
Inspect logs on a build
kp build logs adservice
-
Once an image has completed the build, check Harbor registry for the newly created image
- [ ] Pass
- [ ] Fail
Return to Test Cases Inventory