| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
openshift_cli_facts only runs a single task, and otherwise
the only existence is to serve as a link in the dependency
chain towards openshift_facts.
This commit flattens openshift_cli into one role.
|
| |
|
|\
| |
| | |
AWS Provisioning with scale groups.
|
| | |
|
|\ \
| | |
| | | |
Adding oc_adm_csr to lib_openshift for node approvals
|
| | | |
|
|\ \ \
| | | |
| | | | |
Add dnf support
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Adam Miller <maxamillion@fedoraproject.org>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Adam Miller <maxamillion@fedoraproject.org>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Adam Miller <maxamillion@fedoraproject.org>
|
|\ \ \ \
| | | | |
| | | | | |
Switch to migrating one host and scaling etcd members back up
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
With large datasets where there are many keys with TTLs the expiry was
creating a data inconsistency problem. The hope is that by performing
the migration once and then forming a new cluster this is avoided.
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1475351
|
|\ \ \ \ \
| | | | | |
| | | | | | |
bug 1468987: kibana_proxy OOM
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
We currently set the memory allocated to the kibana-proxy container to be
the same as `max_old_space_size` for nodejs. But in V8, the heap consists
of multiple spaces.
The old space has only memory ready to be GC and measuring the used heap
by kibana-proxy code, there is at least additional 32MB needed in the code
space when `max_old_space_size` peaks.
Setting the default memory limit to 256MB here and also changing the default
calculation of `max_old_space_size` in the image repository to be only half
of what the container receives to allow some heap for other `spaces`.
|
|\ \ \ \ \ \
| |_|/ / / /
|/| | | | | |
Allow GCS object storage to be configured
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Previously, setting the GCS registry object storage settings resulted in
an invalid configuration. This generates a registry-config secret that
has the correct file if the GCS config is set.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Fix missing space in calico ansible roles
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| |_|_|_|_|_|/
|/| | | | | | |
Refactor openshift_hosted's docker-registry route setup
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
We have identified an issue where a docker-registry service set up
as 'reencrypt' with a provided certificate and a self-signed certificate
on the pod does not authorize users to push images.
If the docker-registry service is set up as 'passthrough' with the
same provided certificate, everything works.
In light of this, this commit essentially adds support for configuring
provided certificates with a passthrough route while maintaining backwards
compatibility with the other use cases.
The default remains 'passthrough' with self-generated certificates.
Other miscellaneous changes include:
- Move fact setup that were only used in secure.yml there
- Omit the hostname for the route if there are none to configure,
oc_route takes care of handling the default
- Replace hardcoded /etc/origin/master by openshift_master_config_dir
|
|\ \ \ \ \ \ \
| |_|/ / / / /
|/| | | | | | |
Ensure that openshift_node_facts has been called for dns_ip
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| |_|_|/ / / /
|/| | | | | | |
Merged by openshift-bot
|
| |/ / / / / |
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
Use sdn_cluster_network_cidr as default calico pool
|
| | |_|_|/
| |/| | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Enable version 3.6 for OSE
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Merged by openshift-bot
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Merged by openshift-bot
|
| | |_|_|_|_|/
| |/| | | | | |
|
|\ \ \ \ \ \ \
| |_|_|/ / / /
|/| | | | | | |
Merged by openshift-bot
|
| |/ / / / / |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Merged by openshift-bot
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Merged by openshift-bot
|
| | |/ / / / /
| |/| | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
With origin 1.5, /usr/local/bin/oc was a symlink to
/usr/local/bin/openshift. During the container_binary_sync updated
versions of both binaries are copied to the host. First openshift is
copied to /usr/local/bin/openshift followed by copying oc to
/usr/local/bin/oc. Since oc is a symlink back to
/usr/local/bin/openshift the end result was everything linked to oc.
This change adds a check before copying a binary. If the destination is
a symlink then said symlink is removed before copying the new binary
over.
Fixed #4965
Reference: https://github.com/openshift/openshift-ansible/issues/4965
|
|\ \ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
Merged by openshift-bot
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| |_|_|_|/ / /
|/| | | | | | |
Merged by openshift-bot
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Additional os_firewall role refactoring
|
| | |_|/ / / /
| |/| | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
* Remove openshift_facts dependency
* Move firewall initialization from std_include.yml to
openshift_cluster/config.yml
Installing firewall packages is only necessary during OpenShift
installation.
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Miciah/openshift_checks-support-ovs-2.7-on-ocp-3.5-and-3.6
openshift_checks: allow OVS 2.7 on OCP 3.5 and 3.6
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
rpm_version: Allow package_list items to specify a list value for version.
If a list value is provided for a package, pass the check if any version in
that list is found.
ovs_version: Specify both 2.6 and 2.7 as allowed versions of OVS for
OpenShift versions 3.5 and 3.6.
|
|\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
adding check to a yaml dump to work properly with new ruamel lib
|
| | | | | | | | | |
|
|\ \ \ \ \ \ \ \ \
| |_|_|/ / / / / /
|/| | | | | | | | |
Change default CFME namespace to use reserved openshift- prefix
|
| | |_|/ / / / /
| |/| | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
As of OCP 3.6 we are advised to prefix reserved namespaces with an
'openshift-' prefix.
Fixes #5049
|