summaryrefslogtreecommitdiffstats
path: root/roles/openshift_hosted/tasks/registry
Commit message (Collapse)AuthorAgeFilesLines
* hot fix for env variable resolveMangirdas2017-08-221-1/+1
|
* Merge pull request #4254 from dmsimard/registry_certsScott Dodson2017-08-214-49/+138
|\ | | | | Refactor openshift_hosted's docker-registry route setup
| * Refactor openshift_hosted's docker-registry route setupDavid Moreau-Simard2017-07-234-49/+138
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | Updated README to reflect refactor. Moved firewall initialize into separate ↵Kenny Woodson2017-08-101-2/+2
| | | | | | | | file.
* | Adding a default condition and removing unneeded defaults.Kenny Woodson2017-08-091-4/+4
| |
* | First attempt at refactor of os_firewallKenny Woodson2017-08-082-2/+45
|/
* hosted registry: Use proper node name in GlusterFS storage setupJose A. Rivera2017-07-141-1/+1
| | | | Signed-off-by: Jose A. Rivera <jarrpa@redhat.com>
* Set OPENSHIFT_DEFAULT_REGISTRY in registry dc.Andrew Butcher2017-06-301-0/+5
|
* registry: look for the oc executable in /usr/local/bin and ~/binGiuseppe Scrivano2017-06-271-2/+2
| | | | Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
* Merge pull request #4484 from jarrpa/glusterfs-fixes-tooOpenShift Bot2017-06-191-1/+1
|\ | | | | Merged by openshift-bot
| * registry: mount GlusterFS storage volume from correct hostJose A. Rivera2017-06-161-1/+1
| | | | | | | | Signed-off-by: Jose A. Rivera <jarrpa@redhat.com>
* | Make rollout status check best-effort, add pollSteve Kuznetsov2017-06-131-1/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | We cannot rely on the `watch.Until` call in the `rollout status` subcommand for the time being, so we need to ignore the result of this call. This will make the rollout status check best-effort, so we need to follow it with a poll for the actual status of the rollout, which we can extract from the `openshift.io/deployment.phase` annotation on the ReplicationControllers. This annotation can have only three values -- `Running`, `Complete` and `Failed`. If we poll on this attribute until we stop seeing `Running`, we can then inspect the last result for `Failed`; if it's present, we have failed the deployment. Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
* | Verify the rollout status of the hosted router and registrySteve Kuznetsov2017-06-091-0/+6
|/ | | | | | | | | | | | | | When deploying the hosted router and registry components, we need to ensure that they correctly roll out. The previous checks were weak in that they either simply waited for a set amount of time and/or did one replica check. They would fail if the router or registry took longer to deploy or if there were un-ready or failing replicas. The `oc rollout` command group contains the `status` endpoint for internalizing all of the logic for determining when a rollout has succeeded or failed, so simply using this client call will ensure that the router and registry correctly deploy. Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
* Remove supported/implemented barrier for registry object storage providers.Andrew Butcher2017-06-061-16/+0
|
* Removing requirement to pass aws credentialsEric Sauer2017-05-221-4/+0
|
* GlusterFS: Allow swapping an existing registry's backend storageJose A. Rivera2017-05-042-1/+34
| | | | Signed-off-by: Jose A. Rivera <jarrpa@redhat.com>
* hosted_registry: Get correct pod selector for GlusterFS storageJose A. Rivera2017-05-041-1/+9
| | | | Signed-off-by: Jose A. Rivera <jarrpa@redhat.com>
* hosted registry: Fix typoJose A. Rivera2017-05-041-1/+1
| | | | Signed-off-by: Jose A. Rivera <jarrpa@redhat.com>
* Allow for GlusterFS to provide registry storageJose A. Rivera2017-04-102-1/+56
| | | | Signed-off-by: Jose A. Rivera <jarrpa@redhat.com>
* Add docker-registry.default.svc short name to registry service signingScott Dodson2017-04-031-1/+2
|
* openshift_hosted: add openshift_hosted_registry_cert_expire_days parameter.Slava Semushin2017-03-291-0/+1
|
* Refactor and remove openshift_serviceaccountRussell Teague2017-03-131-2/+14
|
* Add oc_adm_policy_user task cluster-role policyRussell Teague2017-03-021-0/+7
|
* Correct config for hosted registryRussell Teague2017-03-021-1/+2
|
* Fixed error handling when oc adm ca create-server-cert fails. Fixed a logic ↵Kenny Woodson2017-03-011-1/+1
| | | | error in secure.
* Merge pull request #3493 from kwoodson/registry_reencyrpt_routeScott Dodson2017-03-012-2/+33
|\ | | | | Adding support for a route with reencrypt and certificates.
| * removing extra when conditionKenny Woodson2017-03-011-1/+0
| |
| * Removing run_once.Kenny Woodson2017-03-011-4/+0
| |
| * Adding the activeDeadlineSeconds. Removed debug.Kenny Woodson2017-03-011-11/+0
| |
| * Separating routes so logic is simpler.Kenny Woodson2017-03-011-6/+30
| |
| * Defaulting variables properly to avoid undefined route in dict error.Kenny Woodson2017-03-012-17/+16
| |
| * Removed duplicate host param.Kenny Woodson2017-02-281-1/+0
| |
| * Modified base debug statements. Fixed oc_secret debug/verbose flag. Added ↵Kenny Woodson2017-02-282-17/+8
| | | | | | | | reencrypt for route.
| * Adding support for a route with certs and reencrypt.Kenny Woodson2017-02-282-1/+35
| |
* | Merge pull request #3515 from mtnbikenc/registry-pvc-fixRussell Teague2017-02-281-2/+3
|\ \ | |/ |/| BZ1427009: Correct fact creation for pvc
| * Correct fact creation for pvcRussell Teague2017-02-271-2/+3
| |
* | Merge pull request #3512 from mtnbikenc/hosted-registry-serviceScott Dodson2017-02-271-0/+13
|\ \ | | | | | | BZ1427040: Create hosted registry service
| * | Create hosted registry serviceRussell Teague2017-02-271-0/+13
| |/
* / Make s3_volume_mount available to set_fact callSteve Milner2017-02-271-2/+3
|/ | | | | | 7cf5cc14 cleaned up how the registry was being created. However the s3 cloudfront calls ended up setting and using a fact in the same block. This change makes s3_volume_mount available to the set_fact.
* openshift_hosted: Update tasks to use oc_ modulesRussell Teague2017-02-245-302/+193
|
* CloudFront oc_secret contents should be a listSteve Milner2017-02-221-2/+2
| | | | | Fixes "argument contents is of type <type 'dict'> and we were unable to convert to list"
* Register cloudfront privkey when requiredSteve Milner2017-02-161-9/+23
|
* Merge pull request #3291 from ashcrow/oc-route-moduleJan Chaloupka2017-02-141-8/+8
|\ | | | | [WIP] oc route commands now using the oc_route module
| * oc route commands now using the oc_route moduleSteve Milner2017-02-141-8/+8
| |
* | Merge pull request #3306 from ingvagabund/oc_serviceJan Chaloupka2017-02-131-6/+5
|\ \ | |/ |/| replace 'oc service' command with its lib_openshift equivalent
| * replace 'oc service' command with its lib_openshift equivalentJan Chaloupka2017-02-111-6/+5
| |
* | Merge pull request #3300 from ashcrow/oc-secret-moduleJan Chaloupka2017-02-111-8/+11
|\ \ | | | | | | WIP: oc secrets now done via oc_secret module
| * | oc secrets now done via oc_secret moduleSteve Milner2017-02-101-8/+11
| |/
* / Replace service account secrets handling with oc_serviceaccount_secret moduleJan Chaloupka2017-02-102-20/+12
|/
* Copies CloudFront pem file to registry hostsSteve Milner2017-02-061-0/+21
| | | | | | | | | | | | | This change copies the CloudFront private key to registry hosts when the provider is set to s3 and CloudFront baseurl, privatekey, and keyparid are all provided. It also adds the following variable examples in the host inventory files: - openshift_hosted_registry_storage_s3_cloudfront_baseurl - openshift_hosted_registry_storage_s3_cloudfront_privatekeyfile - openshift_hosted_registry_storage_s3_cloudfront_keypairid See https://bugzilla.redhat.com/show_bug.cgi?id=1395168