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

Use InternalTLSEnabled() instead of internal-encryption #14301

Merged
merged 1 commit into from
Aug 29, 2023

Conversation

nak3
Copy link
Contributor

@nak3 nak3 commented Aug 28, 2023

This patch changes to use InternalTLSEnabled() instead of internal-encryption to verify config key.

Release Note

NOE

@knative-prow knative-prow bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Aug 28, 2023
@knative-prow knative-prow bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. area/API API objects and controllers area/autoscale area/networking area/test-and-release It flags unit/e2e/conformance/perf test issues for product features labels Aug 28, 2023
@nak3
Copy link
Contributor Author

nak3 commented Aug 28, 2023

/hold

We need to fix networking repo. Current PR is for demonstrating the error.

@knative-prow knative-prow bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 28, 2023
@nak3
Copy link
Contributor Author

nak3 commented Aug 28, 2023

The unit test should be fixed once knative/networking#847 was fixed.

@ReToCode
Copy link
Member

I like the idea, but do we want to reopen the discussion on having those flags with those settings first? Context: https://cloud-native.slack.com/archives/C04LGJ0D5FF/p1690967287198279?thread_ts=1688403244.113969&cid=C04LGJ0D5FF.

WDYT @KauzClay ?

@nak3
Copy link
Contributor Author

nak3 commented Aug 28, 2023

We can keep using the InternalTLSEnabled() even if the discussion will be accepted and the internal logic will be changed. So, I think it is not necessary to wait for the outcome of the discussion?

@ReToCode
Copy link
Member

Good point, let's do that.

@knative-prow-robot knative-prow-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 28, 2023
@knative-prow-robot knative-prow-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 29, 2023
@knative-prow knative-prow bot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Aug 29, 2023
@nak3 nak3 changed the title [WIP] Use dataplane-trust instead of internal-encryption Use InternalTLSEnabled() instead of internal-encryption Aug 29, 2023
@knative-prow knative-prow bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 29, 2023
@codecov
Copy link

codecov bot commented Aug 29, 2023

Codecov Report

Patch and project coverage have no change.

Comparison is base (43f7526) 86.23% compared to head (e2e8264) 86.23%.
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #14301   +/-   ##
=======================================
  Coverage   86.23%   86.23%           
=======================================
  Files         195      195           
  Lines       14702    14702           
=======================================
+ Hits        12678    12679    +1     
  Misses       1723     1723           
+ Partials      301      300    -1     
Files Changed Coverage Δ
cmd/activator/main.go 0.00% <0.00%> (ø)
pkg/reconciler/revision/resources/deploy.go 90.13% <0.00%> (ø)
pkg/reconciler/revision/revision.go 92.13% <0.00%> (ø)

... and 2 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@nak3
Copy link
Contributor Author

nak3 commented Aug 29, 2023

/hold cancel

This is ready now.

@knative-prow knative-prow bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 29, 2023
Copy link
Member

@ReToCode ReToCode left a comment

Choose a reason for hiding this comment

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

/lgtm

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Aug 29, 2023
@knative-prow
Copy link

knative-prow bot commented Aug 29, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nak3, ReToCode

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 knative-prow bot merged commit 09a8095 into knative:main Aug 29, 2023
63 checks passed
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/API API objects and controllers area/autoscale area/networking area/test-and-release It flags unit/e2e/conformance/perf test issues for product features lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants