5
Running two tillers does not make it HA. There is an open issue at the moment.
4
Back when Kubernetes announced the new StatefulSet feature with K8s v1.5 (converting it from the old PetSet name), they put out a really good blog post walking through an example of its usage: https://kubernetes.io/blog/2016/12/statefulset-run-scale-stateful-applications-in-kubernetes/
The first paragraph has a really good description of differentiating ...
3
Based on this Github documentation it is possible to pull a docker image from a private docker registry:
values.yaml
imageCredentials:
name: credentials-name
registry: private-docker-registry
username: user
password: pass
templates/imagePullSecret.yaml
{{- define "imagePullSecret" }}
{{- printf "{\"auths\": {\"%s\": {\"auth\": \"%s\"}}}" .Values....
3
The problem was that nodes, while registered with kubeadm init were providing their private IPs to the cluster master. This caused problems, because master was trying to reach 192.0.*.* addresses which were not resolved as nodes from it's point of view.
I needed to edit /etc/systemd/system/kubelet.service.d/10-kubeadm.conf and specify public IP of the node ...
3
You have found a Kubernetes issue #22770, where there is a workaround mentioned here and it goes like follows:
What you're experiencing is a known issue with k8s where for some operations it expects to be able to resolve your node names in the global DNS.
And suggested a work around would be to:
Add entries to /etc/hosts on the master mapping ...
2
I believe this is an current bug in k3s that upstream DNS is hardcoded to 1.1.1.1. this should be resolved shortly https://github.com/rancher/k3s/issues/53
1
My 2 cents. We have similar requirement like you do. We end up having multiple values files in the form of values-<namespace>.yaml and it should come with the defaults set to values.yaml
We also have some shell scripts to deploy to the namespace. Something like this deploy.sh --namespace app.
It is not without its problem, the number of files are ...
1
Usually to access an external API you can just use its URL. But you can create a Service for it if you like, the type of service should be ExternalName as described in the documentation https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types
1
A service in kubernetes is (mostly) used for internal communication. If you want to access an external resource by domain/ip you can just do so. If you have an IP address and you would like to have some sort of domain connected to it, you could you am service with the external name field set to the up address (we use that for database purposes). An endpoint ...
1
ibuildthecloud9 gave me the right hint. Since the github issue doesn't describe how to midify the dns, I figured it out and want to document it here in case someone need to change it, too. It's stored in the configmap coredns as Corefile:
proxy . 1.1.1.1
You need to replace this by your dns server (192.168.0.19 in my case). It could be done manually using ...
1
Use a docker image within your pipeline that has helm and other tools installed.
To quote the docs:
Pipeline is designed to easily use Docker images as the execution
environment for a single Stage or the entire Pipeline. Meaning that a
user can define the tools required for their Pipeline, without having
to manually configure agents. Practically ...
1
I ended up using stolon for its automatic leader election and fail over handling.
Crunchy Data offers small building blocks so there is a lot of work to do to put them all together while stolon has a ready helm chart.
But I didn't try patroni since stolon worked just fine.
1
You can use helm get manifest <RELEASE_NAME> to fetch the kubernets manifests and you can use helm get values <RELEASE_NAME> to get the values.yaml from the cluster. But I don't think there is any way to get the chart files back. Sorry.
PS: Please replace <RELEASE_NAME> with your release name.
Only top voted, non community-wiki answers of a minimum length are eligible
