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

Do not call GetIngressEndpoint() when --resolvabledomain is enabled #11318

Merged
merged 1 commit into from
May 10, 2021

Conversation

nak3
Copy link
Contributor

@nak3 nak3 commented May 9, 2021

GetIngressEndpoint() is a function to get ingress endpoint for the
spoof client. So we don't need to call it when --resolvabledomain is
enabled. Especially when Ingresss service uses ClusterIP, it alwasy
fails to get endpoint and test fails.

This patch changes to call GetIngressEndpoint() only when
resolvabledomain is false in websocket test.

`GetIngressEndpoint()` is a function to get ingress endpoint for the
spoof client. So we don't need to call it when `--resolvabledomain` is
enabled. Especially when Ingresss service uses `ClusterIP`, it alwasy
fails to get endpoint and test fails.

This patch changes to call GetIngressEndpoint() only when
resolvabledomain is false in websocket test.
@google-cla google-cla bot added the cla: yes Indicates the PR's author has signed the CLA. label May 9, 2021
@knative-prow-robot knative-prow-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. area/test-and-release It flags unit/e2e/conformance/perf test issues for product features labels May 9, 2021
@codecov
Copy link

codecov bot commented May 9, 2021

Codecov Report

Merging #11318 (3275f0b) into main (d30f0bd) will decrease coverage by 0.02%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##             main   #11318      +/-   ##
==========================================
- Coverage   87.74%   87.72%   -0.03%     
==========================================
  Files         191      191              
  Lines        9211     9211              
==========================================
- Hits         8082     8080       -2     
- Misses        876      878       +2     
  Partials      253      253              
Impacted Files Coverage Δ
pkg/autoscaler/scaling/multiscaler.go 87.61% <0.00%> (-1.77%) ⬇️
pkg/autoscaler/statforwarder/leases.go 76.97% <0.00%> (-1.44%) ⬇️
pkg/reconciler/configuration/configuration.go 88.28% <0.00%> (+1.56%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d30f0bd...3275f0b. Read the comment docs.

Copy link
Contributor

@markusthoemmes markusthoemmes left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label May 10, 2021
@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: markusthoemmes

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

The pull request process is described here

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 May 10, 2021
@knative-prow-robot knative-prow-robot merged commit 99acbaf into knative:main May 10, 2021
@nak3 nak3 deleted the test-websocket branch June 11, 2021 01:02
nak3 added a commit to nak3/serving that referenced this pull request Jun 11, 2021
…native#11318)

`GetIngressEndpoint()` is a function to get ingress endpoint for the
spoof client. So we don't need to call it when `--resolvabledomain` is
enabled. Especially when Ingresss service uses `ClusterIP`, it alwasy
fails to get endpoint and test fails.

This patch changes to call GetIngressEndpoint() only when
resolvabledomain is false in websocket test.
openshift-merge-robot pushed a commit to openshift/knative-serving that referenced this pull request Jun 15, 2021
* Do not call GetIngressEndpoint() when --resolvabledomain is enabled (knative#11318)

`GetIngressEndpoint()` is a function to get ingress endpoint for the
spoof client. So we don't need to call it when `--resolvabledomain` is
enabled. Especially when Ingresss service uses `ClusterIP`, it alwasy
fails to get endpoint and test fails.

This patch changes to call GetIngressEndpoint() only when
resolvabledomain is false in websocket test.

* Use TLS for websocket and gRPC tests (knative#11322)

* Support websocket https

* Use TLS for websocket and gRPC tests

Current gRPC and Websocket does not use TLS, but still uses HTTP even
when it runs with HTTPS mode.

This patch fixes it.

* Add ServerName to pseudo host with TLS.

* Decrease the length of test name

* Fix race issue

* Add workaround only https

* try dialer option

* Without parallel

* Use a single DialOption

* Revert "Without parallel"

This reverts commit 99455a6.

* Revert "Revert "Without parallel""

This reverts commit 7105cbc.

* Fix TestGRPCStreamingPingViaActivator

* Do not run gRPC with parallel

* Add TODO comment

* Use net.SplitHostPort

* make long ksvc name generic

* Revert "make long ksvc name generic"

This reverts commit 4119f08.
markusthoemmes pushed a commit to openshift/knative-serving that referenced this pull request Jun 22, 2021
* Do not call GetIngressEndpoint() when --resolvabledomain is enabled (knative#11318)

`GetIngressEndpoint()` is a function to get ingress endpoint for the
spoof client. So we don't need to call it when `--resolvabledomain` is
enabled. Especially when Ingresss service uses `ClusterIP`, it alwasy
fails to get endpoint and test fails.

This patch changes to call GetIngressEndpoint() only when
resolvabledomain is false in websocket test.

* Use TLS for websocket and gRPC tests (knative#11322)

* Support websocket https

* Use TLS for websocket and gRPC tests

Current gRPC and Websocket does not use TLS, but still uses HTTP even
when it runs with HTTPS mode.

This patch fixes it.

* Add ServerName to pseudo host with TLS.

* Decrease the length of test name

* Fix race issue

* Add workaround only https

* try dialer option

* Without parallel

* Use a single DialOption

* Revert "Without parallel"

This reverts commit 99455a6.

* Revert "Revert "Without parallel""

This reverts commit 7105cbc.

* Fix TestGRPCStreamingPingViaActivator

* Do not run gRPC with parallel

* Add TODO comment

* Use net.SplitHostPort

* make long ksvc name generic

* Revert "make long ksvc name generic"

This reverts commit 4119f08.
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/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. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants