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

Removing secure-verify-ca-secret support #4695

Merged
merged 2 commits into from
Nov 8, 2019

Conversation

janosi
Copy link
Contributor

@janosi janosi commented Oct 18, 2019

What this PR does / why we need it: The annotation secure-verify-ca-cert is not supported anymore and ignored silently currently. This PR is to remove the relevant code and the relevant parts from the documentation. There is a new error log if the annotation is present in an Ingress definition. Later this log should be removed, too, but currently it serves as a note to the users who currently uses this annotation in their Ingresses.

Which issue this PR fixes: This PR is due to issue #4503 , but the actual fix for the problem of that isse will be handled by issue 4688. I.e. this PR should not close any issues.

Special notes for your reviewer:

…that annotation is used in an Ingress definition
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Oct 18, 2019
@k8s-ci-robot
Copy link
Contributor

Hi @janosi. Thanks for your PR.

I'm waiting for a kubernetes 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.

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.

@k8s-ci-robot k8s-ci-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Oct 18, 2019
@@ -104,7 +104,7 @@ func TestAnnotations(t *testing.T) {
"default/secure-verify-ca": {},
},
}).Parse(ing)
if err != nil {
if err == nil {
Copy link

Choose a reason for hiding this comment

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

This should be an error here.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That is right. Fixing.

@janosi
Copy link
Contributor Author

janosi commented Oct 18, 2019

/assign @ElvinEfendi

@aledbf
Copy link
Member

aledbf commented Oct 18, 2019

@janosi please don't assign PRs manually

@aledbf
Copy link
Member

aledbf commented Oct 18, 2019

/ok-to-test

@k8s-ci-robot k8s-ci-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 Oct 18, 2019
@codecov-io
Copy link

Codecov Report

❗ No coverage uploaded for pull request base (master@a6815c3). Click here to learn what that means.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff            @@
##             master    #4695   +/-   ##
=========================================
  Coverage          ?   58.62%           
=========================================
  Files             ?       88           
  Lines             ?     6743           
  Branches          ?        0           
=========================================
  Hits              ?     3953           
  Misses            ?     2353           
  Partials          ?      437
Impacted Files Coverage Δ
internal/ingress/types.go 0% <ø> (ø)
internal/ingress/zz_generated.deepcopy.go 0% <ø> (ø)
internal/ingress/types_equals.go 17.39% <ø> (ø)
internal/ingress/controller/controller.go 50.43% <ø> (ø)
...nternal/ingress/annotations/secureupstream/main.go 100% <100%> (ø)

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 a6815c3...c76995b. Read the comment docs.

@janosi
Copy link
Contributor Author

janosi commented Oct 18, 2019

@janosi please don't assign PRs manually

Sure.
This message from the bot above is a bit confusing then
To complete the pull request process, please assign elvinefendi You can assign the PR to them by writing /assign @elvinefendi in a comment when ready.

@aledbf
Copy link
Member

aledbf commented Nov 8, 2019

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 8, 2019
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aledbf, janosi

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 8, 2019
@k8s-ci-robot k8s-ci-robot merged commit a0dc3a9 into kubernetes:master Nov 8, 2019
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. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", 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.

6 participants