| Age | Commit message (Collapse) | Author |
|---|
|
enable dynamicly provisioned GlusterFS volume for hosted registry
|
|
|
|
|
|
|
|
to set the registry hostname""
|
|
the registry hostname"
|
|
Automatic merge from submit-queue.
Set a default for openshift_hosted_registry_storage_azure_blob_realm
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1491100
|
|
Automatic merge from submit-queue.
use non-deprecated REGISTRY_OPENSHIFT_SERVER_ADDR variable to set the registry hostname
|
|
Remove unused symlink
|
|
|
|
registry hostname
bug 1537593
https://bugzilla.redhat.com/show_bug.cgi?id=1537593
|
|
Add missing task that got dropped in a refactor
|
|
Removed in 28b254886bf17251e973bfdad4dd4c89e26187fc
|
|
|
|
Move more plugins to lib_utils
|
|
|
|
This commit continues moving plugins into lib_utils.
This commit does not move any plugins for add-on roles
such as logging and metrics.
|
|
In Ansible 2.2, the include_role directive came into existence as
a Tech Preview. It is still a Tech Preview through Ansible 2.4
(and in current devel branch), but with a noteable change. The
default behavior switched from static: true to static: false
because that functionality moved to the newly introduced
import_role directive (in order to stay consistent with include*
being dynamic in nature and `import* being static in nature).
The dynamic include is considerably more memory intensive as it will
dynamically create a role import for every host in the inventory
list to be used. (Also worth noting, there is at the time of this
writing an object allocation inefficiency in the dynamic include
that can in certain situations amplify this effect considerably)
This change is meant to mitigate the pressure on memory for the
Ansible control host.
We need to evaluate where it makes sense to dynamically include roles
and revert back to dynamic inclusion if and where it makes sense to do
so.
|
|
Currently, both registry and router pods need to
be polled for successful deployment.
Somtimes this can take up to a minute.
This commit attempts to deploy both pods
before polling either. This should reduce
the average wait time for polling pods by 50%
as time spent polling the first will also allow
the second pod to continue it's own deployment.
|
|
We set these variables using facts in init, no need
to duplicate the logic all around the codebase.
|
|
This commit relocates filter_plugings to lib_utils,
changes the namespacing to prevent unintended use of
older versions that may be present in filter_plugins/
directory on existing installs.
Add lib_utils to meta depends for roles
Also consolidate some plugins into lib_utils from
various other areas.
Update rpm spec, obsolete plugin rpms.
|
|
This commit removes a now-empty role.
|
|
|
|
add 3.8 templates for gluster ep and svc
|
|
|
|
|
|
|
|
Remove hosted vars from openshift_facts.
The current pattern is causing a bunch of undesired sideffects.
|
|
|
|
Add external glusterfs backend to hosted and glusterfs playbook
|
|
|
|
hosted_registry: clean up tmp mount point and fstab
|
|
|
|
This commit removes any references to versions < 1.5/3.5
We assume the version is always greater than or equal to 1.5/3.5.
|
|
Fixes #6004
|
|
Automatic merge from submit-queue.
Allow cluster IP for docker-registry service to be set
For historical reasons a small set of programs in our environments rely
on the cluster-internal Docker registry having the IP address
"172.30.1.1". So far we always had to patch in that address manually.
Adding a variable on the "openshift_hosted" role allows the IP address
to be set correctly when a cluster is installed.
|
|
|
|
The "registry_volume_claim" variable has not been used since at least
commit 7cf5cc1 (February 21, 2017) and this commit removes the last
mention.
|
|
For historical reasons a small set of programs in our environments rely
on the cluster-internal Docker registry having the IP address
"172.30.1.1". So far we always had to patch in that address manually.
Adding a variable on the "openshift_hosted" role allows the IP address
to be set correctly when a cluster is installed.
|
|
Update registry_config.j2 to fix BZ#1490738
|
|
auto-generated wildcard certificate or custom openshift_hosted_router_certificate.
|
|
Filter plugin modules should have unique names to not conflict with core
Ansible modules. (Ansible 2.4)
|
|
Currently, openshift_hosted role duplicates some logic
across separate task chains. This commit cleans up
the openshift_hosted role and converts it to be
primarily used with include_role to give better
logic to the playbooks that utilize this role.
This commit also refactors the playbook that calls
various openshift_hosted roles into individual playbooks.
This allows more granularity for advanced users.
|
|
Automatic merge from submit-queue
hot fix for env variable resolve
If we use environment variables in our inventory files (and from what I seen we do this everywhere where We deploy OCP) our fact engine ignores env variables so if my path looks like
```
openshift_hosted_registry_routecertificates={"certfile": "{{inventory_dir}}/../files/certs/wildcard.registry.company.local.crt", "keyfile": "{{inventory_dir}}/../files/certs/wildcard.registry.companylocal.key", "cafile":"{{inventory_dir}}/../files/certs/CompanyLocalRootCA.crt"}
openshift_hosted_registry_routehost=containers.registry.comany.local
```
the result is: `/../files/certs/RoSLocalRootCA.crt`
We need to fix our fact set in a long run to read Ansible variables. And it was done in the same way with router certificates already.
|
|
|
|
This workaround prevents the warnings on using Jinja2 templating
delimiters in `when:` conditions in cases where a variable is used as
the conditional. This has been fixed in Ansible 2.4.
https://github.com/ansible/ansible/pull/25092
|
|
setting openshift_hosted_registry_storage_gcs_rootdirectory default value
|
|
|
|
Merged by openshift-bot
|
|
Merged by openshift-bot
|
