Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

oc: add --insecure-policy for creating edge routes #9890

Merged
merged 1 commit into from
Jul 19, 2016
Merged

oc: add --insecure-policy for creating edge routes #9890

merged 1 commit into from
Jul 19, 2016

Conversation

0xmichalis
Copy link
Contributor

@0xmichalis
Copy link
Contributor Author

[test]

@openshift-bot
Copy link
Contributor

Evaluated for origin test up to f89940d

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/6366/)

@@ -130,6 +131,11 @@ func CreateEdgeRoute(f *clientcmd.Factory, out io.Writer, cmd *cobra.Command, ar
}
route.Spec.TLS.CACertificate = string(caCert)

insecurePolicy := kcmdutil.GetFlagString(cmd, "insecure-policy")
if len(insecurePolicy) > 0 {
route.Spec.TLS.InsecureEdgeTerminationPolicy = api.InsecureEdgeTerminationPolicyType(insecurePolicy)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it validate correctly against invalid values in insecurePolicy?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes.

$ oc create route edge --service=foo --insecure-policy=Allowed --port=80
The Route "foo" is invalid.
spec.tls.insecureEdgeTerminationPolicy: Invalid value: "Allowed": invalid value for InsecureEdgeTerminationPolicy option, acceptable values are None, Allow, Redirect, or empty

@fabianofranz
Copy link
Member

Minor comment otherwise LGTM.

@0xmichalis
Copy link
Contributor Author

Comment addressed [merge]

@openshift-bot
Copy link
Contributor

openshift-bot commented Jul 19, 2016

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/6366/) (Image: devenv-rhel7_4623)

@0xmichalis
Copy link
Contributor Author

FAILURE after 119.223s: test/end-to-end/core.sh:29: executing 'oc get -n test pods' expecting any result and text 'frontend.+Running'; re-trying every 0.2s until completion or 120.000s: the command timed out

It's taking more than 2m for the deployer to be created

frontend-1-deploy           0/1       ContainerCreating   0          2m

@smarterclayton @mfojtik

@0xmichalis
Copy link
Contributor Author

[merge]

@openshift-bot
Copy link
Contributor

Evaluated for origin merge up to f89940d

@openshift-bot openshift-bot merged commit 50f1f6e into openshift:master Jul 19, 2016
@0xmichalis 0xmichalis deleted the add-insecure-policy-flag branch July 19, 2016 13:24
@smarterclayton
Copy link
Contributor

The frontend problem is the same as the database - secret binding is the
problem.

On Tue, Jul 19, 2016 at 8:07 AM, OpenShift Bot [email protected]
wrote:

Merged #9890 #9890.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#9890 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABG_p5s6-I4x21gKkUW9J9y_ZSoSKdPQks5qXL3pgaJpZM4JOjlP
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants