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

Configure httpRedirect on istio gateway in helm #1948

Merged

Conversation

AyushSawant18588
Copy link
Contributor

Fixes #
Update knative-serving CRD to allow configuring of HTTP->HTTPS redirection on Istio Gateway through helm chart. Currently through knative operator helm chart HTTP->HTTPS redirection on Istio Gateway is not configurable. This was done only in Knative operator manifest file in this PR: #1912

Issue: #1944

Copy link

linux-foundation-easycla bot commented Dec 23, 2024

CLA Signed

  • ✅login: AyushSawant18588 / (25c678e)

The committers listed above are authorized under a signed CLA.

@knative-prow knative-prow bot requested review from houshengbo and matzew December 23, 2024 05:46
Copy link

knative-prow bot commented Dec 23, 2024

Welcome @AyushSawant18588! It looks like this is your first PR to knative/operator 🎉

@knative-prow knative-prow bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Dec 23, 2024
Copy link

knative-prow bot commented Dec 23, 2024

Hi @AyushSawant18588. 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.

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.

@AyushSawant18588 AyushSawant18588 force-pushed the httpRedirect-istio-gateway branch from 891f736 to 25c678e Compare December 23, 2024 06:19
@houshengbo houshengbo removed the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Dec 23, 2024
Copy link

codecov bot commented Dec 23, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 63.88%. Comparing base (29e9f59) to head (25c678e).
Report is 3 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1948   +/-   ##
=======================================
  Coverage   63.88%   63.88%           
=======================================
  Files          54       54           
  Lines        2622     2622           
=======================================
  Hits         1675     1675           
  Misses        830      830           
  Partials      117      117           

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

@houshengbo houshengbo added the cla: yes Indicates the PR's author has signed the CLA. label Dec 23, 2024
@houshengbo
Copy link
Contributor

@AyushSawant18588 could you join the knative org to pass the EasyCLA checking?

@@ -4875,6 +4875,13 @@ spec:
type: string
type: object
tls:
Copy link
Contributor

Choose a reason for hiding this comment

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

I am wondering whether you also need to change https://github.com/knative/operator/blob/main/config/charts/knative-operator/values.yaml for the default values of these new fields.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

These are changes in Knative Serving CRDs so I do not think there will be any change in values.yaml of knative-operator helm chart.
These changes will allow for httpRedirect configuration while creating Knative Serving Custom Resource after installing knative-operator through this helm chart. What do you think?

Copy link
Contributor

@houshengbo houshengbo Jan 2, 2025

Choose a reason for hiding this comment

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

I thought you were about to configure the values for the fields added in this PR.
If they are not editable in values.yaml, they will always be the same values as defined in the CRD. Still not configurable.

Copy link
Contributor Author

@AyushSawant18588 AyushSawant18588 Jan 2, 2025

Choose a reason for hiding this comment

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

This PR introduces changes to enable applying the httpRedirect setting when creating Knative Serving after installing the Knative Operator using the Helm chart. Since this setting is for Knative Serving, this setting is not to be configurable through the values.yaml file of the Knative Operator Helm chart .

@houshengbo
Copy link
Contributor

/test all

@houshengbo
Copy link
Contributor

/lgtm
/approve

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Jan 2, 2025
Copy link

knative-prow bot commented Jan 2, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AyushSawant18588, houshengbo

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 Jan 2, 2025
@knative-prow knative-prow bot merged commit 8ec7417 into knative:main Jan 2, 2025
21 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. 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.

2 participants