-
Notifications
You must be signed in to change notification settings - Fork 18
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
Loki gateway does not deploy on RKE2 #68
Comments
Dropping override example here for those hitting issues.
|
Dropping a comment update here - it wouldn't fix the "automagic" nature of this but we could expose this Loki DNS value as a zarf helm override (zarf-dev/zarf#2403). |
Switching this to enhancement issue. I would like to tackle this by adding a standardized DNS service that we manage as part of the Loki uds-config chart. In reviewing this issue I noted a few things:
The path forward here:
This should be a relatively seamless change, and for existing users overriding this they would be able to drop their override. Marking this as a good-first-issue, happy to converse with anyone who wants to pick this up. |
## Description Creates a standard service in the loki package so that the loki gateway can rely on the name of this service instead of nonstandard names for the DNS service in certain k8s distros (i.e. rke2). ... ## Related Issue Fixes #68 ## Type of change - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Other (security config, docs update, etc) ## Checklist before merging - [ ] Test, docs, adr added or updated as needed - [ ] [Contributor Guide](https://github.com/defenseunicorns/uds-template-capability/blob/main/CONTRIBUTING.md) followed Co-authored-by: Micah Nagel <micah.nagel@defenseunicorns.com>
Environment
Device and OS: ec2 instance, amazon linux 2023
App version: 0.6.2
Kubernetes distro being used: RKE2 1.27.x
Steps to reproduce
Expected result
Happy deploy!
Actual Result
The loki gateway is configured to point at the DNS service in kube-system. The default svc name it expects is
kube-dns
and RKE2 has a different name (rke2-coredns-rke2-coredns
).Severity/Priority
Medium? Completely blocks deployment after loki if the dns service is not named
kube-dns
, but with bundle overrides it could be changed.Additional Context
While this could be done with a variable it would be annoying to have to pass in an environment specific value like this. Ideally a standard service could be created that maps to the DNS pods in cluster already?
The text was updated successfully, but these errors were encountered: