Open mvinkler opened 2 years ago
/assign
Hey @rhuss , if @JuneOh710 is not working on this issue, i would like to work on it as it interests me. Could you brief me a little about this ? I did look into feature request and the use case, could you touch on things where should i start with ?
Hey @rhuss , if @JuneOh710 is not working on this issue, i would like to work on it as it interests me. Could you brief me a little about this ? I did look into feature request and the use case, could you touch on things where should i start with ?
Hello, @briheet01. I took on this issue as a part of an initiative for undergrad students. I'm actually meeting with a member of knative today at 5pm EST to discuss this issue. Would it be possible for you to let us continue working on this issue?
@JuneOh710 Yeah sure, good luck.
@aliok Is this issue is ready to grab? I would like to explore the projects of our Knative community.
I want to work on this issue if no one is working on it yet. I am assigning it to myself but pls do unassign me if you have sbd else working on this one already. Note that my contributions might take time and if I am assigned to an issue this means I am genuinely working on it.
/assign
Sorry I needed to unassign this from myself as I could not find much time to work on this as I am going thru a difficult pace on my end.
Feature request
Please introduce
--https
flag, similar to one in knative/serving: https://github.com/knative/serving/pull/5157Use case
The flag will add option to run all e2e tests with different http and https settings. Currently, TestDomain test expects the first service to be available at http, and the second at https, but this may not be the case if "defaultExternalScheme" is set to https.