-
Notifications
You must be signed in to change notification settings - Fork 701
[Contour Gateway Provisioner] add imagepullsecret for envoy and contour (fixes #7138) #7141
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
base: main
Are you sure you want to change the base?
Conversation
|
Hi @flbla! Welcome to our community and thank you for opening your first Pull Request. Someone will review it soon. Thank you for committing to making Contour better. You can also join us on our mailing list and in our channel in the Kubernetes Slack Workspace |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #7141 +/- ##
=======================================
Coverage ? 81.04%
=======================================
Files ? 130
Lines ? 19696
Branches ? 0
=======================================
Hits ? 15962
Misses ? 3449
Partials ? 285
🚀 New features to boost your workflow:
|
|
hi @tsaarni , okay, I added it |
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.
Question to consider:
Should we validate the image pull secret is present/valid in the cluster before reconciling the dataplane? or leave it up to the user to know that if their pods fail to deploy, it may be because the secret is invalid/not present?
cmd/contour/gatewayprovisioner.go
Outdated
| Default(provisionerConfig.gatewayControllerName). | ||
| StringVar(&provisionerConfig.gatewayControllerName) | ||
|
|
||
| cmd.Flag("image-pull-secret", "The image pull secret for the managed Envoy and Contour."). |
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.
nit: change flag to image-pull-secret-name
| @@ -0,0 +1 @@ | |||
| add a new flag: --image-pull-secret, which allows users to specify a secret in the same namespace as the gatewayprovisionner for pulling images from private registries. when set, it's used to pull Envoy and Contour images. No newline at end of file | |||
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.
shouldnt this specify that the secret lives in the same namespace as the deployed data/control plane? (not the provisioner, since it is a local object reference on the data/controlplane pod spec)
| } | ||
|
|
||
| if imagePullSecret != "" { | ||
| deploy.Spec.Template.Spec.ImagePullSecrets = []core_v1.LocalObjectReference{ |
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.
lets add some more test coverage (here and the dataplane tests) for the case when imagepullsecret is provided
…ur (fixes projectcontour#7138) Signed-off-by: flbla <[email protected]>
|
Hi @sunjayBhatia, thank you for the code review, I've updated based on your feedback. |
|
The Contour project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to the #contour channel in the Kubernetes Slack |
|
Keep it open please |
add a new image-pull-secret args for Contour Gateway Provisioner to be able to use an existing secret as image-pull-secret for envoy and contour
fixes #7138