HDDS-872 we added Dockerfile and skaffold definition to run dev builds on kubernetes. But it would be great to include example k8s resource definitions helping the deployment of ozone to any kubernetes cluster.
In this patch I will
1. Add k8s resources files to the release tar file to deploy basic ozone cluster
2. Add Dockerfile to the release tar file to create custom ozone image any time
3. Add additional maven profiles to build and push development docker images.
4. We don't need skaffold any more as the maven based approach is more flexible (we can support multiple k8s definitions)
To easily support multiple type of configuration (simple ozone, minikube, csi) we need a basic set of k8s resources files and additional transformations to generate the ready-to-use files for each specific use-cases.
The easiest way to do this is adopting the existing structure from https://github.com/flokkr/k8s and use https://github.com/elek/flekszible tool. But the tool itself is not required at runtime as we generate all the required k8s resources files during the development and add the results to the version control.