I believe that to manage the builds / deploys follows by the same Jenkins you can use Blue Ocean theme it's more friendly and you can track CI/CD.
For infrastructure I suggest use Rundeck (Cron like with web gui) + Ansible + ARA Records Ansible to track the plays.
@Adam Wolski welcome to the SE site!
If the server has enough resources, it's possible. But for example if you need to reboot the machine, or there will be a hardware problem or a crash or hacker attack, all your services and data will go offline/be at risk as the single machine would be a single point of failure. Also, if you serve globally, best service ...
You should be able to use the flag spec.containers.resources.limits.cpu to set your desired state on a deployment.
The official docs here and here have some examples of how to specify this in the yaml. You can set a global default along with min/max limits:
I don't have much experience with Symantec (I don't really like the product).
But searching on Google apparently has some steps to set up, as they don't natively support Kuberentes as an application.
Look if these two articles can help you.
According to the README of the deis/workflow project on GitHub, it is no longer maintained since March 1, 2018.
However, the README indicates that there is a fork, called Hephy Workflow. At the time of writing, this is the first time I heard about Deis and Hephy and I have not worked with these solutions.
Alternatives to these products are OpenShift, ...
Recently Kubernetes started preview work on https://cluster-api.sigs.k8s.io which is meant to be the standard way to solve the way how High Availability clusters are deployed.
The kubeadm tool has also been updated with features to deploy multiple masters since this question was first asked, which help tremendously. With the exception of deploying cloud-...
Your questions in order:
The container not only need to be built, it needs to be in a registry that Kubernetes has access to. If you are using Docker containers (the default), you can push your container to Docker Hub so that Kubernetes can retrieve the image.
They are showing as pending because they do not yet have any containers inside of them. You've ...
You have to push your image in a registry in order to get the deployment working. Kubernetes does not deal with images (i.e. building, pushing...).
Try kubectl describe deployment mojo-deployment, you'll get more informations about why it's pending (surely because it does not know how to get your Docker image).
Based on the error message it seems that the yaml is invalid:
Unsupported value: "IfNotPresent:ef86dfe0b703": supported values:
"Always", "IfNotPresent", "Never"
It seems that IfNotPresent contains some tag and that is unsupported.
According to the log there is something wrong with the Etcd certificate:
Error: client: etcd cluster is unavailable or misconfigured; error #0: x509:
certificate signed by unknown authority
error #0: x509: certificate signed by unknown authority
Please read the documentation how to create etcd certificates again and try to fix it.
You need to first switch to Edge version by going to the
Docker -> Settings -> General tab.
Then, you have to enable the kubernetes.
Open Docker for Windows settings by accessing your system tray and navigate to the Kubernetes tab. Select the checkbox for Enable Kubernetes to start a single-node cluster when starting Docker.