-
Notifications
You must be signed in to change notification settings - Fork 11
support metadata search #348
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
Conversation
14122f2
to
778f88a
Compare
@@ -0,0 +1,10 @@ | |||
{{- if .Values.serviceAccount.create }} |
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.
Though can be considered breaking change, it's kinda awkward we have these values for creating a new ServiceAccount yet we never do
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.
@guy-har Do you think we can keep this? We've already had this value but never actually created the serviceAccout, only referenced it.
778f88a
to
a34c3e1
Compare
a34c3e1
to
757a3f3
Compare
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.
Looks Good,
Added minor comments.
Also, how was this tested?
charts/lakefs/templates/_arktika.tpl
Outdated
{{/* | ||
Arktika service port | ||
*/}} | ||
{{- define "arktika.port" -}} | ||
{{- default 80 (.Values.mds.service).port }} | ||
{{- end }} |
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.
Didn't find usage, also, in the deployment we are using port 8000
apiVersion: v1 | ||
kind: Service | ||
metadata: | ||
name: arktika-server |
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.
name: arktika-server | |
name: {{ include "arktika.fullname" . }} |
charts/lakefs/templates/_arktika.tpl
Outdated
Arktika volumes | ||
*/}} | ||
{{- define "arktika.volumes" -}} | ||
{{- with .Values.mds.extraVolumes -}} |
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.
Does not exist in values 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.
I'm not sure it should be in the default values, because I thought that we shouldn't make these assumptions...
It's a consumer issue choosing what volumes or environment vars he needs. For our specific test case, I've created a secret with GS credentials which were then mounted using these generic templates.
Here's a snippet from my testing values, relevant for extraVolumes
and extraVolumeMounts
:
extraVolumes:
- name: gcp-credentials
secret:
secretName: gcp-credentials
extraVolumeMounts:
- name: gcp-credentials
mountPath: /app/credentials.json
subPath: credentials.json
extraEnvVars:
- name: GOOGLE_APPLICATION_CREDENTIALS
value: /app/credentials.json
charts/lakefs/templates/_arktika.tpl
Outdated
Arktika volume mounts | ||
*/}} | ||
{{- define "arktika.volumeMounts" -}} | ||
{{- with .Values.mds.extraVolumeMounts -}} |
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.
Does not exist in values 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.
Check above comment
labels: | ||
{{- include "arktika.labels" . | nindent 4 }} | ||
spec: | ||
replicas: {{ .Values.mds.replicaCount }} |
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.
Not sure whats the best practice here, but if we currently don't support working with multiple replicas, should it be hard coded? Otherwise we might need to document it somewhere
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.
Absolutely, thanks
I've manually installed the chart with both GS and S3 block stores and performed couple commits on the main repository, made sure the metadata repository is updated with no cloud provider errors |
2824b60
to
9ad1a90
Compare
9ad1a90
to
afdb0a3
Compare
charts/lakefs/templates/_arktika.tpl
Outdated
helm.sh/chart: {{ include "lakefs.chart" . }} | ||
{{ include "arktika.selectorLabels" . }} | ||
{{- if .Chart.AppVersion }} | ||
app.kubernetes.io/version: {{ .Chart.AppVersion | quote }} |
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.
I wonder - perhaps the version should be the mds image tag instead?
(Feel free to not do it and resolve if you think otherwise)
charts/lakefs/templates/_arktika.tpl
Outdated
{{- end }} | ||
- name: {{ include "arktika.fullname" . }}-config | ||
mountPath: /app/config.yaml | ||
subPath: config.yaml |
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.
Will this not error during apply if config is empty?
Meaning by default Values.mds.config
is null, so in runtime the ConfigMap has no key config.yaml
in it's data spec at all, there's no such key.
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.
I don't really mind as the service couldn't run without it, though we let the app catch it with a default value
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.
WDYM? not sure I understand the response
5b6a264
to
97e3dce
Compare
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.
Thanks! LGTM!
Left some unresolved / new comments but none of them is a blocker!
BTW Im sure you noticed but just in case there's git conflicts
charts/lakefs/values.yaml
Outdated
config: | ||
lakefs: | ||
endpoint: "https://example.lakefs.io" | ||
access_key_id: "AKIAIOSFOLEXAMPLE" | ||
secret_access_key: "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY" | ||
metadata_settings: | ||
since: "1970-01-01T00:00:00+00" | ||
max_commits: 100 | ||
repositories: | ||
# example-repo-1: | ||
# branches: | ||
# - main | ||
# - dev | ||
# example-repo-2: | ||
# branches: | ||
# - main | ||
# - feature-* |
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.
I would comment that out since it's dead config
and reference the docs, config structure may change
not a blocker
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.
It is commented and I have referenced the docs above the mds block
97e3dce
to
2edf037
Compare
Waiting on releasing until we have a valid image of the default version |
closes #treeverse/lakeFS-Enterprise#454
This was tested with both S3 and GS buckets