| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Created by command:
/usr/bin/tito tag --accept-auto-changelog --use-version=3.6.86
|
|\
| |
| | |
Updating registry-console version to be v3.6 instead of 3.6
|
| | |
|
|\ \
| | |
| | | |
Merged by openshift-bot
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This commit allows to specify imageConfig.format specifically for master
or for nodes.
One use case of this could be if you want to use customer builder
images. In this case imageConfig.format only needs to be changed in the
master-config.yml but not in the node-config.yml.
|
|\ \ \
| | | |
| | | | |
openshift_logging: increasing *_elasticsearch_* default CPU and memory
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Lower memory requirements in fedora-ci jobs
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
Updating python-passlib assert
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Created by command:
/usr/bin/tito tag --accept-auto-changelog --use-version=3.6.85
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Merged by openshift-bot
|
| |/ / / / |
|
|\ \ \ \ \
| |_|/ / /
|/| | | | |
Verify memory and disk requirements before install
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Added indicator to check result for why that check was skipped.
Note that currently the user will only see it with ansible-playbook -vv
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Customized the error summary to depend on the intent of the playbook run.
Ensured output makes sense when failures are unrelated to running checks.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Example usage:
$ ansible-playbook -i hosts playbooks/byo/config.yml -e
openshift_disable_check=memory_availability,disk_availability
Or add the variable to the inventory / hosts file.
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Merged by openshift-bot
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Signed-off-by: Jose A. Rivera <jarrpa@redhat.com>
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Created by command:
/usr/bin/tito tag --accept-auto-changelog --use-version=3.6.84
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Merged by openshift-bot
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | | |
Signed-off-by: Jose A. Rivera <jarrpa@redhat.com>
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Created by command:
/usr/bin/tito tag --accept-auto-changelog --use-version=3.6.83
|
|\ \ \ \ \ \
| |_|_|/ / /
|/| | | | | |
Merged by openshift-bot
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
127.0.0.1 does not end up in "ansible_all_ipv4_addresses" and should
be considered valid.
For example, a hostname could be resolving to a public address that is
not bound to the actual server.
Or the host could resolve to 127.0.0.1 from the perspective of
the host since the hostname is set up in /etc/hosts.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Created by command:
/usr/bin/tito tag --accept-auto-changelog --use-version=3.6.82
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Merged by openshift-bot
|
| | | | | | | |
|
| | | | | | | |
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Add Kibana readiness probe, stop using `oc scale` for cluster start
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
In order to ensure that the Kubernetes machinery can determine when the
Kibana Pods are becoming ready, we need to add a readiness probe to the
Containers that make up those pods. The Kibana readiness probe simply
hits the base URL at `http://localhost:5601/` and expects a 200.
Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
|
| |/ / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
When we currently create the set of logging `DeploymentConfig`s, we
create them with zero desired replicas. This causes the deployment to
immediately succeed as there is no work to be done. This inhibits our
ability to use nice CLI UX features like `oc rollout status` to monitor
the logging stack deployments. Instead, we should can create the configs
with the correct number of replicas in the first place and stop using
`oc scale` to bring them up after the fact.
Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Merged by openshift-bot
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Those tests spin up docker images and remove them at the end.
The removal seems to fail randomly on test systems.
Changed the removal task to ignore errors.
|
|\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Merged by openshift-bot
|
| | |_|_|_|_|_|/
| |/| | | | | | |
|
| |_|_|_|_|/ /
|/| | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Created by command:
/usr/bin/tito tag --accept-auto-changelog --use-version=3.6.80
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Merged by openshift-bot
|