| Summary: | [networking_public_181]Should add option '--insecure-policy' for passthrough and reencrypt route for CLI | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | zhaozhanqi <zzhao> |
| Component: | Networking | Assignee: | Jacob Tanenbaum <jtanenba> |
| Status: | CLOSED ERRATA | QA Contact: | Meng Bo <bmeng> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.5.0 | CC: | aos-bugs, bbennett, eparis, mmccomas, tdawson, xtian |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
Feature: add the ability to configure insecure termination policy for passthrough and reencrypt routes
Reason: insecure termination was added to these route types and the configuration options should be consistent with edge routes
Result: It is possible to configure insecure termination for the three types of routes from the CLI
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-04-12 19:18:17 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
zhaozhanqi
2016-12-09 09:51:45 UTC
Jake, did this get resolved by the work for https://trello.com/c/0BaxAOK9 ? Commit pushed to master at https://github.com/openshift/origin https://github.com/openshift/origin/commit/daa215cbc1e2ae698e6f667751486c7791b9a0dc adding option '--insecure-policy' for passthrough and reencrypt route for CLI PR11953 added support for insecureEdgeTerminationPolicy to reencrypt and passthrough routes, so it should be supported in the CLI as well. Bug: 1403155 This has been merged into ocp and is in OCP v3.5.0.17 or newer. Verified this bug v3.5.0.17 this bug has been fixed. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:0884 |