Charles Moulliard

Here is what crictl reports ``` [root@test1-master-0 core]# crictl images IMAGE TAG IMAGE ID SIZE k8s.gcr.io/pause 3.1 da86e6ba6ca19 747kB quay.io/coreos/etcd v3.3.10 643c21638c1c9 39.7MB quay.io/coreos/kube-client-agent 36c62ccd7b16b522450c61e96fc556b217ee24f5 b02de22ff740f 33.8MB quay.io/openshift-release-dev/ocp-release d0bc83da1db0c 292MB...

If I try to create a pod then it fails with this error ``` [root@test1-master-0 core]# crictl runp pod-config.json FATA[0000] run pod sandbox failed: rpc error: code = Unknown desc...

The workaround is to create another tanzu secret with the registry credentials and to specify it within the tap config file for the buildservice to avoid to use the shared...

> cannot push the image as the CA Certificate of the private container repository is not mounted as volume and used part of the following command > > ``` >...

Workaround is to install the certificate manager, create a ClusterIssuer (= selfsigned) and let the certificate manager to generate the proper TLS secret including ca.crt, tls.crt, tls.key ``` helm repo...

As the S2I Build process relies on a specific version of the openjdk-1.8 docker image [1], then such version info should also be included within that file. This number should...

> we need here Label added to the project/namespace -> `oc label namespace default istio-injection=enabled`

> Are they fixed-value labels? Or do they need dynamic values? We don't need dynamic values for the moment but fixed-values. Due to the time constraint to have such feature...

> Would it be okay to set those labels on all/some top-level/important objects we create (DeploymentConfig, Service, Route etc) or would we need some kind of system to specifically specify...

> understand what it does As the `launcher` tool is part of our strategy to help developers to develop their `cloud native applications`, a certain level of knowledge about `kubernetes`...