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

feat: add ditto operator support #19

Draft
wants to merge 7 commits into
base: main
Choose a base branch
from
Draft

Conversation

sjbodzo
Copy link
Contributor

@sjbodzo sjbodzo commented Jan 15, 2025

adds support for ditto operator, moving away from hades as we look towards its deprecation

@sjbodzo sjbodzo requested a review from ChrisMcKenzie January 15, 2025 03:19
Copy link

Linting charts...

------------------------------------------------------------------------------------------------------------------------
 Charts to be processed:
------------------------------------------------------------------------------------------------------------------------
 big-peer => (version: "0.2.14", path: "charts/big-peer")
------------------------------------------------------------------------------------------------------------------------

Error: directory ../ditto/charts/operator not found

------------------------------------------------------------------------------------------------------------------------
No chart changes detected.
------------------------------------------------------------------------------------------------------------------------
Error: failed linting charts: failed building dependencies for chart "big-peer => (version: \"0.2.14\", path: \"charts/big-peer\")": failed waiting for process: exit status 1
failed linting charts: failed building dependencies for chart "big-peer => (version: \"0.2.14\", path: \"charts/big-peer\")": failed waiting for process: exit status 1

@sjbodzo sjbodzo marked this pull request as draft January 15, 2025 03:22
@sjbodzo
Copy link
Contributor Author

sjbodzo commented Jan 15, 2025

Merge contigent upon:

  • agreement on structure of new classes / templates
  • setting chart ref back to upstream operator image
  • resolving any versioning issues

Copy link
Contributor

@sl1pm4t sl1pm4t left a comment

Choose a reason for hiding this comment

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

I know this is a WIP, but I've added some comments on improvements we could make.
Also, one question about removal of ingress configuration.

{{- /* Generate big peer deployment config driven by ditto operator */ -}}
{{- $fullname := include "common.names.fullname" . -}}
{{- $values := index .Values "ditto-deployment" -}}
{{- $storageClassName := default "local-path" $values.storage.storage_class_name -}}
Copy link
Contributor

Choose a reason for hiding this comment

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

StorageClass should be left blank by default, so that the cluster default is used.
local-path will not be compatible with most clusters.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good point, will make sure this one is addressed.

imagePullPolicy: {{ $values.image.pullPolicy }}
imagePullSecrets: []
resources:
limits:
Copy link
Contributor

Choose a reason for hiding this comment

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

Could we expose these resource settings as values instead of hardcoding.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yep, was hardcoded just to get it working. This is a draft currently..

imagePullSecrets: []
resources:
limits:
cpu: 2000m
Copy link
Contributor

Choose a reason for hiding this comment

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

Same here

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Agree

# Additional ingresses can be added by adding a dictionary key similar to the 'main' ingress.
# @default -- See below
ingress:
main:
Copy link
Contributor

Choose a reason for hiding this comment

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

Why is this being removed? Is this incompatible with Ditto Operator?
We are relying on this for valet.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hey, just seeing the feedback here. Yeah this branch is just for tracking what "works", not an optimized push for merge.

Currently Ditto Operator defines an ingress with nginx ingress class. This is wholly decoupled from the helm chart ingress route. What I have been doing is just ignoring the ingress config provided by the operator & relying on this one here. By removing the block Im making it "non default", but downstream I still specify it if that makes sense.

- name: hydra-consul
repository: oci://quay.io/ditto-external
- name: ditto-operator
repository: file://../../../ditto/charts/operator
Copy link
Contributor

Choose a reason for hiding this comment

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

We should update this to a public source.

repository: "oci://quay.io/ditto-external"
condition: hydra-subscription.enabled
#repository: "oci://quay.io/ditto-external"
repository: "file://../../../ditto/charts/operator"
Copy link
Contributor

Choose a reason for hiding this comment

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

Same here

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah these were pinned to local because at the time the branch was made it was only in a branch on the monorepo. These will be cleaned up before marking off draft :)

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