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

[dy] Add ingress chart #42

Merged
merged 2 commits into from
Jan 31, 2024
Merged

[dy] Add ingress chart #42

merged 2 commits into from
Jan 31, 2024

Conversation

dy46
Copy link
Contributor

@dy46 dy46 commented Jan 26, 2024

Summary

Create separate helm chart to create ingress for Mage. Including the ingress with the main helm chart can lead to issues when upgrading the chart. I also added a comment to the main helm chart to recommend creating the ingress separately.

Tests

Tested locally

cc: @wangxiaoyou1993

Scheduler Selector labels
*/}}
{{- define "mageai.schedulerSelectorLabels" -}}
app.kubernetes.io/name: {{ .Values.scheduler.name }}
Copy link
Member

Choose a reason for hiding this comment

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

can you remove unused configs in the ingress helm chart?
Make sure the values used in this file are shown in the values.yaml

annotations:
artifacthub.io/alternativeName: Mage-Ingress
artifacthub.io/category: integration-delivery
artifacthub.io/images: |
Copy link
Member

Choose a reason for hiding this comment

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

these images are not used in this helm chart. so you don't need to include them

Copy link
Member

Choose a reason for hiding this comment

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

@dy46
Copy link
Contributor Author

dy46 commented Jan 31, 2024

@wangxiaoyou1993 updated

@dy46 dy46 merged commit 50a9572 into master Jan 31, 2024
4 checks passed
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.

None yet

2 participants