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

GKE single cluster configuration archetype #12

Closed
wants to merge 7 commits into from
Closed

GKE single cluster configuration archetype #12

wants to merge 7 commits into from

Conversation

kumare3
Copy link
Contributor

@kumare3 kumare3 commented Oct 31, 2019

Demo purposes. To make it work, users will need to change some config

name: staging
- id: production
name: production
- id: domain
Copy link
Contributor

Choose a reason for hiding this comment

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

let's nix this.

access-key: minio
auth-type: accesskey
disable-ssl: true
endpoint: http://minio.flyte.svc.cluster.local:9000
Copy link
Contributor

Choose a reason for hiding this comment

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

we're going to stick with using Minio for this? should we move to gcs?

Choose a reason for hiding this comment

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

we move to gcs?

Moving to GCS will be good..

registration:
maxWorkflowNodes: 100
scheduler:
eventScheduler:
Copy link
Contributor

Choose a reason for hiding this comment

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

should we remove this section completely or is there a gcp equivalent we can move to?

- --config
- /etc/flyte/config/flyteadmin_config.yaml
- serve
image: docker.io/lyft/flyteadmin:v0.1.4
Copy link
Contributor

Choose a reason for hiding this comment

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

this says 0.1.4, but the overlay file has 0.1.1. I'll remove that at some point. no reason to specify if it's not being used.

containers:
- name: flytepropeller
env:
- name: QUBOLE_API_KEY

Choose a reason for hiding this comment

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

What happen if we don't use QUBOLE?

@mweagle
Copy link

mweagle commented Apr 27, 2020

Is this still valid @kumare3 ?

@kumare3 kumare3 closed this Sep 13, 2021
eapolinario referenced this pull request in eapolinario/flyte Dec 20, 2022
* Update code of conduct

Signed-off-by: Samhita Alla <[email protected]>

* boilerpalte

Signed-off-by: Samhita Alla <[email protected]>
eapolinario referenced this pull request in eapolinario/flyte Aug 21, 2023
* Update code of conduct

Signed-off-by: Samhita Alla <[email protected]>

* boilerpalte

Signed-off-by: Samhita Alla <[email protected]>
eapolinario referenced this pull request in eapolinario/flyte Aug 21, 2023
* Updating GH workflows to not use the same hard-coded package name across all repos

* doc update

* Updating readme with a note about forks
eapolinario pushed a commit that referenced this pull request Sep 12, 2023
@cosmicBboy cosmicBboy deleted the gcp branch December 7, 2023 23:34
eapolinario pushed a commit that referenced this pull request Apr 30, 2024
)

* More updates

* Updated readme

* more updates

* more updates
austin362667 pushed a commit to austin362667/flyte that referenced this pull request May 7, 2024
…lyteorg#12)

* More updates

* Updated readme

* more updates

* more updates
robert-ulbrich-mercedes-benz pushed a commit to robert-ulbrich-mercedes-benz/flyte that referenced this pull request Jul 2, 2024
…lyteorg#12)

* More updates

* Updated readme

* more updates

* more updates
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.

6 participants