Skip to content

introduce new feature flag for auto_sni #38604

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

Merged
merged 1 commit into from
Apr 27, 2022

Conversation

kfaseela
Copy link
Member

A later discussion concluded that it makes better sense
to introduce a new feature flag for enabling auto_sni,
and only auto_san_validation should be clubbed with existing VERIFY_CERT_AT_CLIENT feature flag.
RFC has been updated accordingly.

Signed-off-by: Faseela K faseela.k@est.tech

Please provide a description of this PR:

To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

  • Configuration Infrastructure
  • Docs
  • Installation
  • [ X] Networking
  • Performance and Scalability
  • Policies and Telemetry
  • Security
  • Test and Release
  • User Experience
  • Developer Infrastructure

Please check any characteristics that apply to this pull request.

  • [ X] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

Sorry, something went wrong.

@kfaseela kfaseela requested review from a team as code owners April 26, 2022 20:56
@istio-policy-bot istio-policy-bot added area/networking release-notes-none Indicates a PR that does not require release notes. labels Apr 26, 2022
@istio-testing istio-testing added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Apr 26, 2022
@kfaseela kfaseela force-pushed the feature-flag-for-auto-sni branch from aa85f66 to 33b4692 Compare April 26, 2022 21:11
A later discussion concluded that it makes better sense
to introduce a new feature flag for enabling auto_sni,
and auto_san_validation should be clubbed with VERIFY_CERT_AT_CLIENT.
RFC has been updated accordingly.

Signed-off-by: Faseela K <faseela.k@est.tech>
@kfaseela kfaseela force-pushed the feature-flag-for-auto-sni branch from 33b4692 to 274c406 Compare April 26, 2022 21:13
Copy link
Member

@hzxuzhonghu hzxuzhonghu left a comment

Choose a reason for hiding this comment

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

LGTM

@kfaseela
Copy link
Member Author

/retest

@kfaseela
Copy link
Member Author

/test integ-pilot-istiodremote-mc_istio

@istio-testing
Copy link
Collaborator

In response to a cherrypick label: new pull request created: #38611

l8huang pushed a commit to l8huang/istio that referenced this pull request Jun 16, 2022
* Add auto-sni support (istio#38238)

* [WIP] Add auto-sni support

Signed-off-by: Faseela K <faseela.k@est.tech>

* Fix unit test failure

Signed-off-by: Faseela K <faseela.k@est.tech>

* enhance release-notes and small code improvements

Signed-off-by: Faseela K <faseela.k@est.tech>

* introduce new feature flag for auto_sni (istio#38604)

A later discussion concluded that it makes better sense
to introduce a new feature flag for enabling auto_sni,
and auto_san_validation should be clubbed with VERIFY_CERT_AT_CLIENT.
RFC has been updated accordingly.

Signed-off-by: Faseela K <faseela.k@est.tech>

* fix unit test

Co-authored-by: Faseela K <faseela.k@est.tech>
@kfaseela kfaseela deleted the feature-flag-for-auto-sni branch August 5, 2022 08:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/networking release-notes-none Indicates a PR that does not require release notes. 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.

None yet

5 participants