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

Cert rotation test does not use specific ingress namespace #15331

Merged
merged 1 commit into from
Jun 17, 2024

Conversation

mgencur
Copy link
Contributor

@mgencur mgencur commented Jun 17, 2024

Fixes #15276

Proposed Changes

  • The routing-serving-certs are deployed in system namespace. This is where both Serving and Kourier controller expects them. The Serving components and Kourier might be possibly deployed in different system namespaces (like downstream) but in upstream it's the same namespace.

Release Note


@knative-prow knative-prow bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jun 17, 2024
@knative-prow knative-prow bot requested review from ReToCode and skonto June 17, 2024 06:33
Copy link

codecov bot commented Jun 17, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.79%. Comparing base (1f7cc48) to head (2f5bb44).

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #15331      +/-   ##
==========================================
+ Coverage   84.78%   84.79%   +0.01%     
==========================================
  Files         218      218              
  Lines       13504    13504              
==========================================
+ Hits        11449    11451       +2     
+ Misses       1688     1687       -1     
+ Partials      367      366       -1     

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

@@ -225,12 +219,6 @@ func TestTLSCertificateRotation(t *testing.T) {
t.Fatalf("Failed to delete secret %s in system namespace: %v", config.ServingRoutingCertName, err)
}
checkEndpointState(t, clients, url)

t.Log("Deleting secret in ingress namespace")
if err := clients.KubeClient.CoreV1().Secrets(ingressNS).Delete(context.Background(), config.ServingRoutingCertName, v1.DeleteOptions{}); err != nil {
Copy link
Contributor

Choose a reason for hiding this comment

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

It seems the error is: system_internal_tls_test.go:231: Failed to delete secret routing-serving-certs in ingress namespace: secrets "routing-serving-certs" not found. We could skip that error with if apierrs.IsNotFound(err) but I guess we want to keep upstream clean from the downstream assumptions.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Right. I wanted to keep upstream clean. Thanks

@skonto
Copy link
Contributor

skonto commented Jun 17, 2024

/test ?

Copy link

knative-prow bot commented Jun 17, 2024

@skonto: The following commands are available to trigger required jobs:

  • /test build-tests
  • /test contour-latest
  • /test contour-tls
  • /test gateway-api-latest
  • /test istio-latest-no-mesh
  • /test istio-latest-no-mesh-tls
  • /test kourier-stable
  • /test kourier-stable-tls
  • /test unit-tests
  • /test upgrade-tests

The following commands are available to trigger optional jobs:

  • /test gateway-api-latest-and-contour
  • /test https
  • /test istio-latest-mesh
  • /test istio-latest-mesh-short
  • /test istio-latest-mesh-tls
  • /test performance-tests

Use /test all to run the following jobs that were automatically triggered:

  • build-tests_serving_main
  • istio-latest-no-mesh-tls_serving_main
  • istio-latest-no-mesh_serving_main
  • unit-tests_serving_main
  • upgrade-tests_serving_main

In response to this:

/test ?

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-sigs/prow repository.

@skonto
Copy link
Contributor

skonto commented Jun 17, 2024

/test kourier-stable

@skonto
Copy link
Contributor

skonto commented Jun 17, 2024

/test kourier-stable-tls

@skonto
Copy link
Contributor

skonto commented Jun 17, 2024

/lgtm
/approve

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Jun 17, 2024
Copy link

knative-prow bot commented Jun 17, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mgencur, skonto

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 added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 17, 2024
@skonto
Copy link
Contributor

skonto commented Jun 17, 2024

/hold for tests

@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 Jun 17, 2024
@mgencur
Copy link
Contributor Author

mgencur commented Jun 17, 2024

/test kourier-stable

Unrelated error.

@mgencur
Copy link
Contributor Author

mgencur commented Jun 17, 2024

/unhold

@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 Jun 17, 2024
@knative-prow knative-prow bot merged commit 8d768f5 into knative:main Jun 17, 2024
69 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. 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.

TestTLSCertificateRotation is flakey
2 participants