Kenjiro Nakayama

Results 27 issues of Kenjiro Nakayama

**What steps did you take:** Here is the simple step to produce the issue. #### 1. Create job.yaml ```yaml cat

discussion

## What is changing? (Please include as many details as possible.) Once https://github.com/knative/serving/pull/13005 was merged, we should add the documentation about the feature. (I am going to create the draft...

triage/needs-eng-input
kind/serving
status/blocked
lifecycle/stale
kind/feature-request

Support disabling HTTP traffic between Ingress and activator As described in [the feature docs](https://docs.google.com/document/d/1XE7UzgQlVVtAb7ULSqOyKCaIHtm8zMF35ainp1JmwyY/edit?resourcekey=0-e1MXRxQaalq-EHW46ZCCWg#): > it will similarly want an ENCRYPTED_ONLY variable (or file) to disable the non-encrypted paths. the...

kind/feature

## In what area(s)? /area test-and-release ## What version of Knative? HEAD ## Expected Behavior TestScaleToN passes somewhat consistently ## Actual Behavior TestScaleToN fails pretty consistently ## Steps to Reproduce...

kind/bug
area/test-and-release

## In what area(s)? /area networking /area test-and-release As commented https://github.com/knative/serving/pull/11322/files#r636574573, e2e test with `--https` option does not work with `t.Parallel()` for TestWebSocket*. Example log https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative_serving/11322/pull-knative-serving-https/1395322718584311808 https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative_serving/11322/pull-knative-serving-https/1395530844940013568 It often fails...

kind/bug
area/networking
area/test-and-release
lifecycle/frozen
triage/accepted

## In what area(s)? /area networking /area test-and-release ## Describe the feature Current upgrade test `test/e2e-upgrade-tests.sh` does not spport `https` option. As far as tested with the following changes: https://github.com/knative/serving/pull/11529/commits/1a2dcb6cc6b8d5ab2958d579468f45a22d70a9b8...

kind/feature
area/networking
area/test-and-release
triage/accepted

/area networking /area test-and-release ## What version of Knative? HEAD ## Expected Behavior e2e with Contour do not fail. ## Actual Behavior Please refer to the recent KinD e2e logs....

kind/bug
area/networking
area/test-and-release

As described in [the feature docs](https://docs.google.com/document/d/1XE7UzgQlVVtAb7ULSqOyKCaIHtm8zMF35ainp1JmwyY/edit?resourcekey=0-e1MXRxQaalq-EHW46ZCCWg#): > NOT IN SCOPE: > Scaling metadata (not request data) user pods autoscaler, activator autoscaler. the alpha release does not support the encrypted traffic...

kind/feature
lifecycle/active

As described in [the feature docs](https://docs.google.com/document/d/1XE7UzgQlVVtAb7ULSqOyKCaIHtm8zMF35ainp1JmwyY/edit?resourcekey=0-e1MXRxQaalq-EHW46ZCCWg#): > the HTTP Proxy (KIngress) needs to be able to accept certificates for *both* the activator (in the knative-serving namespace) and the Revision pods...

kind/feature
lifecycle/active

Please see reproduce steps: ##### step-1. current version ``` $ git log --oneline -p -1 601a49d Merge pull request #22 from dinever/admin_ui ``` ##### step-2. Start dingo ``` go run...

bug