-
Notifications
You must be signed in to change notification settings - Fork 187
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
gitrepo: Add support for specifying proxy per GitRepository
#1109
Conversation
6515aaf
to
c74f6b1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a few minor suggestions.
The overall implementation LGTM!
e41a5ea
to
5143135
Compare
Add `.spec.proxySecretRef.name` to the `GitRepository` API to allow referencing a secret containing the proxy settings to be used for all remote Git operations for the particular `GitRepository` object. It takes precedence over any proxy configured through enviornment variables. Signed-off-by: Sanskar Jaiswal <[email protected]>
``` | ||
|
||
Proxying can also be configured in the source-controller Deployment directly by | ||
using the standard environment variables such as `HTTPS_PROXY`, `ALL_PROXY`, etc. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The cheatsheet is going away, we'll have a dedicated page for Proxy settings under installation/configuration
, see fluxcd/website#1560. For now let's leave it like this, after the docs refactoring we can link to it from here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks @aryan9600 🥇
Add
.spec.proxySecretRef.name
to theGitRepository
API to allow referencing a secret containing the proxy settings to be used for all remote Git operations for the particularGitRepository
object. It takes precedence over any proxy configured through environment variables.This allows for users to specify different proxy settings for different
GitRepository
objects as opposed to the current way of using env vars to specify proxy settings at a global controller level. This is particularly useful when the controller is running in a multi-tenant environment and tenants want to use their own proxy servers.