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

Added imagePullSecrets to deployment template #904

Merged
merged 4 commits into from
Dec 2, 2022

Conversation

Kuvesz
Copy link
Contributor

@Kuvesz Kuvesz commented Dec 2, 2022

Q A
Bug fix? yes
New feature? no
API breaks? no
Deprecations? no
License Apache 2.0

What's in this PR?

I added imagePullSecrets to the deployment template and updated the chart version. Also updated release.yml to not include dev tags for now in releases.

Why?

Not sure when there would be a need for this as the images are publicly accessible but just in case it doesn't hurt if it's there.

Checklist

  • Implementation tested
  • Error handling code meets the guideline
  • Logging code meets the guideline

@Kuvesz Kuvesz requested a review from a team as a code owner December 2, 2022 12:55
@CLAassistant
Copy link

CLAassistant commented Dec 2, 2022

CLA assistant check
All committers have signed the CLA.

@Kuvesz Kuvesz force-pushed the update_chart_with_imagepullsecrets branch from 8b85c68 to 8295a21 Compare December 2, 2022 12:59
Copy link
Member

@pregnor pregnor left a comment

Choose a reason for hiding this comment

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

The change itself looks okay even though I would argue we should add commented out example code into the values.yaml.

The only use-case I could come up with would possibly be an air-gapped system with access control over the images.
I'm hesitant to approve, because I don't want additional unused code in the code base, but also don't want to block progress or uniforming things.

@Kuvesz
Copy link
Contributor Author

Kuvesz commented Dec 2, 2022

The change itself looks okay even though I would argue we should add commented out example code into the values.yaml.

The only use-case I could come up with would possibly be an air-gapped system with access control over the images. I'm hesitant to approve, because I don't want additional unused code in the code base, but also don't want to block progress or uniforming things.

To be honest I'm not exactly sure we need this either as I've stated in my original comment. Everything else will be fine without it really and we can come back to this if someone from the community feels like they need it?

pregnor
pregnor previously approved these changes Dec 2, 2022
@pregnor
Copy link
Member

pregnor commented Dec 2, 2022

We can let it fly as the values.yaml already contains the corresponding config.
In that sense this is really fixing a bug in the chart.

Copy link
Contributor

@bartam1 bartam1 left a comment

Choose a reason for hiding this comment

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

I think we can remove this part after that change:

{{- if .Values.imagePullSecrets }}

@Kuvesz
Copy link
Contributor Author

Kuvesz commented Dec 2, 2022

I think we can remove this part after that change:

{{- if .Values.imagePullSecrets }}

I don't quite get why? Would you mind explaining it a bit further?

@bartam1
Copy link
Contributor

bartam1 commented Dec 2, 2022

I think we can remove this part after that change:

{{- if .Values.imagePullSecrets }}

I don't quite get why? Would you mind explaining it a bit further?

When you add an imagepullsecret into a serviceaccount then a pod which use that serviceaccount will contain the imagepullsecret what is in the serviceaccount. Here you add that imagepullsecret into the deployment anyway. Our serviceaccount imagepullsecret solution is wrong I think because when a user disable (

) the serviceaccount creation then the imagepullsecret will not be in the default serviceaccount and in the koperator's pod.

@Kuvesz Kuvesz merged commit 91768f0 into master Dec 2, 2022
@Kuvesz Kuvesz deleted the update_chart_with_imagepullsecrets branch December 2, 2022 22:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants