Skip to content
This repository has been archived by the owner on Jan 3, 2023. It is now read-only.

Support HTTPS only #142

Closed
nikhiljindal opened this issue Mar 7, 2018 · 1 comment
Closed

Support HTTPS only #142

nikhiljindal opened this issue Mar 7, 2018 · 1 comment
Assignees
@nikhiljindal
Milestone
v0.4

Comments

@nikhiljindal
Copy link
Contributor

Single cluster ingress supports blocking HTTP traffic all together as per: https://github.com/kubernetes/ingress-gce/blob/master/README.md#blocking-http.

We need to support it in kubemci as well

cc @csbell @G-Harmon @mdelio
@G-Harmon G-Harmon mentioned this issue Mar 7, 2018
Merged
This was referenced Mar 30, 2018
Merged
Merged
k8s-github-robot pushed a commit to kubernetes/kubernetes that referenced this issue Apr 4, 2018
Merge pull request #62052 from nikhiljindal/httpsOnly
6cd3c08 
Automatic merge from submit-queue (batch tested with PRs 61806, 61508, 62075, 62079, 62052). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.

Adding an e2e test for verifying https-only annotation with kubemci

Fixes GoogleCloudPlatform/k8s-multicluster-ingress#142

Refactoring existing GCE ingress test to be reusable with kubemci.
Similar to #61871

cc @G-Harmon @nicksardo @madhusudancs 

```release-note
NONE
```
@nikhiljindal nikhiljindal added this to the v0.4 milestone Apr 4, 2018
@nikhiljindal nikhiljindal self-assigned this Apr 4, 2018
@nikhiljindal
Copy link
Contributor Author

We now have an e2e test verifying that this is working: kubernetes/kubernetes#62052

@ryane ryane mentioned this issue Oct 28, 2018
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@nikhiljindal nikhiljindal

Labels
None yet
Projects
None yet
Milestone
v0.4
Development

No branches or pull requests
1 participant
@nikhiljindal