Support for gRPC ingress on KAS

Ashvin Sharmarequested to merge
ashvins/grpc-ingress-kas into master

Issues:

What does this MR do?

This code change adds support for a new GRPC ingress configuration for the Kas component in GitLab. The changes create a new function to retrieve GRPC ingress settings, add logic to conditionally enable this feature when requested, and define the feature flag that controls whether GRPC ingress should be configured. Essentially, this gives users the option to enable a separate network entry point specifically for GRPC communication with the Kas service, which can be turned on or off through configuration settings.

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

  • Merge Request Title and Description are up to date, accurate, and descriptive
  • MR targeting the appropriate branch
  • MR has a green pipeline on GitLab.com
  • When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes

  • Documentation created/updated

  • Tests added

  • Integration tests added to GitLab QA (This is not done because of the reason mentioned here.)

  • Equivalent MR/issue for omnibus-gitlab opened (

    )

  • Validate potential values for new configuration settings. Formats such as integer 10, duration 10s, URI scheme://user:passwd@host:port may require quotation or other special handling when rendered in a template and written to a configuration file. (Not applicable, default value comes from helm chart)

Related issues

Edited by Ashvin Sharma

Merge request reports