| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
[WIP] When using flannel there are iptables rules that need
to be added as stated here:
https://access.redhat.com/documentation/en-us/reference_architectures/2017/html-single/deploying_red_hat_openshift_container_platform_3.4_on_red_hat_openstack_platform_10/#run_ansible_installer
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1493955
|
|\
| |
| | |
Use "requests" for CPU resources instead of limits
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We now use a CPU request to ensure logging infrastructure pods are
not capped by default for CPU usage. It is still important to ensure
we have a minimum amount of CPU.
We keep the use of the variables *_cpu_limit so that the existing
behavior is maintained.
Note that we don't want to cap an infra pod's CPU usage by default,
since we want to be able to use the necessary resources to complete
it's tasks.
Bug 1501960 (https://bugzilla.redhat.com/show_bug.cgi?id=1501960)
|
|\ \
| | |
| | | |
Fix undefined variable for master upgrades
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Currently, oreg_auth_credentials_replace is undefined
during master upgrades.
This commit ensures this variable is defined during
upgrades.
|
|\ \ \
| | | |
| | | | |
[bz1491399] Adding pre check to verify clusterid is set along with cloudprovider when performing upgrade.
|
| | | |
| | | |
| | | |
| | | | |
performing upgrade.
|
|\ \ \ \
| | | | |
| | | | | |
Check for container runtime prior to restarting when updating system CA trust.
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
bug 1489498. preserve replica and shard settings
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Bug 1503233 - Add liveness and readiness probe checks to ASB deployme…
|
| | | | | | | |
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| |_|_|_|_|_|/
|/| | | | | | |
Initial Kuryr support
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This commit enables deploying Kuryr networking on top of OpenShift in
containers. kuryr-controller is a Deployment and kuryr-cni is deployed
as DaemonSet (container will drop all CNI configuration files).
Co-Authored-By: Antoni Segura Puimedon <celebdor@gmail.com>
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Update service catalog playbook for service-catalog rc1
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | |_|_|_|/ /
| |/| | | | | |
|
| |_|_|_|/ /
|/| | | | |
| | | | | |
| | | | | |
| | | | | | |
We are seeing instances take longer than 5m to become available,
possibly due to GCP infra issues.
|
|\ \ \ \ \ \
| |_|/ / / /
|/| | | | | |
Fix typo in setting prom-proxy memory limit
|
| | |_|_|/
| |/| | |
| | | | |
| | | | | |
bz: https://bugzilla.redhat.com/show_bug.cgi?id=1493368
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
Provisioning updates.
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Fix prometheus role nfs
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Allow for external or internal nfs.
use facts as used for logging and metrics.
Update prometheus-alertmanager image to v0.9.1
|
|\ \ \ \ \ \
| |_|_|_|/ /
|/| | | | | |
Fix missing docker option signature-verification
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Currently, docker 1.12 can be configured to use the
run-time parameter of 'signature-verification'
By default, rpm installation of docker results in
'--signature-verification=false' being added to
OPTIONS in /etc/sysconfig/docker
Currently, openshift-ansible does not preserve that
value. This can cause docker to be unable to pull
images from a previously working source due to a
change in configuration.
This commit adds the option with the default
as provided by the rpm installation.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1502560
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Updating ES proxy image prefix and version to match other components
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Bug 1501768: fix eventrouter nodeSelector padding
|
| | |_|/ / /
| |/| | | | |
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Automatic merge from submit-queue.
cri-o: error out when node is a Docker container
Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1489555
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1489555
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Automatic merge from submit-queue.
Rewire openshift_template_service_broker_namespaces configurable
@ewolinetz
@bparees
|
| | |_|_|/ /
| |/| | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Automatic merge from submit-queue.
Add ability to set node and master imageConfig to latest
Currently, imageConfig.latest is hard-coded to false.
This commit adds an appropriate boolean to enable
setting to true.
Fixes: https://github.com/openshift/openshift-ansible/issues/1422
|
| | |_|/ / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Currently, imageConfig.latest is hard-coded to false.
This commit adds an appropriate boolean to enable
setting to true.
Fixes: https://github.com/openshift/openshift-ansible/issues/1422
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Automatic merge from submit-queue.
Add switch to enable/disable container engine's audit log being stored in elasticsearch
If enabled, tho logs are stored in ES' operations index, accessible only by cluster admins.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
If enabled, tho logs are stored in ES' operations index, accesible only by cluster admins.
|