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

[stable/aws-s3-proxy] Sync labels btw pod and deployment #588

Merged

Conversation

BlueHorn07
Copy link
Contributor

@BlueHorn07 BlueHorn07 commented Jun 30, 2024

Description

The labels for Deployment, Ingress, and Services are defined as aws-s3-proxy.labels in the _helpers.tpl file. However, the labels for pods do not use these common labels.

In my experience, when I added extraLabels in the values file, they were not applied to the pods’ labels, only to the Deployment and other resources.

I believe that using the defined common labels for pods as well would be more helpful.

Checklist

  • Title of the PR starts with chart name (e.g. [stable/mychartname])
  • I have read the contribution instructions, bumped chart version and regenerated the docs
  • Github actions are passing

@BlueHorn07 BlueHorn07 requested a review from a team as a code owner June 30, 2024 05:26
@BlueHorn07 BlueHorn07 changed the title sync labels between deployment and pod [stable/aws-s3-proxy] Sync labels btw pod and deployment Jun 30, 2024
@@ -8,13 +8,11 @@ spec:
replicas: {{ .Values.replicaCount }}
selector:
matchLabels:
app.kubernetes.io/name: {{ include "aws-s3-proxy.name" . }}
app.kubernetes.io/instance: {{ .Release.Name }}
{{ include "aws-s3-proxy.labels" . | indent 6 }}
Copy link
Member

@max-rocket-internet max-rocket-internet Jul 1, 2024

Choose a reason for hiding this comment

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

I don't think this part should change as selector labels are immutable and shouldn't be treated like the other labels 🙂

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hi there, thanks for your comment!

Are you suggesting that the changes to matchLabels might cause breaking changes? If that’s the case, I’ll revert the changes to matchLabels. 🙏

Copy link
Member

Choose a reason for hiding this comment

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

Exactly, they are immutable, you can't change them without deleting and recreating the resource. So I would just not change this part.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I’ve reverted it. Thanks for pointing it out and for your kind review! 😄

Copy link
Member

@max-rocket-internet max-rocket-internet left a comment

Choose a reason for hiding this comment

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

Nice, thanks @BlueHorn07 💖

@max-rocket-internet max-rocket-internet merged commit 762a516 into deliveryhero:master Jul 1, 2024
5 checks passed
fekaiser pushed a commit to gastromatic/delivery-hero-helm-charts that referenced this pull request Oct 23, 2024
…o#588)

* sync labes between deployment and pod

* bump chart version to 0.1.5

* revert matchLabels changes
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.

2 participants