In an earlier post, Installing Harbor with Helm, I described in detail how to install Ingress and Harbor and finally push an image successfully. There the domain was publicly reachable and the certificate was issued by a certificate authority. In an intranet environment, however, we need to use an internal domain name for access.

1. Installing the Base Environment Install Kubernetes Reference link: Install a Kubernetes Cluster Using Kubeadm . It is worth noting that Kubeflow is not compatible with every version of Kubernetes, see system-requirements. 1 2 3 4 kubectl version Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.12", GitCommit:"e2a822d9f3c2fdb5c9bfbe64313cf9f657f0a725", GitTreeState:"clean", BuildDate:"2020-05-06T05:17:59Z", GoVersion:"go1.12.17", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.

1. Multi-Stage Builds Compiling a project requires a set of specific tools, but those tools are not needed at runtime. To reduce the image size, you can build in stages. Build in the first stage, then carry the compiled output into the next stage to produce a smaller image. 1 2 3 4 5 6 7 8 9 10 11 FROM golang:1.

I wrote about this in an earlier post, How to Install a GPU Driver on CentOS. This one looks at how to run TensorFlow with Docker. 1. Check Which TensorFlow Version the Current CPU Supports On a CPU that does not support AVX instructions, running TensorFlow > 1.15 fails with Illegal instruction (core dumped).

Here we take clearing the entire commit history of the main branch as the example. Switch to the main branch 1 git checkout main Create a clean branch 1 git checkout --orphan new_main Commit all files 1 2 git add -A git commit -m "msg" Delete the main branch 1 git branch -D main Rename the new branch to main 1 git branch -m main Force push to the remote repository 1 git push -f origin main