Florian JUDITH fjudith

https://concourse-ci.org/generic-oauth.html

CONCOURSE_OAUTH_DISPLAY_NAME=oauth
CONCOURSE_OAUTH_CLIENT_ID=concourse
CONCOURSE_OAUTH_CLIENT_SECRET: <keycloak client secret>
CONCOURSE_OAUTH_AUTH_URL=https://keycloak.example.com/auth/realms/<realm name>/protocol/openid-connect/auth
CONCOURSE_OAUTH_TOKEN_URL=https://keycloak.example.com/auth/realms/<realm name>/protocol/openid-connect/token
CONCOURSE_OAUTH_USERINFO_URL=https://keycloak.example.com/auth/realms/<realm name>/protocol/openid-connect/userinfo

apt-get update -yqq && \
apt-get install -yqq php-common php-cli php-xml php-sqlite3 && \
cd /tmp && \
curl -L https://phoronix-test-suite.com/releases/phoronix-test-suite-8.6.1.tar.gz | tar -xvzf - && \
cd phoronix-test-suite && \
./install-sh && \
phoronix-test-suite list-suites &amp;&amp; \

The current boot2docker iso image contains bugs related to vmxnet3 support. It is required to use an alternative image in order to fix this issue.

docker-machine create -d vmwareworkstation --vmwareworkstation-boot2docker-url=https://github.com/boot2docker/boot2docker/releases/download/v18.09.1/boot2docker.iso --vmwareworkstation-memory-size="4096" --vmwareworkstation-cpu-count "2" default

https://stackoverflow.com/questions/48993286/is-it-possible-to-route-traffic-to-a-specific-pod?rq=1

You can guarantee session affinity with services, but not as you are describing. So, your customers 1-1000 won't use pod-1, but they will use all the pods (as a service makes a simple load balancing), but each customer, when gets back to hit your service, will be redirected to the same pod.

Note: always within time specified in (default 10800):

H2O + Kubeflow/Kubernetes How-To

Introduction

Ce guide est une transposition du billet de Nicholas PNG publié le 29 Mars 2018 sur le blog h2o.ai dans la solution coreos-kubernetes

https://blog.h2o.ai/2018/03/h2o-kubeflow-kubernetes-how-to/

Attention: Ksonnet est instable sur Git-Bash pour Windows. Il est recommandé d'exécuter les étapes de ce guide dans WSL (Windows Subsystem for Linux).

Guide de mise en oeuvre de Wordpress avec Istio

Environnement

Wordpress Version: 4.9.4 (https://github.com/fjudith/docker-wordpress)
Istio Version: 0.6.0 (https://github.com/istio/istio)
Kubernetes Version: 1.9.3 (https://github.com/fjudith/coreos-kubernetes)
Operating System Version: CoreOS Stable (vagrant/vmware workstation & vagrant /virtualbox)
Network CNI: flannel
Storage: local

Open an Putty/SSH session as to the host dedicated to run portainer root user, then execute the following command line.

This required requires access to docker.sock

docker run -d --privileged -p 9000:9000 -v /var/run/docker.sock:/var/run/docker.sock -v portainer-data:/data --name 'portainer' --restart on-failure portainer/portainer

	apiVersion: v1
	kind: Namespace
	metadata:
	name: gitlab
	---
	apiVersion: rbac.authorization.k8s.io/v1
	kind: Role
	metadata:
	name: gitlab-runner
	namespace: gitlab

	#!/usr/bin/env bash

	git branch -r \| grep -v '\->' \| while read remote; do git branch --track "${remote#origin/}" "$remote"; done
	git fetch --all
	git pull --all