| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
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
|
| |
| |
| |
| |
| |
| |
| |
| | |
The playbooks/certificate_expiry directory is being moved inside the
openshift-checks tree, and a symlink there is put in place for backwards
compatibility. RPM does not handle this well, so this expands the section
of the specfile that already contains a workaround for this situation to
also handle this move.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We are moving toward having adhoc post-install checks and so the
"preflight" designation needs to be widened.
Updated location to playbooks/byo/openshift-checks, added health check playbook, and updated README.
Also included the certificate_expiry playbooks.
Left behind symlinks and wrappers for existing checks.
To conform with the direction of the rest of the repo, the
openshift-checks playbooks are split into two directories, one under
playbooks/common with the actual invocation and one under
playbooks/byo for entrypoints that are just wrappers for the ones in common.
Because the certificate_expiry playbooks are intended not just to be
functional but to be examples that users modify, I did not split them
similarly. That could happen later after discussion but for now I just
left them whole under byo/openshift-checks/certificate_expiry.
|
| |
| |
| |
| |
| |
| | |
Created by command:
/usr/bin/tito tag
|
|\ \
| | |
| | |
| | |
| | | |
juanvallejo/jvallejo/update-docker-image-availability-check
Merged by openshift-bot
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Merged by openshift-bot
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Merged by openshift-bot
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This change allows for the specification of JSON objects like
lists as parameters to templates.
Signed-off-by: Jose A. Rivera <jarrpa@redhat.com>
|
|\ \ \ \
| |_|_|/
|/| | | |
Merged by openshift-bot
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Removing requirement to pass aws credentials
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Update examples to include metrics deployer version
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Without this we can have a mismatch between the OpenShift version and
the metrics version.
Fixes https://github.com/openshift/origin/issues/13532
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Move etcd upgrade code into role
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Merged by openshift-bot
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Bug 1447019
|
|\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Merged by openshift-bot
|
| | | | | | | | | |
|
|\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
Merged by openshift-bot
|
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
GitHubIdentityProvider provides the ability to authenticate against
GitHub organization teams [1].
This adds the attribute as optional so that users do not get the error
"provider GitHubIdentityProvider contains unknown keys teams".
[1]: https://docs.openshift.com/container-platform/3.5/install_config/configuring_authentication.html#GitHub
|
|\ \ \ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | | |
inventory: rename certificates->certificate in router example
|
|/ / / / / / / / / /
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Per change 9397727e433cbd9bfd865fb5ad773c7b6b4590e8, router replaced
certificates with certificate.
|
|\ \ \ \ \ \ \ \ \ \
| |_|_|_|_|_|_|_|_|/
|/| | | | | | | | | |
Merged by openshift-bot
|
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Updating some files to account for recent changes:
- Commit fbadeb4 moved the location of the Dockerfiles
- playbook2image is now available from the openshift org
- downstream image is building with boto 2.34
Adjusting image build scripts and documentation to match these changes.
|
|\ \ \ \ \ \ \ \ \ \
| |_|_|_|_|_|_|_|_|/
|/| | | | | | | | | |
Merged by openshift-bot
|
| | | | | | | | | | |
|
| |\ \ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
github.com:juanvallejo/openshift-ansible into jvallejo/add-etcd-volume-check
|
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
It was agreed to name role variables as `r_ROLE_NAME_VARIABLE_NAME`. Giving it a try.
|
| | | | | | | | | | | |
|
| | | | | | | | | | | |
|
| |/ / / / / / / / / |
|
| | | | | | | | | | |
|
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
We don't need to convert to int and then to float. Read it as float from the start.
|
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
It has been agreed that we don't use it any longer.
|
| | | | | | | | | | |
|
|\ \ \ \ \ \ \ \ \ \
| |_|_|_|_|_|_|_|/ /
|/| | | | | | | | | |
Fix yamllint problems
|
|/ / / / / / / / /
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
I should've noticed before merging...
|
|\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
add ability to expose Elasticsearch as an external route
|
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
This adds the ability to expose Elastisearch as a route outside of the
cluster.
- `openshift_logging_es_allow_external`: True (default is False) - if this is
True, Elasticsearch will be exposed as a Route
- `openshift_logging_es_ops_hostname`: The external facing hostname to use for
the route and the TLS server certificate (default is "es." +
`openshift_master_default_subdomain`)
There are other similar parameters for the TLS server cert, key, and CA cert.
There are other similar parameters for when the OPS cluster is deployed e.g.
`openshift_logging_es_ops_allow_external`, etc.
|