Skip to content

add probe path for whitelisting#6505

Merged
knative-prow-robot merged 18 commits intoknative:masterfrom
itsmurugappan:dev01
Jan 23, 2020
Merged

add probe path for whitelisting#6505
knative-prow-robot merged 18 commits intoknative:masterfrom
itsmurugappan:dev01

Conversation

@itsmurugappan
Copy link
Contributor

@itsmurugappan itsmurugappan commented Jan 12, 2020

Fixes #5918

Proposed Changes

  • Add a probe path thats easy to whitelist
  • e2e test

@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Jan 12, 2020
@knative-prow-robot knative-prow-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jan 12, 2020
Copy link
Contributor

@knative-prow-robot knative-prow-robot left a comment

Choose a reason for hiding this comment

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

@itsmurugappan: 0 warnings.

Details

In response to this:

Fixes #5918

Proposed Changes

  • Add a probe path thats easy to whitelist

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@knative-prow-robot
Copy link
Contributor

Hi @itsmurugappan. Thanks for your PR.

I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@knative-prow-robot knative-prow-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. area/autoscale area/networking labels Jan 12, 2020
@knative-prow-robot knative-prow-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. area/test-and-release It flags unit/e2e/conformance/perf test issues for product features and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jan 12, 2020
@nak3
Copy link
Contributor

nak3 commented Jan 12, 2020

/ok-to-test
/test pull-knative-serving-istio-1.4-mesh
/test pull-knative-serving-istio-1.3-mesh

@knative-prow-robot knative-prow-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jan 12, 2020
@knative-prow-robot knative-prow-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 12, 2020
@knative-prow-robot knative-prow-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jan 12, 2020
@knative-metrics-robot
Copy link

The following is the coverage report on the affected files.
Say /test pull-knative-serving-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/activator/net/revision_backends.go 93.6% 93.0% -0.6

@tcnghia
Copy link
Contributor

tcnghia commented Jan 16, 2020

/test all

@itsmurugappan
Copy link
Contributor Author

/test pull-knative-serving-https

@itsmurugappan
Copy link
Contributor Author

/test pull-knative-serving-istio-1.3-mesh

@itsmurugappan
Copy link
Contributor Author

/test pull-knative-serving-unit-tests

@tcnghia
Copy link
Contributor

tcnghia commented Jan 16, 2020

/test pull-knative-serving-kourier-stable
/test pull-knative-serving-istio-1.4-mesh

@knative-prow-robot
Copy link
Contributor

knative-prow-robot commented Jan 16, 2020

@itsmurugappan: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
pull-knative-serving-istio-1.4-no-mesh bb80418 link /test pull-knative-serving-istio-1.4-no-mesh
pull-knative-serving-gloo-0.17.1 bb80418 link /test pull-knative-serving-gloo-0.17.1
pull-knative-serving-contour-latest bb80418 link /test pull-knative-serving-contour-latest
pull-knative-serving-https 1864bb1 link /test pull-knative-serving-https
pull-knative-serving-kourier-stable 1864bb1 link /test pull-knative-serving-kourier-stable

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@knative-test-reporter-robot

The following jobs failed:

Test name Triggers Retries
pull-knative-serving-unit-tests 0/3

Failed non-flaky tests preventing automatic retry of pull-knative-serving-unit-tests:

pkg/reconciler/nscert.Failure

@itsmurugappan
Copy link
Contributor Author

/test pull-knative-serving-unit-tests

@tcnghia
Copy link
Contributor

tcnghia commented Jan 16, 2020

@itsmurugappan it looks like we are pretty close to the release cut date (Jan 20), so I am nervous about landing this now. We are usually in code freeze around this time.

So I am going
/hold
until next week. This will shift things out one release. Apologies for the inconvenience.

@knative-prow-robot knative-prow-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 16, 2020
@itsmurugappan
Copy link
Contributor Author

@itsmurugappan it looks like we are pretty close to the release cut date (Jan 20), so I am nervous about landing this now. We are usually in code freeze around this time.

So I am going
/hold
until next week. This will shift things out one release. Apologies for the inconvenience.

Sure. No problem.

@tcnghia
Copy link
Contributor

tcnghia commented Jan 21, 2020

/hold cancel

@knative-prow-robot knative-prow-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 21, 2020
@tcnghia
Copy link
Contributor

tcnghia commented Jan 23, 2020

@itsmurugappan let's check this in as is but let's not close the issue. I will follow up with making the probe path consistent with KPA probes as well to close the issue.

/lgtm
/approve

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 23, 2020
@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: itsmurugappan, tcnghia

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow-robot knative-prow-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 23, 2020
@knative-prow-robot knative-prow-robot merged commit 0ce2a6f into knative:master Jan 23, 2020
@itsmurugappan
Copy link
Contributor Author

@itsmurugappan let's check this in as is but let's not close the issue. I will follow up with making the probe path consistent with KPA probes as well to close the issue.

/lgtm
/approve

@tcnghia issue got closed before I could change the issue reference in the PR. Shall I open a new one ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/autoscale area/networking area/test-and-release It flags unit/e2e/conformance/perf test issues for product features cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Use better probe path than "/" for activator and KPA