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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Calendso chart first draft #15

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Calendso chart first draft #15

wants to merge 1 commit into from

Conversation

tinyzimmer
Copy link
Contributor

Haven't put it through extensive testing yet, mainly because I've never used the product before. But seems to start okay so far 馃槢

@tinyzimmer tinyzimmer requested a review from kav September 12, 2021 11:01
@josephedward
Copy link

This is a really handy chart - fwiw, when I tried to use calendso the challenge was verifying the domain with google search console to be able to use any of the google reminders etc - given we have our gcp credentials in the chart, is there a way to programmatically make that request to the gcp api?

@tinyzimmer
Copy link
Contributor Author

This is a really handy chart - fwiw, when I tried to use calendso the challenge was verifying the domain with google search console to be able to use any of the google reminders etc - given we have our gcp credentials in the chart, is there a way to programmatically make that request to the gcp api?

If I think I'm understanding you correctly, probably not? That's kinda one of the downsides of helm, you don't have the ability to programmatically do stuff like that, and where you do, it's not in a very idempotent way.

At my first look at this application, it almost felt to me like it warrants an operator.

@josephedward
Copy link

This is a really handy chart - fwiw, when I tried to use calendso the challenge was verifying the domain with google search console to be able to use any of the google reminders etc - given we have our gcp credentials in the chart, is there a way to programmatically make that request to the gcp api?

If I think I'm understanding you correctly, probably not? That's kinda one of the downsides of helm, you don't have the ability to programmatically do stuff like that, and where you do, it's not in a very idempotent way.

At my first look at this application, it almost felt to me like it warrants an operator.

I don't know as much as you do about kubernetes, but it seems like it could use an operator. Not sure if there's even a way to do that programmatically at all, being somewhat sensitive and subject to human review (of the proposed domain to search console). I guess there could be directions to get a domain approved, then deploy the chart. Or could use some other scheduling and email libraries to replicate the reminders...I guess you could put that code in an operator and wouldn't need google at all. Tedious, but then no one would know about your meetings? Is calendso's more privacy-centric hosting service open for registration?

@tinyzimmer
Copy link
Contributor Author

I clearly need to play with it more to get more context on the flow you are describing. Part of me wanted to throw it up on a private cluster and play around with it anyway, since I've never used it or calendly before.

Where in the helm chart you have the option to give me the name of a secret, I don't have the ability to actually fetch the contents of that secret. But, an operator would be a different story. It would have access to the K8s APIs and be able to programmatically interact with the secret values and such. Could even do things like generate the CalDav key in a cleaner manner than helm provides (which I opted to avoid entirely).

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

3 participants