In both directories, 'user-regular1' and 'user-regular2' are member of the 'k8s-users' group, 'user-admin' is member of 'k8s-admins' group.
For Active Direcoty, 'user-bind' is a simple user which is member of the default 'Domain Users' group in Active Directory. Hence, we can use it to authenticate because has read-only access to Active Directory.
The mail attribute is used to create the RBAC rules.
These commands must be run on all the masters
# mkdir /etc/systemd/system/kube-controller-manager.service.d
# cat > /etc/systemd/system/kube-controller-manager.service.d/override.conf<<EOF
[Service]
ExecStart=
ExecStart=/usr/bin/hyperkube controller-manager \\
This procedure takes into account Prometheus Operator
has been installed using the manifests provided in
prometheus-operator/contrib/kube-prometheus/manifests/ on
https://github.com/coreos/prometheus-operator.git
This procedure is based on this documentation
We can use the ngx_stream_module module (available since version 1.9.0) in order to use
TCP load balancing. In this mode, nginx will just forward the tcp packets the masters.
/!\ The Open Source version of Nginx only allows one to
use passive health checks so therefore using this configuration
is only to consider in a PoC. The main issue with passive
health-checks is that nginx will mark a node as unresponsive
and not distribute traffic only after a failed request.
based from https://developers.redhat.com/blog/2016/09/13/running-systemd-in-a-non-privileged-container/
Create container image:
FROM opensuse/tumbleweed:latest
RUN zypper install -y systemd systemd-sysvinit
CMD ["/sbin/init"]
| --- | |
| apiVersion: apps/v1 | |
| kind: Deployment | |
| metadata: | |
| generation: 1 | |
| labels: | |
| app: source-ip-app | |
| name: source-ip-app | |
| namespace: default | |
| spec: |